AsyncAPI channel · Mistral AI
· Mistral AI Streaming Completions API
/chat/completions
Streaming chat completions. Client POSTs a ChatCompletionRequest with `stream: true`. The server responds with `Content-Type: text/event-stream` and emits a sequence of `chat.completion.chunk` events, terminated by a `data: [DONE]` line. When `stream_options.include_usage` is true, the final chunk before `[DONE]` carries a populated `usage` object and an empty `choices` array.
Provider:Mistral AIAsyncAPI: v2.6.0Spec: Mistral AI Streaming Completions APIOperations: 1Messages: 3
Channel address
/chat/completions
Operations
subscribe
receiveChatCompletionStream
Receive streamed chat completion chunks
Messages
ChatCompletionChunk
One streamed delta from POST /chat/completions.
Content-Type: application/json
ChatCompletionUsageChunk
Final usage chunk emitted when stream_options.include_usage is true.
Content-Type: application/json
StreamDone
Sentinel marking end of SSE stream.
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.