AsyncAPI channel · Sarvam AI · Sarvam AI Chat Completions Streaming (HTTP + SSE)

/v1/chat/completions

Chat completion SSE stream. The client opens this channel by issuing `POST /v1/chat/completions` with `Content-Type: application/json`, `api-subscription-key` header, and a JSON body containing `stream: true`. The server responds with `Content-Type: text/event-stream` and emits a sequence of `data:` lines, each carrying one JSON-serialized `chat.completion.chunk` object, followed by a final `data:

Provider: Sarvam AI AsyncAPI: v2.6.0 Spec: Sarvam AI Chat Completions Streaming (HTTP + SSE) Operations: 1 Messages: 1

Channel address

/v1/chat/completions

Operations

receiveChatCompletionChunk
Receive streamed chat completion chunks via SSE.

Messages

chatCompletionChunk
One server-sent event carrying an incremental chat completion delta.
Content-Type: text/event-stream

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.