Messaging Health Status
The Health Messaging Status feature enables you to monitor the status of the WhatsApp Business Account (WABA) and phone number within the Cloud API messaging system.
By making the request to the /health_status
endpoint, you can receive immediate feedback the operational condition of the messaging service, identifying any potential issues or limitations that might be affecting message delivery or system performance.
Only WABA and phone number statuses are available today. We are working to make Template Messages statuses available in the near future as well.
API Reference
When you request the health_status
field, the Messaging API automatically returns the status of both the phone number and WABA account in the same response. Currently, the API does not return the health status of message templates.
Health Status
GET
https://waba-v2.360dialog.io/health_status
Request Example:
curl --location 'https://waba-v2.360dialog.io/health_status' --header 'D360-API-KEY: {{API_Key}}' --header 'Content-Type: application/json'
Headers
Name | Type | Description |
---|---|---|
D360-API-KEY* | string |
See Callback Response below.
Response Payload
Messaging Health Status Details
When you attempt to send a message, it involves several parts (nodes or entities), such as a WhatsApp Business Account (WABA), a business phone number, and sometimes a message template. Each node has a "health status" assigned to the can_send_message
property to show if it can send messages:
AVAILABLE
: Indicates that the node meets all messaging requirements.LIMITED
: Indicates that the node meets messaging requirements, but has some limitations. If a given node has this value, additional info will be included.BLOCKED
: Indicates that the node does not meet one or more messaging requirements. If a given node has this value, the errors property will be included which describes the error and a possible solution.
Overall Status
The overall health status property can_send_message
will be set as follows:
If one or more nodes is blocked, it will be set to
BLOCKED
.If no nodes are blocked, but one or more nodes is limited, it will be set to
LIMITED
.If all nodes are available, it will be set to
AVAILABLE
.
Example Response:
Additional Info Property
If a given node's can_send_message
property is set to LIMITED
, the additional_info
property will be included, which provides additional context for the limitation.
Example Limited Response
This is an example response to a request on a business phone number that can be used to send messages, but has a limit on the number it can send because its display name has not been approved.
Errors Property
If a given node's can_send_message
property is set to BLOCKED
, the errors
property will be included, which describes the reason for the status and a possible solution.
Example Blocked Response
This is an example response to a request on a template that can't be sent in a template message because it is still in a pending state.
We're plan to introduce the ability to fetch the health status of message templates soon. More information will be provided as it becomes available.
Last updated