whatsapp_number_not_verified now names the number's status
Released: November 12, 2026
whatsapp_number_not_verified message Changed
Section titled “whatsapp_number_not_verified message ”Requests under /v1/{phone_number_id}/... and the MCP tools return
422 whatsapp_number_not_verified when the phone_number_id belongs to
your organization but the number is not connected. The message used to
read “The WhatsApp number is not verified for this organization.”, which
suggested a missing verification step. It now states that the number is
not connected, gives its status, and says what to do:
{ "error": { "type": "invalid_request_error", "code": "whatsapp_number_not_verified", "message": "The WhatsApp number is not connected (status: disconnected). Reconnect it in the Kirimdev dashboard.", "request_id": "req_01HXYZABCDEFGHJKMNPQRSTVWX" }}| Status | Meaning |
|---|---|
disconnected, error | The connection to Meta was lost. Reconnect the number in the dashboard. |
connecting | The number is still being connected or synced. Retry in a few minutes. |
degraded | Meta temporarily limited the number. It recovers on its own after the cooldown. |
The code and HTTP status are unchanged. Keep branching on
error.code; do not parse the message.