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

/v1/async/sonar

Async Sonar chat completions. NOT a push/streaming transport. Client POSTs to enqueue a job and later GETs the request id to retrieve the response. Modeled here only because it is Perplexity's other documented asynchronous interaction pattern; there is no SSE on this channel.

Open source AsyncAPI → All perplexity channels perplexity provider profile
Provider: perplexity AsyncAPI: v2.6.0 Spec: Perplexity Streaming API (HTTP + Server-Sent Events) Operations: 2 Messages: 2

Channel address

/v1/async/sonar

Operations

publish
enqueueAsyncSonarJob
Enqueue an asynchronous Sonar chat completion job
receiveAsyncSonarJobAcknowledgement
Receive job acknowledgement with request id (polled, not pushed)

Messages

AsyncSonarEnqueueRequest
Enqueue async Sonar job (non-SSE)
Content-Type: application/json
AsyncSonarJobAcknowledgement
Async Sonar job acknowledgement (polling pattern)
Content-Type: application/json

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.