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.
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.
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.