Server-Sent Events stream of `text_completion` chunks produced by
`POST /beta/completions` (the Fill-In-the-Middle completions endpoint)
when `stream` is `true`. Each event is a partial completion chunk
following the OpenAI legacy completions streaming shape. The stream is
closed by a literal `data: [DONE]` event.
Provider:DeepSeekAsyncAPI: v2.6.0Spec: DeepSeek Streaming API (HTTP + SSE)Operations: 1Messages: 2
Channel address
/beta/completions
Operations
subscribe
subscribeFimCompletionStream
Receive streaming FIM (Fill-In-the-Middle) completion chunks.
Messages
FimCompletionChunk
A single streaming chunk emitted on the SSE stream while a
`/beta/completions` (Fill-In-the-Middle) 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.
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.