APIMatic SDKs now come with core libraries that improve code quality, reduce SDK size, and provide better test coverage for all SDKs.

TypeScript SDKs now support complex query parameters that allow you to send complex types and arrays/maps of complex types in query strings.

​ We have added the support of multiline in the text area for string input in the API Code Playground. ​

​ In the Developer Portal, users can update the heading, body and code fonts. For the hosted portal, the user can select list of fonts available on the portal editor. For the self-hosted portal, the web font URL can be provided as part of the portal settings in the build file.

Hosted Portal Users​

In the API developer portal, the list of available fonts in the portal editor is updated for code, body and headings.

For Python SDKs, the test runner used to run unit tests was Nose. As its maintenance support is coming to an end, APIMatic has replaced nose with Pytest for all future test suites.

You can now generate a build input for existing Portals created using the UI workflow. The build input corresponds to the published or unpublished version of the Portal and enables you to:

1. Create a backup for the Portal.
2. Migrate from the UI workflow to the docs as code workflow.

For details on description of the build input, go to APIMatic Build Input Documentation.

APIMatic now exports any data available for a schema that also uses $ref to reference another schema definition, by placing the reference and the sibling data within the allOf construct.

​ We have added support of read-only and write-only properties in the API Developer Portal. The read-only and write-only tags have been changed to Response Only and Request Only respectively.

We have provided the Discriminator support via the API portal.

We are pleased to announce support for read-only and write-only properties in API Transformer which is one of the commonly used features of OpenAPI specification documents (v2.0 and above).