Everything WhatsApp gives you
- 01
Conversations per number
One row per number with the last message, the person's profile name and whether the 24 h window is open.
- 02
The 24-hour window
Outside the window only templates are delivered; a free text fails with 131047, as Meta reports it.
- 03
Templates with review states
Approved, pending, rejected, paused or disabled; each change sends message_template_status_update to the app.
- 04
Parameters checked
A wrong parameter count answers 132000; an undeclared template 132001, and it is listed so you can add it.
- 05
People who reply
reply_as_user sends a text, a template button tap, an image or a location as Meta's messages webhook.
- 06
Signed webhooks
Status and message webhooks carry X-Hub-Signature-256 with your app secret; the verification GET runs on demand.
- 07
Tier, throughput, quality
Over the throughput: 130429. Over the tier: 131056. A restricted number: 131048. Low template quality pauses it.
- 08
Recipients per number
Whether a number has WhatsApp, its profile name and the steps each message goes through: sent, delivered, read, failed.
The screens
Each number is a control or a reading on the real screen. Everything you can click there, your agent can do with a tool.
A conversation, as Meta would report it

Open for 24 h after the person's last message; outside it only templates go out.
A free text sent outside the window fails, and the status webhook says so.
The template as the person sees it, with its URL and quick-reply buttons.
accepted, sent, delivered, read: each webhook with what your app answered.
Fail it with a Meta error code, or send the read webhook again.
- Customer service window
Open for 24 h after the person's last message; outside it only templates go out.
- Failed 131047
A free text sent outside the window fails, and the status webhook says so.
- Template with buttons
The template as the person sees it, with its URL and quick-reply buttons.
- Status, as the app saw it
accepted, sent, delivered, read: each webhook with what your app answered.
- Provoke on this message
Fail it with a Meta error code, or send the read webhook again.
Templates and their review state

Sends follow the status: a paused template answers 132015, a disabled one 132016.
The app used a template that does not exist; Stuntman answered 132001.
Change it and Stuntman sends message_template_status_update to the app.
Low quality pauses the template, as Meta does.
The values the app sent last; a wrong count is answered 132000.
- Rejected and paused
Sends follow the status: a paused template answers 132015, a disabled one 132016.
- Asked for, not declared
The app used a template that does not exist; Stuntman answered 132001.
- Status
Change it and Stuntman sends message_template_status_update to the app.
- Quality
Low quality pauses the template, as Meta does.
- Variables checked
The values the app sent last; a wrong count is answered 132000.
Number, access and webhook

Every Graph call gets 190 OAuthException until tokens are restored.
Webhooks carry X-Hub-Signature-256, so the app's check is tested.
Sends Meta's hub.challenge GET and checks the app echoes it.
Unique numbers a day; over it the send fails with 131056.
The same settings as a file: ids, access, webhook, limits and quality.
- Expire tokens now
Every Graph call gets 190 OAuthException until tokens are restored.
- Signed with the app secret
Webhooks carry X-Hub-Signature-256, so the app's check is tested.
- Verification request
Sends Meta's hub.challenge GET and checks the app echoes it.
- Messaging tier
Unique numbers a day; over it the send fails with 131056.
- number.yaml
The same settings as a file: ids, access, webhook, limits and quality.
Break it on purpose
The failures you need to test, exactly when you ask: from the screen or by a tool call, each one shown on the timeline with who caused it.
500 on the next sendGraph error #131000, for count sends
force_whatsapp_failure {answer: 500}400 invalid parameterGraph error #100
force_whatsapp_failure {answer: 400}Broken connectionThe connection resets, answers nothing, or hangs
force_whatsapp_failure reset | empty | timeoutExpired tokenEvery Graph call gets 190 "Session has expired"
expire_whatsapp_tokensNot on WhatsAppThe status webhook reports 131026
set_recipient {whatsapp: false}Outside the windowA free text after 24 h without a reply fails 131047
send a text while get_window says closedTemplate pausedSends with it fail 132015; disabled gives 132016
set_template_status pausedFailed with a codeA sent message turns failed with the Meta error you pick
set_message_status {status: failed}Duplicate status webhookThe same status webhook arrives again
resend_statusBad webhook signatureWrong, missing or old secret, or a replay; returns your status
send_bad_webhookRate limitSends over the throughput get 130429
set_whatsapp_number {throughput}
Why not the real sandbox
No template review wait
Templates are approved, rejected or paused when you say, not after Meta's review queue.
Real error codes
131047, 132000, 131026 and 190 come with Meta's titles, so the app's error handling is tested for real.
Someone on the other side
Replies, button taps, images and locations without a test phone or a second WhatsApp account.
Webhooks you can break
A wrong signature, an old secret or a replay shows whether the app really checks X-Hub-Signature-256.
Your AI agent drives it
Claude Code, Codex or any MCP client connects to /mcp (or calls /api over plain HTTP), sets the stand-in up, breaks it on cue and reads what your app did.
Make sure the order confirmation flow works when the customer taps "Talk to us".
MCP tools
list_whatsapp_messagesMessages both ways, with status history and the windowwait_for_whatsappWait for the app to send to a number; returns itreply_as_userThe person replies: text, button, image or locationset_message_statusMove a message to sent, delivered, read or failedget_windowIs the 24 h window open for a number, and until whenset_template_statusApprove, reject, pause or disable a templateforce_whatsapp_failureThe next sends fail: 500, 400, reset, empty, timeoutsend_bad_webhookA webhook the app must rejectexpire_whatsapp_tokensEvery Graph call gets 190 until restored
The same over HTTP
- GET
/api/whatsapp/messages - GET
/api/whatsapp/wait - POST
/api/whatsapp/numbers/{number}/reply - POST
/api/whatsapp/force - POST
/api/whatsapp/number/webhook/bad
- Templates live in whatsapp/templates.yaml; no review by Meta happens here.
- Port 8025 serves WhatsApp together with the screen, /api and /mcp.