Changelog

Postman recently introduced API Key authentication in its latest app and corresponding Postman Collection versions. API Transformer and other APIMatic products now support this feature for all import/export purposes. In addition to this, we now also handle disabled request bodies (another new feature introduced by Postman) when importing Collection files.

We’ve updated the version of SuperAgent library used in our Node.js SDK to fix a moderate severity vulnerability. We’ve also made some other smaller fixes.

Please generate a new Node.js SDK to receive these fixes.

We’ve fixed an issue in SDKs where HTTP redirections were not being handled properly. Please generate new SDKs to receive the fixes.

We’ve added logging to our Java SDKs. Logging-enabled SDKs will log important events in the API lifecycle for troubleshooting or debugging later.

Both versions of RAML (0.8, 1.0) support XML examples and XML schema definitions. Previously, we supported only JSON examples and JSON schema definitions found in RAML input files. Now, however, we support parsing of XML examples and XML schema definitions as well.

We’ve updated our SDKs that use OAuth 2 Client Credential Flow to enable automatic re-authorization of the client when the OAuth token is expired.

We’ve added the ability to programmatically configure the logger used in the NodeJS SDK. You can now disable logging or add a custom log handler during runtime.

Resource types and traits are an integral part of RAML. We have been working hard in improving our support for them in order to improve your RAML conversion experience on API Transformer. Majority of the improvements target RAML v1.0 while some of them also target v0.8.

OpenAPI/Swagger allows you to include external documentation in your API description for various components. API Transformer now supports conversion of this information for both import/export of OpenAPI/Swagger files.

We’ve updated the version for jackson-databind, a dependency of our Java SDK, due to a vulnerability found in the previous version of the library. We recommend that you generate and redeploy your Java SDK to get the fix.