There was a problem with the datetime implementation in AngularJS. 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.

There was a bug in the AngularJS SDK in sending complex types (models) as Form and Body Parameters.

In cases of endpoints which accept model instances as form/body 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.

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.

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