OpenAPI 3 support for custom connectors
Important
This content is archived and is not being updated. For the latest documentation, go to Microsoft Dataverse Developer Guide. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, marketers, or analysts, automatically | 
Sep 30, 2022 |
- |
Business value
Support for the latest industry standard OpenAPI 3 specification is being added to our platform for developing custom connectors. This new capability removes the need to convert OpenAPI 3 specifications to OpenAPI 2 format thereby increasing developers' productivity.
Feature details
The OpenAPI Specification refers to a standard for describing HTTP APIs in a machine-readable format and is currently the most widely used standard for API description. The OpenAPI 2.0 Specification is the first widely adopted version of the specification and is the same as Swagger 2.0 - the specification as published by SmartBear Software. OpenAPI 3.0 was released in July 2017 as the first version of the specification with industry participation. That specification was published by the OpenAPI Initiative of which Microsoft is a founding member. The version 3.0 specification is not compatible with version 2.0 and is a major revamp. OpenAPI 3.1 is the latest revision of the specification.
Power Platform uses OpenAPI to describe the functionality of a connector (either custom or certified). The platform allows various components (like the flow designer) to understand the various actions/triggers supported by the connector.
With this release, we're adding support for the OpenAPI 3 Specification so that developers can build custom connectors with the OpenAPI 3 specifications of their APIs. The platform will convert the OpenAPI 3 specifications into OpenAPI 2.0 format, ensuring that existing tools continue to work. There is no change in the current experience.