With this release, you can make your API documentation AI-ready with automatic llms.txt generation, streamline API Portal development with powerful new CLI commands, and handle paginated responses seamlessly across Java, C#, Ruby, and Python SDKs.
We've also made the API Portal navigation more customizable, added granular auto-fix controls to our VS Code extension, and updated Java SDK publishing to support Sonatype's new Central Portal, ensuring your workflows stay current with industry changes.
You can now automatically generate llms.txt and llms-full.txt files in your API Portals.
This means tools like GitHub Copilot, ChatGPT, Claude, and Cursor can better understand and interact with your API Documentation.
APIMatic now provides out-of-the-box support for llms.txt, a new web standard designed to make developer documentation accessible to AI assistants. These files are similar to sitemap.xml and robots.txt, but tailored for LLMs, and are generated automatically when using the Docs-as-Code workflow
π Read the changelog for details.
You can now streamline your Docs-as-Code workflow with a new set of APIMatic CLI commands.
With these commands, you can scaffold new projects, create API recipes, generate a table of contents, and preview changes in real-time:
π Check out the CLI reference documentation to learn more about these commands.
To install or upgrade the CLI, run the following command:
π¦ Java SDK Publishing Updated for Sonatype Central Portal Migration
You can now publish Java SDKs using the new Sonatype Central Portal integration.
APIMatic has updated the Java SDK publishing flow to align with Sonatype's retirement of OSSRH on June 30, 2025. Your Java packages now publish directly to the Sonatype Central Portal, ensuring a seamless transition.
π See the changelog for details.
You can now auto-fix specific rule violations in your API definition either by rule or by instance. This gives you greater control when cleaning up your OpenAPI specifications.
With the release of v1.0.4 of the APIMatic VS Code Extension, we've enhanced the auto-fix functionality to support granular fixes. Previously, auto-fixes were applied across the entire API workspace but now, you can:
This feature enables precise issue resolution, letting you fix only what needs fixing.
π Read the changelog for more details
You can now control how your developer portalβs left navigation is structured and displayed.
This means a more tailored, intuitive experience for your users, whether you prefer dropdowns, collapsible sections, or always-on navigation.
Weβve introduced new options for customising the Left Navigation Bar, including two navigation modes and three layout variations. The standard mode displays all navigation items in a vertical tree structure, while the dropdown mode groups top-level items in a dropdown menu, showing child items only for the selected section. You can also choose how first-level sections behave on load with the basic, expanded, or collapsed layout variations. Together, these settings give you precise control over how your documentation is organised and experienced.
You can now navigate paginated API responses using a unified, OpenAPI-driven interface in the Java, C#, Ruby and Python SDKs. This means less boilerplate code and consistent pagination handling across all your SDKs, regardless of the pagination style.
Configure pagination in your OpenAPI definition using the x-pagination extension. Your SDKs then automatically provide intuitive, language-specific helpers(both sync and async) for iterating over data.
For example, in the Java SDK, paginated endpoints return a PagedFlux<Item, PagedResponse<Item, Page>>, allowing you to:
This ensures a consistent developer experience across pagination strategies like cursor, offset, or link-based pagination.
π Learn more about the pagination in SDKs.
Your feedback makes our product better.
Follow us on LinkedIn to stay updated with the latest news from APIMatic!