Skip to main content
The WhatsApp API sends template messages through the WhatsApp Cloud API. Every message can be backed by a certified RFC 3161 timestamp for legal proof.
All WhatsApp endpoints use HTTP Basic Authusername = account e-mail, password = securityToken. See Authentication.

Concepts

  • Sender — a WhatsApp Business number you connect (or a system number provided by Escrybe). Managed under Senders.
  • Template — a pre-approved message structure (Meta approval required). Managed under Templates.
  • Message — an outbound send bound to a template and a recipient.

Endpoints

Full request/response schemas live in the API Reference tab.

Sending a message

The response returns a message_id, a public visual_id and a status of processing until payment is settled and the message is queued.
  • The recipient’s phone is verified against WhatsApp — numbers not on WhatsApp are rejected with 400.
  • If the template’s header uses an image or document, one of media_url, media_file or media_base64 is required.
  • If a message stalls with status 2 (insufficient credits), top up your balance and POST /api/whatsapp/v1/process with the message_id to re-queue it.

Certified timestamps

Each message can produce attestation files for the accepted, sent, delivered and read phases. Download them all as a ZIP:

Templates

Templates must be approved by Meta before use. Create one, then poll its status until approved:
The final template name is normalized and prefixed with your user id (e.g. user42_order_confirmation) — the response’s name field is what you use when sending; your original text is kept as display_name. A sender-identification footer is automatically appended to the body, and image/document header templates submitted without media use a default Escrybe sample file for Meta approval.