Skip to main content

· One min read

There was a bug in the index file of the generated SDK. The import for configuration.js was not handled correctly. This bug was causing trouble in using the properties and functions exported from configuration.js.

You may generate your SDK again to get this bug fix.

· One min read

We encountered an error with custom types import in our Node SDK (with test cases). Custom Types which had spaces in between 2 words like Custom Type, or any special characters in their name were not being generated correctly. Causing the SDK to break.

This bug has been fixed now. Please regenerate your SDK if you encountered this bug.

· One min read

Node JS SDKs now come with retries for requests. We allow retries for the following cases:

  • GET requests only.
  • General connection errors.
  • Timeout errors.
  • DNS address resolution failure errors.

Re-generate your Node JS SDKs now to get this new feature.

· One min read

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

· One min read

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.

· One min read

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.