​ We’ve just released v1.0.4 of the APIMatic VS Code Extension, and it introduces a major developer experience improvement: individual rules auto fixing for validation and linting issues.

APIMatic now supports four widely-used pagination strategies in Ruby 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.

APIMatic now supports four widely-used pagination strategies in .NET 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.

We’re excited to announce support for generating llms.txt and llms-full.txt files as part of your developer portal. It enables tools like Cursor, GitHub Copilot, ChatGPT, and Claude to quickly understand your documentation.

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.

You can now configure layout within the theme object of your portal. This gives you precise, declarative control over container alignment and maximum width—enabling cleaner, more responsive layouts with minimal effort.

You can now customize the behavior and appearance of the Left Navigation Bar in your developer portal. The new options include two navigation modes and three layout variations that give you more control over how navigation is structured and displayed.

APIMatic now supports four widely-used pagination strategies in Python 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 latest update allows publishing source code without tags using an existing profile, with improved log visibility. It also enables source code publishing alongside language configurations without requiring changes to package publishing settings, streamlining the process. Additionally, the retention period for logs and generated SDKs has been significantly extended.

We’ve upgraded the underlying infrastructure of our Docs as Code API to improve its performance. We've also shipped several improvements related to error messages to streamline your CI/CD pipelines and make troubleshooting easier. Below you’ll find a quick overview of what’s changed and how to adapt your integrations.