Skip to main content
Every error response includes ok: false and a machine-readable code.

Error envelope

Realtime WebSocket error frames

The realtime text-to-speech WebSocket reports errors as JSON error frames instead of HTTP responses. The frame carries the same machine-readable code values as the table below; the human-readable text is in message (the WebSocket counterpart of the HTTP envelope’s detail), and optional context is in meta:
The Status column shows each code’s default HTTP status; on the WebSocket the code arrives in an error frame, optionally followed by a close. Whether an error closes the session — and with which close code — is defined in the realtime guide.

Reference

Operational guidance

Authentication

Send API keys correctly and distinguish session-only account endpoints from API-key endpoints.

Rate limits

Retry concurrency, capacity, and timeout errors without overloading generation.

CLI troubleshooting

Map CLI exit codes to auth, quota, timeout, network, and dependency fixes.

Developer logs

Inspect failed requests, latency, request IDs, and generated cURL examples.