Complete support for multiple responses has been added to API Transformer across all major formats like OpenAPI, RAML, API Blueprint, etc. This means a major reduction in loss of information related to responses when converting between various formats. Note, that these changes can also affect how your import in the Dashboard works.
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.
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.
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.
We have added support for adding contact information of the organization maintaining the API in our API editor.
We've added the ability to call API endpoints directly from the browser in our Developer Experience Portal for APIs. This is provided as an alternative to calling the API via our proxy.
Our Android, .Net, Go, Java, NodeJS, PHP, Python and Ruby SDKs now allow skipping verification of SSL certificates. To do this enable the CodeGen Setting Allow Skipping Certificate Verification and then set the corresponding configuration variable in the respective SDK.
We've rewritten our Developer Experience portal and are releasing it as a major version. The new version introduces several new features in addition to bug fixes to some long-standing issues.
Check out the changes and how to migrate to the new portal.
We have added a new CodeGen setting to allow disabling linting in our SDKs. If you would like to benefit from this feature then please enable the setting and generate your SDKs again.
Our Postman exporters (both versions 1.0 and 2.0) now support collection variables to better represent requests in cases where multiple servers are involved.
Our GO SDK has been revamped pertaining to multiple bug fixes and new features.
You can now use multiple base URLs in your API description using the new Server Configuration. This feature allows you to
A property is nullable if it allows sending null (in case of JSON/YAML, etc.) or nil (in case of XML) as value. Several API description formats like Open API, RAML, etc. has support for nullable properties. Transformer now also supports this property and you can convert between different formats without losing this information.
Several API description formats like Swagger, RAML, WSDL, WADL, etc. support various kinds of validation keywords to restrict and validate instance values based on their type. Support for these validation keywords has now been added to Transformer. You can now convert between any of these formats without losing information for these keywords.
We have now added support for multiple datetime formats in our PHP SDKs. The following formats are supported:
Mon, 15 Jun 2009 20:45:30 GMT2016-03-13T12:52:32.123Z1480809600Multiple formats are now supported for Array serialisation in form and query parameters. Formats supported include UnIndexed, Indexed, Plain, CSV, PSV, TSV.
This settings can be set using our API Blueprint CodeGen setting extension named ARRAYSERIALIZATION.
We have now added support for multiple datetime formats in our Java and Android SDKs. The following formats are supported:
Mon, 15 Jun 2009 20:45:30 GMT2016-03-13T12:52:32.123Z1480809600Postman recently added a new export format i.e. Postman Collection Format v2.1. Along with this, they also improved and added new authentication mechanisms in the older versions (1.0, 2.0). Our parsers have been updated to accommodate all these changes.
WADL components support references to other components using Cross Referencing as per the specification at https://www.w3.org/Submission/wadl/#x3-60002.1 . The support was this was missing from our parsers previously and has now been added! Please transform your files again to get the latest changes.
We are excited to announce the latest addition to our long list of supported platforms. Our C# section now has a new template for a .NET Standard library in addition to the already supported PCL and UWP templates. This library targets .Net Standard 1.3.
Usage of discriminators is already supported by our code generation engine. We are happy to announce that now support for using discriminators has also been added to AngularJS SDK.
Please generate your SDK again if you want to use this feature.
OAuth 2.0 support was recently added to the API Editor and Code Generation engine. Now the support is added to Transformer as well as import/export in the Dashboard.
Usage of discriminators is already supported by our code generation engine. We are happy to announce that now support for using discriminators has also been added to Node.
Please generate your SDK again if you want to use this feature.
Swagger supports response and schema examples as can be seen from their documentation on adding examples. If your API description contains response or schema examples, then the exported Swagger file will be populated with these examples.
Our API editor and Code Generation engine now supports OAuth 2.0 for authentication in the generated SDKs.
OAuth 2 enabled SDKs will help developers in:
You can read more about OAuth 2.0 in APIMatic editor and Code Generation engine here.
You can now set Composer Package Name for PHP SDKs being generated.
This will affect the name generated in the composer.json file. Leaving it empty will generate the a fallback package name based on your API name.
Good news! You can now export your existing API description files to WSDL. The generated WSDL can be utilized in generating server interfaces using VS developer tools in addition to other benefits. The WSDL generated follows the WSDL 1.1 format specified at https://www.w3.org/TR/wsdl.
Now you can upload a ZIP file containing your Postman Collection file along with any Postman Environment Files. That way we will extract values for your environment variables from the Environment files and give a better output during conversions on the Transformer or when importing APIs to your Manage APIs page. Support for Postman data dump files has now been added as well.
NodeJS SDKs will now return promises in endpoint calls, as an alternative to accepting callbacks.
Re-generate your NodeJS SDK to get the new Promise-enabled SDK implementation now.
NodeJS SDKs can now optionally preserve additional properties returned in the response. This setting can be enabled via Settings > CodeGen Settings page in the API editor and turning on the Enable Additional Model Properties flag.
APIMatic Code Generation engine now supports polymorphic responses with the help of a discriminator field.
Check out the Discriminator documentation to get started.
If you have a Swagger 1.2 API description file split into Resource Listing and API Declaration files, you can import/convert it using a ZIP file. Previously, such API description file could only be converted/imported by providing the Resource Listing file via a URL where all API Declaration files were located relative to this URL.
Multiple formats are now supported for Array serialisation in form and query parameters. Formats supported include UnIndexed, Indexed, Plain, CSV, PSV, TSV.
This settings can be set using our API Blueprint CodeGen setting extension named ARRAYSERIALIZATION.
Swagger makes use of a property discriminator to support polymorphism in custom types. We have now added support for this property in our system. We also offer an extension that will allow you to specify a custom value for the discriminator to override its default value.
We have now added support for additional properties in models in the CSharp SDK. The additional properties are deserialized and stored in a dictionary inside the model.
This can be enabled via navigating to the Settings > CodeGen Settings page in the API editor and enabling the Enable Additional Model Properties flag.
APIMATIC now offers you a swagger extension to specify Server Configuration details within your Swagger file. When you import this file, we will extract the relevant server configuration information from this extension.
Server configurations can be used to create multiple environments, multiple servers that can be used with specific endpoints and server URLs with template parameters. You can view more details about these configurations at Server Configuration. We have added support for an extension to help you specify this information without having to manually add it through the editor everytime you import your Swagger file. For more details on this extension please see Swagger Server Configuration Extension
We have now added support for multiple datetime formats in our Angular SDKs. The following formats are supported:
(Mon, 15 Jun 2009 20:45:30 GMT)(2016-03-13T12:52:32.123Z)(1480809600)If you have WADL/WSDL files with references to external schema files that exist relative to your root file, then you can import/convert them successfully. These files may be accessible by URL or a ZIP file.
We have now added support for multiple datetime formats in our SDKs. The following formats are supported:
(Mon, 15 Jun 2009 20:45:30 GMT)(2016-03-13T12:52:32.123Z)(1480809600)Node JS SDKs now come with retries for requests. We allow retries for the following cases:
Re-generate your Node JS SDKs now to get this new feature.
Exception Classes support has been added to Node SDKs. Generate your SDK again to get this new feature!
NodeJS SDKs now have both Local(endpoint specific) and Global Level (API specific) errors implemented as specified in the API Descriptions.
SDKs generated by APIMATIC now support logging events!
You can now use multiple base URLs in your API description using the new Server Configuration. This feature allows you to
Starting today, we are going to maintain an awesome Changelog for APIMATIC. :)
Follow this changelog to stay up-to-date with