Webhook observation
Receive supported message events without changing the responder.
Reviewed
observeAllOrigins defaults to false. Omitting it on a callback save writes false, preserving the existing external-admitted inbound and API outbound callback behavior. Set it explicitly to true on each save to receive fresh supported observations in native mode. Read and save responses include the persisted boolean. Callback management works in either mode but still requires a connected number and webhooks:manage; reading settings requires webhooks:read.
Opt-in covers fresh native Meta inbound messages and supported canonical outbound API, human-agent, Logic Flow, Automation, Broadcast and System sent/delivered/read/failed observations. It does not include AI-agent, coexistence-sync, unknown or internal origins. Event selection still applies. It does not backfill history, replay old events, grant send scopes or change Flow state, assignment or human ownership. API sends still require EXTERNAL_API handling. Separately reviewed MCP template tools retain their own authority and are not a native-mode API send exception.
Message callbacks include the same safe attribution object as message reads. Missing evidence stays unknown or null. Pending inbound media remains bound to the endpoint that admitted it and can block later callbacks; at the 24-hour event deadline it becomes unavailable and terminal without a request to your receiver. Later media completion cannot replay it or attach it to a new endpoint. Recover gaps with retained-history and changes reconciliation.
Failed-status callbacks retain the safe failure code observed when the event was admitted. Later status recovery or another failure cannot replace it on a delivery retry. An older event without a stored snapshot omits the code instead of guessing from the message's current state.
Next: Verify signed callbacks or recover retained message changes.
Receive webhooks
Configure a Waaru callback URL, select message events, verify signed raw requests in Node.js, deduplicate delivery, and recover paused or failing webhooks.
API errors and retries
Interpret Waaru Developer API error codes, rate-limit headers, admission failures, and uncertain send outcomes without duplicating customer messages.