AsyncAPI channel · perplexity · Perplexity Streaming API (HTTP + Server-Sent Events)

/v1/sonar

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

Provider: perplexity AsyncAPI: v2.6.0 Spec: Perplexity Streaming API (HTTP + Server-Sent Events) Operations: 2 Messages: 6

Channel address

/v1/sonar

Operations

publish
openSonarStream
Open an SSE stream for Sonar chat completions
receiveSonarStreamEvents
Receive Sonar SSE events (full or concise mode)

Messages

SonarStreamRequest
Sonar chat completions request with stream=true
Content-Type: application/json
ChatCompletionChunk
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.

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.