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.
Introducing Discriminator Configuration using the API Portal
We have provided the Discriminator support via the API portal.
Added Support for Read-Only and Write-Only Properties in API Transformer
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).
Enabling DX Analytics for All Team Members Within the API Portal
Access to DX Analytics is no longer restricted to API Owners, the entire team can now track the performance of their API Portal.
Adding Support for Persistent Connections in Ruby SDK
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.
Introducing Persistent HTTP Connections in Unirest for PHP
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.
Introducing APIMatic Proxy 2.0 for Self-hosted Portals and XML Calls
We have enhanced the support to call API endpoints via the APIMatic Proxy for API Portals.
JSON Object Type Support in SDKs
We have added support for a new JSON Object type in all our SDKs.
Enable/Disable Retries per Endpoint for any HTTP Method
By default, our SDKs support retries for idempotent HTTP requests only. A flag is added at endpoint level which, when enabled, allows retries for non-idempotent HTTP requests as well.
Adding Support for Optional and Nullable Fields in a Model in Python SDKs
In the improved Python SDK, fields of a custom type can now differentiate between a nullable value and a missing value and will operate according to the behavior of the type specified. This way you can either pass a value that corresponds to the type specified, use null
as a value or skip the field altogether depending upon the defined behavior of the field.