Skip to main content

Notifications

Community site session details

Community site session details

Session Id : E8Q25NuGA734RN4bfhX80o
Power Apps - Building Power Apps
Unanswered

Custom Connector import using Open API 3.0

Like (3) ShareShare
ReportReport
Posted on 25 Oct 2022 15:48:35 by 10

According to this link: Open API 3 support the ability to create a custom connecter from an Open API 3.0 .json file is supported automatically since 9/30.  However, still getting the "OpenAPI 3.0 schema definitions are not supported. Please try again with an OpenAPI 2.0 definition" message when attempting to import from a 3.0 file.  This link: https://learn.microsoft.com/en-us/connectors/custom-connectors/define-openapi-definition still contains a box indicating 3.0 is not supported.  So which is it?  And if it should be enabled are there any special settings in the tenant that need to be enabled to allow it to work?

  • jdaniel1 Profile Picture
    81 on 18 Apr 2025 at 20:31:30
    Custom Connector import using Open API 3.0
    Has there every been support for Open API 3.0 yet? This appears to be backlogged item for over a few years now. One Microsoft learn page says it was int he works but here we still are waiting for it. 
  • ApiTrader Profile Picture
    167 on 16 May 2024 at 18:15:58
    Re: Custom Connector import using Open API 3.0

    ChatGPT 4.0 is a great way to transform a Swagger 3.0 to 2.0

  • jhoneyfield Profile Picture
    4 on 08 Apr 2024 at 16:34:39
    Re: Custom Connector import using Open API 3.0

    Big thank you for this! We were able to use Open API 3.1 -> Postman Collection -> Export as Postman Collection 2.1 and Import it directly into Power Automate; worked like a charm. 🙏👏

  • agsb Profile Picture
    2 on 04 Apr 2024 at 06:14:04
    Re: Custom Connector import using Open API 3.0

    Workaround: I made Open API 3 spec, made it into a postman collection and then created the custom connector with the postman collection. Custom connector allows Postman collection import even if it has a Open API spec 3 file. This longer workflow is good enough for me temporarily. clearly the permanent solution is for MS to support import of Open API 3 spec YAML.

  • smalm Profile Picture
    10 on 16 Nov 2022 at 19:17:07
    Re: Custom Connector import using Open API 3.0

    Hi @Anonymous ,

     

    What I've learned is that you can import an OpenAPI 3.0 file (yaml or json) if you are creating the connector through Power Automate (not Power Apps).  Unclear to me why they are different.  That said, the approach is to down convert from 3.0 to 2.0, rather than the platform natively supporting 3.0, so you may run into issues (as I have).  It is in preview after all, but my import had several errors (40+) related to schema resolution and path parameters.  I have not yet had a chance to identify the specifics on the errors and see if there are any tweaks that can be made in the source file to have better success.  FWIW, I've had better success importing my 3.0 files into Postman which supports it natively and then exporting the collection and using that as the source in the "Import a Postman Collection" when creating the custom connector.

  • Community Power Platform Member Profile Picture
    on 15 Nov 2022 at 09:51:39
    Re: Custom Connector import using Open API 3.0

    I have the same issue! I'm curious to if this functionality has actually been released and what settings needs to be enabled to make it work

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Understanding Microsoft Agents - Introductory Session

Confused about how agents work across the Microsoft ecosystem? Register today!

Warren Belz – Community Spotlight

We are honored to recognize Warren Belz as our May 2025 Community…

Congratulations to the April Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard > Power Apps - Building Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 89 Most Valuable Professional

#2
MS.Ragavendar Profile Picture

MS.Ragavendar 60

#3
stampcoin Profile Picture

stampcoin 48

Overall leaderboard