VonyxDocs

Errors and limits

HTTP statuses, close codes and limits of the Enhancer API.

View this page as Markdown

Most failures show up as an HTTP status when the WebSocket opens. After that, the socket is closed with a code.

When connecting (HTTP status)

StatusBodyMeaningWhat to do
400bad redirect: ...Redirect missing, or not a ws:// / wss:// URLFix the redirect parameter or path
401unauthorizedAPI key missing or wrongCheck the key; for carriers, use the path form
402Zero Balance please recharge.Wallet is emptyAdd credits, then call again
503service temporarily unavailableKey check briefly unavailableRetry
503relay capacity fullAt the connection limitRetry, and tell us your peak concurrency

After connecting (close code)

CodeReasonMeaning
1000relay teardownNormal end of the call
4001denoise unavailableThe noise-removal engine couldn't take the call
4002redirect target unreachableYour redirect URL didn't accept the connection within 10 s

Limits

  • 32 KB per message. Keep every message under 32 KB, including playAudio from your bot. A bigger message ends the call. Base64 PCM16 at 8 kHz fits about 1 second of audio in 32 KB.
  • Keep reading. If your redirect socket stops reading for 5 seconds, the call is dropped.
  • 10-second connect. Your redirect must accept the connection within 10 seconds.
  • Concurrency. Tell us your expected peak of simultaneous calls before you launch.

On this page