Chat completion SSE stream. The client opens this channel by issuing
`POST https://api.targon.com/v1/chat/completions` with `stream: true` in
the JSON request body and an `Authorization: Bearer` API key. The server
responds with `Content-Type: text/event-stream` and emits chat completion
chunk events until a final `data: [DONE]` sentinel.
Receive streamed chat completion chunks as SSE events.
Messages
ChatCompletionChunk
A single data-only 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.
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.