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.

We're releasing a new version of our Developer Experience Portal which improves docs generation for all SDKs. This is a breaking change and requires manual migration. Check out all the changes below.

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.

We have made some minor improvements to synchronization in our Java and Android SDKs. To benefit from these improvements, please generate your SDKs again.

For those of you looking to convert your Insomnia files, we have good news! Yes, we now support Insomnia Export Format Specification v3.0 in our API Transformer. With this feature, you can now convert your existing Insomnia files to any of our supported formats or vice versa.

We have added a new CodeGen setting that allows you to specify a list of words that Code Generation will not split when converting identifiers from API specification to language-specific identifiers. This is useful for declaring brand names such as APIMatic.

E.g. if you provide the words apimatic and vmware in your the list, APIMaticandvmWare becomes ApimaticAndVmware or apimatic_and_vmware, depending on the place of use.

For the past few months, we have been hard at work improving API Transformer to give our users good quality output for any of their conversions. This changelog highlights all improvements made and new features added which we plan to release in a few weeks from now. To get full advantage of these improvements, some of the users who import from various formats like OpenAPI/Swagger, API Blueprint, etc. may need to regenerate their portal/SDKs.