To improve clarity and onboarding, all client initialization code samples now include relevant import statements. This update makes it easier for developers to understand and use the SDKs, eliminating guesswork around class and function origins in docs and READMEs.
Sonatype has announced the retirement of OSSRH (including oss.sonatype.org and s01.oss.sonatype.org) on June 30, 2025. All Java packages must be published via the Sonatype Central Portal moving forward.
To support this change, APIMatic has updated the Java SDK publishing workflow.
APIMatic now supports four widely-used pagination strategies in Java SDKs: Offset, Page, Cursor, and Link based pagination. This enhancement provides a seamless and unified way to consume paginated API responses, regardless of the underlying mechanism.
The SDKs now support passing complex objects, including non-scalar types and collections, as HTTP header parameters in the request.
We’re introducing support for typed additional model properties across all SDKs, enhancing type safety and alignment with OpenAPI specifications.
We have incorporated oneOf and anyOf discriminator and meta case support in Java SDKs to enable seamless value mapping. This enhancement enhances the versatility and ease of use of our Java SDKs, allowing developers to efficiently handle complex data structures and streamline their workflow.
The generated code samples are now idiomatic with no errors. This improves the developer experience by allowing developers to run the code samples without any error in their applications and to get started quickly.
APIMatic has introduced core libraries to provide a stable runtime that powers all functionality of our SDKs. In this release, we have revamped our Java SDKs to improve the code quality and provide better test coverage.
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.
OpenAPI Specification allows you to add an object type in oneOf and anyOf in Java SDKs. Defining an object type means any key/value pair is accepted. Object type in Java means it can refer to any instance, as Object is the root class. Therefore, this change enforces that for any object type case falling under oneOf and anyOf, the Java SDK will treat it as Map.