lead_required

This bot is configured to collect visitor details before it will answer, and the required fields have not been supplied.

• The bot has a lead gate switched on and the visitor has not completed it.
• A custom integration started a conversation without sending the gated fields.

• Read `details.missing` — it lists exactly which fields the gate wants.
• Collect those fields and resend them on the contact before starting the turn.
• If you did not intend a gate, turn it off in the bot's settings; it is off by default.

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

{
  "error": {
    "code": "lead_required",
    "message": "This bot is configured to collect visitor details before it will answer, and the required fields have not been supplied",
    "details": { ... },
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/lead_required",
  "title": "Lead Required",
  "status": 428,
  "detail": "This bot is configured to collect visitor details before it will answer, and the required fields have not been supplied",
  "instance": "/api/bots/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:

• precondition_required

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.