voice_unavailable

Every service that turns speech into text, or a voice into speech, failed for this request.

• A speech provider is down or timing out, and its fallback is too.
• A provider stopped honouring the privacy routing we require, so it is not used.

• Retry after a short wait; the platform moves to another provider by itself.
• Typing always works, and the widget offers it.

{
  "error": {
    "code": "voice_unavailable",
    "message": "Every service that turns speech into text, or a voice into speech, failed for this request",
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/voice_unavailable",
  "title": "Voice Unavailable",
  "status": 503,
  "detail": "Every service that turns speech into text, or a voice into speech, failed for this request",
  "instance": "/api/agents/01a0652b-3713-7ea1-a6c9-2e895389ec34"
}

Branch on error.code, not on the message — the code is stable, the sentence is not. Log request_id either way.

Codes that are easy to confuse with this one, or that show up alongside it:

• service_unavailable

Quote the request_id from the response — hello@integrable.cloud. It is what lets us find the exact request. The full list of codes is at Error codes, and the conventions every endpoint shares are in Retries, versioning and limits.