If you don’t see your preferred webhook provider, you can request support for it.
- Develop and test WhatsApp webhooks locally without deploying to a public environment or setting up HTTPS.
- Inspect and troubleshoot requests from WhatsApp in real time via the inspection UI and API.
- Modify and replay WhatsApp webhook requests with a single click instead of reproducing events manually in your WhatsApp account.
- Secure your app with WhatsApp webhook validation provided by ngrok. Invalid requests are blocked by ngrok before reaching your app.
What you’ll need
- An ngrok account and your authtoken.
- The ngrok agent installed.
- Node.js installed (for the sample app, or use your own app).
- A Facebook app and a business phone number for WhatsApp.
This integration requires an ngrok Pay-as-you-go plan because Meta validates your ngrok domain and certificate.
1. Start your app
For this tutorial, you can use the sample Node.js app on GitHub. To install the sample, run the following in a terminal:http://localhost:3000.
The app logs request headers and body in the terminal and shows a message in the browser.
2. Expose your app with ngrok
Once your app is running locally, you’re ready to put it online securely using ngrok.- Copy your ngrok authtoken from the dashboard.
-
Start ngrok with your reserved domain:
-
Copy the URL ngrok displays.
Your app is now exposed at that URL for use with WhatsApp (use
https://myexample.ngrok.app/webhooksas the callback URL).
3. Configure WhatsApp to send webhooks
Follow Meta’s documentation for setting up WhatsApp Cloud API webhooks, and set the following:- Callback URL: your ngrok URL with your app’s path (for example,
https://myexample.ngrok.app/webhooks). - Verify token: a value of your choosing (for example,
12345) that your app checks during the verification handshake. - Webhook fields: subscribe to messages and any other fields you need.
WEBHOOK_VERIFIED.
Run webhooks with WhatsApp and ngrok
Send a message to your WhatsApp business number to trigger the webhook. Confirm your localhost app receives the message and logs both the headers and body in the terminal.Inspecting requests
ngrok’s Traffic Inspector captures all requests made through your ngrok endpoint to your localhost app. Select any request to view detailed information about both the request and response.To avoid exposing secrets, accounts only collect traffic metadata by default.
You must enable full capture in the Traffic Inspector section of your account settings to capture complete request and response data.
- Validate webhook payloads and response data
- Debug request headers, methods, and status codes
- Troubleshoot integration issues without adding logging to your app
Replaying requests
Test your webhook handling code without triggering new events from your service using the Traffic Inspector’s replay feature:- Send a test webhook from your service to generate traffic in your Traffic Inspector.
- Select the request you want to replay in the traffic inspector.
-
Choose your replay option:
- Click Replay to send the exact same request again
- Select Replay with modifications to edit the request before sending
- (Optional) Modify the request: Edit any part of the original request, such as changing field values in the request body.
- Send the request by clicking Replay.
Secure webhook requests
ngrok can verify that incoming requests are from your WhatsApp webhook so only that traffic reaches your app.Webhook verification is limited to 500 validations per month on free accounts.
If you need more, you can upgrade to Hobbyist or Pay-as-you-go.
See TPU Pricing for details.
- In Meta for Developers, go to Settings > Basic, click Show for App secret, and copy the value.
-
Create a Traffic Policy file named
whatsapp_policy.yml. Replace{your app secret}with the value you copied: -
Restart ngrok with the policy file:
- Send another message to the WhatsApp number to trigger the webhook.