Sonar chat completions endpoint (sonar, sonar-pro, sonar-reasoning-pro,
sonar-deep-research). When `stream: true`, responds with SSE. The
`stream_mode` parameter controls event shape:
- `full` (default): each chunk has shape `chat.completion.chunk`
(OpenAI-compatible), with server-side aggregated message; search
results may appear multiple times during the stream.
- `concise`: emits fo
One `data:` SSE event whose payload is a JSON object with
`object: chat.completion.chunk`. The stream ends with a terminal
`data: [DONE]` line.
Content-Type: application/json
SonarChatReasoning
Sonar concise-mode chat.reasoning event
Content-Type: application/json
SonarChatReasoningDone
Sonar concise-mode chat.reasoning.done event
Content-Type: application/json
SonarChatCompletionDone
Sonar concise-mode chat.completion.done event
Content-Type: application/json
StreamDoneSentinel
OpenAI-compatible terminal SSE line `data: [DONE]` marking end of 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.