Is it possible to import existing APIs from a Swagger 2.0 definition into Apigee Edge?

Triying Apigee Edge and reading the docs I found: http://apigee.com/docs/api-services/content/build-simple-api-proxy

It seems possible (from the wizard) to import a pre-existing external API will WSDL or APi Bundle to create an API proxy.

Is it possible to do the same using a Swagger spec v. 1.2 or v. 2.0?

Thanks in advance

4 Likes

Hi @Pedro J. Molina .. You cannot do that today. It is on our roadmap though. I am however not sure of the timelines.

2 Likes

Dear @Pedro J. Molina ,

We now have a swagger2api Node.JS based command line tool which will help you create Apigee API Proxies using swagger 2.0 spec. It will create Apigee API Bundles and help you deploy to Apigee Edge out of the box.

For more details please refer here. It’s released few days back and please feel free to share your findings / suggestions / queries if any related to the tool.

PS : As of today, swagger2api tool is not officially supported by Apigee.

Cheers,

Anil Sagar

2 Likes

A command line tool is available to convert swagger spec 2.0 to API Proxies in APIGEE Edge. For more details please check another answer.

Hi @Anil Sagar is this a supported feature now? If not is there a road map to support swagger import in edge?

Check this out - http://docs.apigee.com/api-services/content/build-simple-api-proxy#usingopenapitogenerateproxies-creatingaproxywithopenapi. It has been available for awhile now.

2 Likes

@santanu4g , yes, It is available now. Check @Cladius Fernando answer above.

Just noticed that it is possible to import a swagger based API definition into Edge via the enterprise UI and create an API proxy

Hi @Cladius Fernando is there a corresponding management API as well?

@Anil Sagar @ Google are there any recent updates to the openapi2apigee tool?

Does it support openapi 3.0 specs as well?