ElevenLabs Agents API (/v1/convai) enforces server-side timeouts from November 26, 2026 and may return 504
From Nov 26, /v1/convai requests can time out on the server and return HTTP 504 when latency rises. Retry with backoff.
Your keys
0 of 1 ready
Create each key on its own page, paste it below, then copy the finished lines into your project's .env file. Your keys stay in this tab. They are never sent to Wirestack or saved; we only count that the panel was used.
- ElevenLabs API keyELEVENLABS_API_KEYGet key
Click Create API key
What changed
ElevenLabs posted on November 16, 2026: starting November 26, 2026, the ElevenAgents API (/v1/convai) enforces server-side request timeouts. During temporary increases in latency, a request may return HTTP 504. ElevenLabs asks clients to handle 504 responses, for example by retrying with backoff.
Prerequisites
- An app that calls ElevenLabs Agents endpoints under
/v1/convai(directly or through the official SDKs) - An ElevenLabs API key in
ELEVENLABS_API_KEY
Steps
- Find every call your code makes to
/v1/convai. - Treat
504as a retryable error: wait, then retry with a growing delay and a retry limit. - If your HTTP client already retries
5xxerrors, check that504is on its list. - Ship the change before November 26.
Test it
Point one /v1/convai call at a test server that answers 504 once and then 200, and check that your code retries and succeeds.
Not confirmed
- The changelog does not say how long the timeout is or which
/v1/convaiendpoints are most affected. - It does not say whether the official SDKs retry
504on their own.
