We are happy to announce that our Android and Java SDKs now use the better and faster OkHttp client.

We have updated our Android SDKs to use version 3.0.1 of the Android Plugin for Gradle, and have upgraded the Gradle version to 4.1.

The minimum SDK version has been raised to 16 and the target SDK version has been raised to 26.

Please regenerate your Android SDKs if you wish to get these changes.

Our GO SDK has been revamped pertaining to multiple bug fixes and new features.

• It now supports OAuth 2.0 Bearer Token for authentication in the generated SDKs.
• It now has a base client that can be used as a single point of entry for the SDK.
• The singleton architecture for clients has been removed to ease up the use in multiple user environments.
• Numerous bug fixes and improvements.

You can now use multiple base URLs in your API description using the new Server Configuration. This feature allows you to

• Vary the Base URL between endpoints.
• Create multiple Environments and define different Base URLs for them.
• Templatize Base URL to allow for configuration using parameters in the client.

Our Transformer tool has been supporting HTTP Archive (HAR) format for a long time now. With the addition of new features to our APIMatic tool (e.g. support of multiple servers), there were a few updates required in our HAR parsers. In this regard, several missing features were added and some bugs were also fixed.

A property is nullable if it allows sending null (in case of JSON/YAML, etc.) or nil (in case of XML) as value. Several API description formats like Open API, RAML, etc. has support for nullable properties. Transformer now also supports this property and you can convert between different formats without losing this information.

Several API description formats like Swagger, RAML, WSDL, WADL, etc. support various kinds of validation keywords to restrict and validate instance values based on their type. Support for these validation keywords has now been added to Transformer. You can now convert between any of these formats without losing information for these keywords.

There was a bug in the implementation of the Unindexed and Plain array serialization formats in Ruby SDKs. Arrays of models were not being properly encoded as form fields for the two mentioned formats.

Additionally, a bug in the initialization of inherited models caused duplication in fields with names longer than one word.

Both these bugs have now been fixed. Please regenerate your Ruby SDKs to get this fix.

There was a bug in the implementation of the Unindexed and Plain array serialization formats in Python SDKs. Arrays of models were not being properly encoded as form fields for the two mentioned array serialization formats. The bug has now been fixed.

Please regenerate your Python SDKs to get this fix.

There was a problem in the handling of 'optional' DateTime fields in models. The issue has now been resolved.

Please regenerate your PHP SDKs to get this fix.