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).

Access to DX Analytics is no longer restricted to API Owners, the entire team can now track the performance of their API Portal.

Previously, our Ruby SDKs were initiating a new connection for each API call. Now, we have made this HTTP connection persistent. Using persistent request allows all server requests to be made through one connection, consequently reducing network latency.

Previously, our PHP SDKs were initiating a new connection for each API call. Now, we have made HTTP connections persistent in Unirest for PHP SDK. Using persistent request allows all server requests to be made through one connection.

We have enhanced the support to call API endpoints via the APIMatic Proxy for API Portals.