no_speech

The recording held no speech the agent could hear, so there was nothing to answer.

• The visitor tapped the microphone and said nothing, or spoke too quietly.
• The recording was under half a second, or empty because the microphone was muted.
• Background noise only - the ear recognises its own stock phrases for silence and drops them.

• Nothing to fix on your side: the widget says it did not catch that and listens again.
• In your own client, ask the visitor to repeat themselves rather than showing an error.

{
  "error": {
    "code": "no_speech",
    "message": "The recording held no speech the agent could hear, so there was nothing to answer",
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/no_speech",
  "title": "No Speech",
  "status": 422,
  "detail": "The recording held no speech the agent could hear, so there was nothing to answer",
  "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:

• voice_too_long

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.