By default, APIMatic generated SDKs throw a generic error response on every failed API call. Now, you can customize these error responses by providing placeholders that populate at runtime.

APIMatic SDKs have improved efficiency of internal processes in code sample generation. After this change, generated code samples may slightly change when SDKs are regenerated but there is no functional impact of this change.

We have added some improvements to our existing support for nullable types in API Transformer, in particular when arrays are also involved. These improvements target transformations involving the OpenAPI (v3.0), RAML (v0.8 ,v1.0), Postman (v1.0, v2.0), and Insomnia formats and will ensure reduced loss of information and improved overall quality of the output.

APIMatic has introduced core libraries to provide a stable runtime that powers all functionality of our SDKs. In this release, we have revamped our Ruby SDKs to improve the code quality and provide better test coverage.

APIMatic's developer portal now offers a better visibilty experience with UI changes to the left naviagtion bar. These include indentation of menu items, bold titles and highlighting of selected section in the navigation bar.

APIMatic has introduced core library to provide a stable runtime that powers all functionality of our SDKs. In this release, we have revamped our C# SDKs to improve the code quality and provide better test coverage.

We are pleased to announce that we have added the support for password schema format in API Transformer so that you can now transform between OpenAPI specification versions (v2.0 and above) without losing this information.

We have added a separate section in the "Try it Out" console for code request and response body. Now the user should be able to preview the code sample making the API request after getting a response in the code sample section of the developer portal.

We have improved the font settings management in the API developer portal for better usability and visibility.

We have added an autogenerated table of content in the documentation that contains all the top level headings and sub-headings. Using a table of contents make it easy to navigate through multiple sections across the documentation page. It also helps in getting a high level idea of what are the contents of the documentation before getting into the detail of it.