Generated TypeScript SDKs now support streaming API responses over Server-Sent Events (SSE). When an operation streams its response instead of returning a single buffered body, the SDK exposes it as a typed, async-iterable stream that you consume with a familiar for await...of loop.
The new C# v4 SDKs now support pagination, covering the four widely-used strategies: Offset, Page, Cursor, and Link based pagination. This provides a seamless and unified way to consume paginated API responses, regardless of the underlying mechanism.
Generated C# v4 SDKs now identify themselves on every API call. Each request carries a short User-Agent plus a set of structured X-APIMatic-* headers, and non-GET requests automatically include a retry-safe Idempotency-Key.
Previously, in order for an API provider to use Context Plugins for their API, their SDKs had to be published to a public package manager such as npm, NuGet, or PyPI. That left teams whose SDKs live behind a private host — internal APIs, partner integrations, or APIs that aren't yet ready for public distribution — without a way to offer the same AI-assisted integration experience.
We've now added self-hosted SDK support in Context Plugins. Instead of pulling the SDK from a package manager, the AI agent downloads the SDK package from your portal, installs it locally in the developer's workspace, and wires it into their project — all without the SDK ever needing to be published.
Developers frequently switch between APIMatic documentation and external AI chat tools to understand APIs — a workflow that required manually copying page content and pasting it each time. This release eliminates that friction entirely.
We've introduced the AI Assist Menu, a one-click dropdown available on every documentation page that sends the current page's content directly to your preferred AI tool as context.
We've added new validation and linting rules that flag API entity names exceeding 100 characters in OpenAPI specifications. Names exceeding 100 characters now produce an Error-severity violation that blocks Code Generation, Docs Generation, and Portal Generation.
The Developer Portal's toc.yml now supports a custom slug option, giving you full control over the URL paths generated for your documentation pages.
A new boolean property disableTryItOut has been introduced at the environment level within the Server Configuration, allowing API providers to disable the interactive Try It Out functionality on the API portal for specific environments.
We've expanded the openapi-v3-apimatic-linting,openapi-v3-codegen-linting, openapi-v3-standard-linting, and openapi-v3-standards-validation rulesets with new linting and validation rules covering Pagination, Webhooks, and Callbacks.
Managing event-driven APIs just got simpler. The Developer Portal now lets you include all webhooks or callbacks from a group directly in toc.yml with a single webhook-group or callback-group entry — no more listing every event by hand.