AsyncAPI channel · Groq · Groq Chat Completions Streaming (HTTP + SSE)

/chat/completions

Chat completion SSE stream. The client opens this channel by issuing `POST /chat/completions` with `Content-Type: application/json`, `Accept: text/event-stream` (implied), 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 `

Open source AsyncAPI → All Groq channels Groq provider profile
Provider: Groq AsyncAPI: v2.6.0 Spec: Groq Chat Completions Streaming (HTTP + SSE) Operations: 1 Messages: 3

Channel address

/chat/completions

Operations

streamChatCompletionChunks
Subscribe to streamed chat completion chunks (SSE).

Messages

ChatCompletionChunk
A single SSE `data:` event carrying one JSON `chat.completion.chunk` object. Many of these are emitted per request, in order.
Content-Type: application/json
ChatCompletionUsageChunk
Optional chunk emitted only when the request body sets `stream_options.include_usage: true`. Streamed immediately before `data: [DONE]`.
Content-Type: application/json
StreamDone
The literal SSE event `data: [DONE]` that marks end of stream. Not JSON; the payload is the string `[DONE]`.
Content-Type: text/plain

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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.