AsyncAPI channel · DeepSeek · DeepSeek Streaming API (HTTP + SSE)

/chat/completions

Server-Sent Events stream of `chat.completion.chunk` objects produced by `POST /chat/completions` when `stream` is `true`. The first chunk typically carries `delta.role = "assistant"`. Subsequent chunks carry incremental `delta.content` tokens, and - for the `deepseek-reasoner` model - `delta.reasoning_content` tokens during the chain-of-thought phase. The final data chunk before the terminator ma

Open source AsyncAPI → All DeepSeek channels DeepSeek provider profile
Provider: DeepSeek AsyncAPI: v2.6.0 Spec: DeepSeek Streaming API (HTTP + SSE) Operations: 1 Messages: 2

Channel address

/chat/completions

Operations

subscribeChatCompletionStream
Receive streaming chat completion chunks.

Messages

ChatCompletionChunk
A single `chat.completion.chunk` event emitted on the SSE stream while a `/chat/completions` request with `stream=true` is in progress.
Content-Type: application/json
StreamDone
Sentinel event marking the end of the SSE stream. The raw SSE line is `data: [DONE]`. After this event the server closes the response body.
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.