DEVELOPER GUIDE

WhatsApp sent vs delivered vs read

Understand message states so dashboards and automation do not mistake transport progress for customer action.

Developer guide for message states. Validate the behavior in your own stack before production rollout.

The problem

Sent means the provider accepted the request; delivered means it reached the WhatsApp account; read means the account marked it read.

Design the boundary

Keep each transition in an append-only event log and apply monotonic ordering when events arrive late.

Process the interaction

Do not infer order fulfillment, consent or task completion from a read receipt.

Measure the outcome

Measure state transition latency and unknown or failed outcomes separately.

Related documentation

WhatsApp API · Webhook events · Security · Tutorials

BUILD IT SAFELY

Make the failure path part of the design.

Reliable messaging is an operational system, not only an API call.

Gain Access
STRAIGHT ANSWERS

Questions before you build?

Start with the documentation or review the practical answers below.

Is ChatRail the official Meta Cloud API?

No. ChatRail uses a WhatsApp Linked Devices session. Review the transport trade-offs before production use.

Can I use it without AI?

Yes. Sending, delivery tracking and webhooks work without enabling AI.

Where should I start?

Use the Quickstart for your first request, then choose a workflow tutorial.