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:

• Obtaining consent from user
• Acquiring access token
• Refreshing tokens when they expire
• Making authorized API calls

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.

Improvements have been made to WSDL import by fixing minor bugs, adding new features, and improving on the existing ones in an effort to make it more compliant with the official W3C specification

We have changed the structure of the Angular SDK to break cyclic dependencies. Due to this, the following changes have been made:

• Model deserialization logic has moved out from model files.
• We have added new files ObjectMapper.js and ModelFactory.js to the SDK.
• BaseModel is now being used to assign values to model properties (when model class is directly instantiated)
• BaseController has been added to the SDK.

Please generate your SDK again to get the improved code.

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.

Since we're always working on improving our generated SDK's, today we're announcing some major work done on the Angular.js SDK.

• Angular.js generated code is now standard compliant.
• The standard we're using is John Papa's Angular1 Style Guide.
• The linter can be run from the command-line by using the command jshint <folder-name-to-lint>.
• The configuration file for the linter will be included with the SDK from now.

Please generated your SDK again to get the standard compliant code.

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.

We've made an improvement to how model properties are now generated in the code. The generated SDK now contains both camel case-d version of the property name and the actual property name (where applicable).
Read on to find more details about the change.

Please generate your SDK again to get the improved code.

NodeJS SDKs will now return promises in endpoint calls, as an alternative to accepting callbacks.

• We use ES6 Promises which is based on Promises/A+ and is interoperable with most Promise-based implementations.
• Callbacks are still supported (for backward-compatibility) but are now optional.

Re-generate your NodeJS SDK to get the new Promise-enabled SDK implementation now.