What is a WhatsApp Webhook and How to Configure It in wolkvox Manager
Table of Contents
Introduction
The WhatsApp webhook in wolkvox Manager allows you to receive real-time notifications about errors when sending messages.
Thanks to this feature, companies can implement proactive monitoring and detailed traceability of errors generated by the WhatsApp Business API (Cloud API).
The webhook sends events to a URL defined by the client, which must be previously developed and hosted by their own organization.
The webhook enables WhatsApp operations administrators to:
- Monitor errors in real time.
- Log events for historical analysis or debugging.
- Trigger automatic alerts through integrations with internal systems (e.g., dashboards or ticketing tools).
Note: This feature is available only for Cloud API connectors and may incur additional billing costs.
How to Configure a WhatsApp Webhook in wolkvox Manager
- In the upper-right menu of wolkvox Manager, click the ⚙️ Settings icon.
- In the window that opens, select the Omni Channel tab.
- Go to the WhatsApp sub-tab.
- Locate the desired WhatsApp account and click the Edit button.

- In the upper-right corner of the connector window, click the three vertical dots button.
- In the dropdown menu, select Configure webhook.

The Configure webhook window will appear, where you must:
- Enter your webhook URL, for example: https://mydomain.com/webhook/whatsapp
- (Optional) Enable the Error when sending message switch to receive events only when delivery errors occur.
- Finally, click Save to confirm the changes.
- Note: wolkvox does not create or manage the webhook. The client is responsible for developing, hosting, and maintaining the URL where events will be received.

Final Result: Once configured, the webhook will start receiving automatic notifications from Meta whenever a message delivery error occurs. This facilitates early failure detection and improves quality management of the WhatsApp channel within wolkvox Manager.
Error Codes
Below is a list of the most common error codes returned by Meta to the webhook, along with their possible causes and recommended actions:
| CODE | ERROR DESCRIPTION | COMMON REASONS | RECOMMENDED ACTIONS | 
| 131026 | Message cannot be delivered | 
 | 
 | 
| 131042 | Payment issue related to business eligibility | 
 | Review billing settings and credit limits. | 
| 130472 | The user’s number is part of an experiment | Meta temporarily blocked sending. | Check documentation on marketing message experiments. | 
| 131049 | Meta has decided not to deliver it | Delivery restrictions or applied limits. | 
 | 
| 131048 | Spam frequency limit reached | Blocks or marked as spam. | Check quality status in WhatsApp Manager. | 
| 131031 | The account has been blocked | Policy violations. | Review policies and account status API. | 
| 132000 | Template parameter count mismatch error | Incorrect or incomplete parameters. | Ensure all required parameters are included. | 
| 100 | Invalid parameter | Misspelled or unsupported parameters. | Verify compliance with specifications. | 
| 131053 | Media upload error | Unsupported file type. | Validate media content format. | 
