The WhatsApp Messaging API allows you to send template-based messages to users via a configured WhatsApp Business Account (WABA). This endpoint is designed for reliable, scalable communication, supporting both bulk messaging and personalized messaging workflows using pre-approved WhatsApp templates.Documentation Index
Fetch the complete documentation index at: https://docs.belio.co.ke/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
To use the WhatsApp Messaging API, you need to have the following prerequisites in place:- WhatsApp Service : You must have an active and valid WhatsApp Business service. Visit Service requests
to create a service.
- There are two ways to get a service ID once you have created a service:
- Use the List Services endpoint to list all services and retrieve the ID of the specific one you intend to use
- Go to the Services page and copy the ID by clicking on the copy file icon as shown in
the image below.

- There are two ways to get a service ID once you have created a service:
- WhatsApp Business Account (WABA): You must have a WhatsApp Business Account set up and configured. This includes having a verified phone number and a display name that adheres to WhatsApp’s guidelines.
- Approved Message Templates: You need to create and get approval for message templates that you intend to use for sending messages. These templates must comply with WhatsApp’s policies and guidelines. Check WhatsApp Business Messaging policy.
- API client authorization: This endpoint requires the
message.whatsapp.send.onewayAPI client authorization scope to send one way WhatsApp messages. You can set up scopes on the API Clients page.
Advanced Features
The WhatsApp Messaging API supports advanced features such as message scheduling, media attachments, and interactive message templates.- Media Attachments: You can include media attachments such as images, videos, and documents in your messages to enhance engagement and provide richer content.
- Interactive Message Templates: You can use interactive message templates that include buttons and quick replies to encourage user interaction and improve response rates.
-
Receipt requests : For enhanced functionality, you can include an optional
receiptRequestin the request body. This feature allows you to receive delivery receipts for the messages you send, enabling you to track their status and confirm successful delivery. ThereceiptRequestobject includes the following fields:- correlator: A unique string to correlate the delivery receipt with the original message.
- callbackUrl: A URL where the delivery receipt will be sent.