There was a bug in the Node.js SDK in sending complex types (models) as Form Parameters.

In cases of endpoints which accept model instances as form parameters, models were not being serialized properly before making the endpoint call. This resulted in camel-cased field values being passed, disregarding the correct API names.

This behavior has now been fixed. Please generate your SDK again to get the fix.

There was a problem with the datetime implementation in Node.js. Date/datetime strings were not correctly converted into objects. Instead, strings were being sent and received within the SDK. This problem has now been fixed.

Please generate your SDK again to get this fix.

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.

• Discriminator is a field that is used to differentiate between a parent model and models that inherit from it.
• The response is deserialized into the parent model or one of its child classes by inspecting the discriminator field's value in the response.
• Using a discriminator field, you can build leaner models by not having to build unions of fields needed by a polymorphic response.

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:

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