voice_consent_mismatch

The recording does not read the consent statement closely enough, so it was not stored and no voice was made from it.

• A clip of something else - an interview, an advert - rather than the statement.
• The statement read with a different name, or with parts skipped.
• A noisy room the ear could not hear the words in.

• Read the statement exactly as shown, with the name in it, in a quiet room.
• `details.heard` says what was heard, so you can see what went wrong.

This code carries a details object with more than the message can say:

{
  "error": {
    "code": "voice_consent_mismatch",
    "message": "The recording does not read the consent statement closely enough, so it was not stored and no voice was made from it",
    "details": { ... },
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/voice_consent_mismatch",
  "title": "Voice Consent Mismatch",
  "status": 422,
  "detail": "The recording does not read the consent statement closely enough, so it was not stored and no voice was made from it",
  "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_consent_required
• voice_too_short

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.