Enhanced SDK documentation for enumeration casing across all supported languages. This update ensures consistent and accurate environment enumeration representation in the Getting Started section for all languages. We also improved enum casing in the model documentation section for Java.
We've enhanced SDK documentation completeness and alignment with the actual implementation for Java, .NET, and Go SDKs. This update includes model documentation for parameter collection classes and updated endpoint documentation that presents collected parameters as unified model references, resulting in clearer and more accurate SDK documentation.
We have improved error handling in PHP, TypeScript, Java, .NET, and Go code samples to make it clearer, more consistent, and easier to handle typed errors, while still exposing response metadata like status codes and headers.
We have eliminated transitive javax.* dependencies from apimatic/core for better compatibility across Java versions.
We’ve added support for configuring proxy servers in the generated Java and Ruby SDKs.
To improve clarity and onboarding, all client initialization code samples now include relevant code blocks along with 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.
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.