Why We Became Big Believers in APIMatic’s API Transformer

Kasey

February 15, 2017

We’ve always held to the belief that the Postman toolchain should be an open ecosystem. It’s why we go out of our way to partner with industry leaders to bring additional features to Postman. A user should never hit a wall due to an unsupported format.  Partnering with developers to expand the Postman toolset ensures that our users have the options in their toolbelt to keep their workflows moving quickly during API development.

Over the past year, APIMatic’s API Transformer tool has been on our radar.
We’re happy to support any API description format that fits into our user’s workflow and we fell in love with how easy API transformer makes converting API documentation into different formats such as Swagger, API Blueprint, and RAML.

We saw an opportunity–by partnering with APIMatic and adding third-party integration with API Transformer, Postman Pro is able to simultaneously convert API documentation to any major formats as it saves them directly in a GitHub repository. Never having to worry about documentation format compatibility will continue to move us towards our goal of an open API ecosystem. This is why we are excited to welcome APIMatic’s API transformer as a Postman integrations partner.

Note: Check out APIMatic’s Unlocking API formats for Postman Collections blog for a more in depth look at this news and an interview with Postman CTO Ankit Sobti.

Here’s how to do it yourself:
To use the API Transformer integration with Postman Pro, first log on to your dashboard via the Postman website and navigate to the integrations section:

Select Dashboard.

Select Integrations.

Important: API Transformer uses a GitHub repository to save its documentation. If you don’t already have a GitHub account, you’ll need to create one and integrate it with Postman Pro.

Click on the APIMatic integration option:

Fill out your GitHub and Collection settings:

APIMatic will then convert the Collection’s documentation to your format of choice and store it in GitHub:

Now you’re all set to start converting your documentation to your chosen format!

Integrations like this would not be possible without the outpouring of support and enthusiasm we see daily from the Postman Community. If you like Postman, please don’t forget to let us know on Twitter, Facebook, or in our Slack channel.