36 posts tagged with "New"

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

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.

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

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.

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.

APIMatic CodeGen has now added support to configure the default Faraday connection with available Faraday adapters in Ruby SDKs.

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.