74 posts tagged with "New Feature"

Support for union types and other type constructs (oneOf, anyOf, not) has now been added to API Transformer and can also affect how your import in the Dashboard works. Re-transform/re-import your files to get these latest changes. Learn more about how (and if) these changes will affect you if you use any of these constructs in your API specification file.

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.

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

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

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 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.

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 have added information about the minimum required Java version to the pom.xml file in Java projects. The enforced version has not changed and is still Java 7. Previously if the user tried to use our Java SDK with a lower version, they would face compilation failure and receive error messages that were sometimes ambiguous. Now a Maven build failure is caused which clearly informs the user that the problem is with the version of Java being used. To benefit from this change, please generate your Java SDKs again.