There was a bug being generated in the package.json file with Node SDKs that had no test cases. The bug was related to trailing commas being generated in the package file's dependencies. Causing the package file to not resolve dependencies. The bug has been fixed now.

Please regenerate your NodeJS SDK to get the bug fix

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!

• Logging-enabled SDKs will log important events in the API lifecycle to the console, log file or another logging backend.
• Logging backends are configurable. You can even plug-in a logging service like Loggly or Sentry into your SDKs.
• Easily monitor your SDK usage and find bugs when they occur.

A bug in PHP SDKs being generated lead to custom Error Exception Models not being deserialized properly from the response when an API error occurred. This was caused by an error in the unbox() function in the custom Exception class. It has now been fixed.

If you were using custom Error Exceptions, then please re-generate your PHP SDKs to get the fix.

Code styling within NodeJS SDKs is now improved. For everyone using our Node SDK with Superagent as the HTTP Client, there was a bug in the handling of response when response type is binary. It has been fixed so you can get the bug-fix by generating the SDK again.

Object Instantiation in Custom Types files have now been improved. Only those properties (of the object) that are set in client code will be initialized and instantiated in the SDK. This will prevent any property from being undefined

A logical error in the PHP SDKs being generated lead to a variable, _httpContext, being undefined in some cases. This resulted in a Fatal error when an APIException was expected to be thrown.

Please regenerate your PHP SDK to get the bug fix.

A circular reference problem was fixed in the Python SDKs. This should have only existed if your API description had a DateTime property in a model.

Please regenerate your Python SDK to get the bug fix.

An unexpected additional ')' existed in the generated Ruby code if the SDK had a Datetime property in a model. The syntax error was eliminated by removing this bracket.

Please regenerate your Ruby SDK to get the bug fix.

You can now use multiple base URLs in your API description using the new Server Configuration. This feature allows you to

• Vary the Base URL between endpoints.
• Create multiple Environments and define different Base URLs for them.
• Templatize Base URL to allow for configuration using parameters in the client.