As part of our ongoing work on support for multiple responses, we have released some related changes in RAML 1.0 that may change how your imported API entity looks like.

API Transformer now preserves XML examples and XML serialization attributes like XML node name, prefix, namespace, etc. which reduces loss of information when converting between popular formats that support XML like OAS, RAML, WSDL, WADL, etc.

We have updated the jackson-databind library in our Java SDKs due to a vulnerability reported recently. Please generate a new Java SDK from APIMatic to get the fix.

Information about array responses or primitive type responses was being incorrectly represented or entirely missed. We have released some fixes to improve on this.

You can now export GraphQL schema files from your REST/SOAP APIs using API Transformer.

We've updated the Jackson Data-bind library in our Java SDKs due to a vulnerability reported recently. Please generate a new Java SDK from APIMatic to get the fix.

API Transformer and other APIMatic products now support import and export of Insomnia Export Format files that are in YAML format.

Improvements have been made to Postman import/export of versions 1.0, 2.0 that are expected to be released in the coming few days.

We've made several improvements to our Java SDK, resulting in considerable resource savings and speed-up, in case of blocking API calls. To benefit from these improvements, please generate your SDKs again.

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.