X

The Integration blog covers the latest in product updates, best practices, customer stories, and more.

  • January 20, 2020

Accelerate API Integration With the Power of OpenAPI

The OpenAPI Specification defines a standard, programming language-agnostic interface description for REST APIs. We are pleased to announce OpenAPI support in Oracle integration cloud REST adapter.

What this means is that all OIC integration flows with a REST trigger will publish an openAPI to describe its metadata. This machine readable description of the API will allow interactive API explorers as well as the developers to consume OIC integration flows with ease.

On activation of an integration flow, the metadata link will show the new option to display the openAPI in addition to the swagger URL.


We are also introducing an interactive openAPI explorer in the Oracle integration cloud REST adapter wizard that will help integration developers to explore and consume APIs described in openAPI format with a few clicks. This option can be selected to provide openAPI 1.0/2.0 (a.k.a. Swagger) as well as an openAPI 3.0 spec. 

Steps to consume an API described in openAPI:

  • Create a REST Adapter connection with Invoke role and select the new option and provide the link to the openAPI in the ‘Connection URL’


  • Use this connection within an integration flow. The REST adapter wizard will have an API explorer based on the openAPI description provided in the connection. Browse and select the required path and operation to complete the wizard.  

* This feature is currently in controlled availability. If you are eager to try this out, enable the feature with id oic.cloudadapter.adapter.rest.openapiurl using this blog.

OpenAPI is a rich specification. Currently some of the constructs in openAPI cannot be consumed. Please consult the oracle documentation for information about the constraints. 

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.