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.

We've made API Copilot a first-class part of your portal. It has moved out of a floating overlay and into a dedicated panel beside your docs, and it's now reachable from more places than ever. On top of that, your portal can now open directly into it: with the new API Copilot Home (Beta), developers land in a conversation and start integrating by asking a question instead of browsing the docs for where to begin.

The C# v4 SDK (beta) has picked up a wave of improvements over the past few weeks, spanning streaming, dependency injection, documentation, error handling, and file handling.

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 increasingly don't read API documentation page by page — they build with AI coding tools like Claude Code, Cursor, and VS Code. And these tools are only as good as the context they have. Without accurate, current knowledge of your API, they guess: invented endpoints, stale parameters, and integration code that takes hours to hand-fix.

We've brought your API into that workflow. Right from your developer portal, developers can now load your full API context — docs, SDKs, code samples, and setup instructions — into their AI coding environments in a single step, using Context Plugins.

Our SDKs are now more AI ready than ever. Model reference docs now show idiomatic, language-specific code samples, complete with imports, instead of serialized payloads. They cover how to initialize a structure, reference an enum value, and catch errors across all seven SDK languages.

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.

The new C# SDK is now available in beta. You can generate it today using the APIMatic CLI. Try it out and share your feedback with us.