Production Checklist

PreviousNext

What to check before going to production.

Use this list before a production cutover.

Credentials & authentication

  • API keys are stored server-side only — never shipped in frontend bundles or URLs.
  • Browser clients obtain a short-lived session token (rt_…, 60 s) from your backend instead of using the long-lived key. See Authentication.
  • Keys can be rotated / revoked without a redeploy.

Connection handling

  • Your client handles the relevant close codes — 4408 (idle), 1008 (session limit), 1011 (socket error). See Connection Lifecycle.
  • Reconnect uses capped exponential backoff and resets on success. See Reconnection & Retries.
  • session.update is re-sent after every reconnect (sessions do not resume).

Limits

  • Client honours HTTP 429 with Retry-After.
  • Audio frames stay below 1 MiB.
  • You understand the per-plan limits (connections, concurrent utterances, audio seconds). See Rate Limits.

Audio

  • Sample rate and encoding are consistent across producers. See Audio Input.
  • Chunk size is tuned for your latency target.
  • Keep-alive silence is sent during long idle periods if needed.

Observability

Data