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.
We have added support for a new JSON Object type in all our SDKs.
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.
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.
OAS allows you to set optional/required properties in models. While serializing a model, optional properties will be omitted if the value of property is not set (i.e. initialized with null) and, required properties will be serialized in any case. This is a case of factoring schema in oneOf/anyOf. Now with this support, you can define properties with the same names but with different optional/required constraints in request/response of an endpoint.
APIMatic CodeGen has now added support to configure the default Faraday connection with available Faraday adapters in Ruby SDKs.
APIMatic’s Self Hosted Portal offering has been augmented with the following enhancements:
APIMatic announces the support for multiple authenticaion schemes in Python SDKs. With the new design, it has become quite easy to configure multiple authentication schemes per SDK. All of the auth managers are instantiated at the start during the client initialization. After that their relevant auth managers can be used to apply auth schemes per endpoint as required in SDK.