If you don’t see your preferred webhook provider, you can request support for it.
- Develop and test Plivo webhooks locally without deploying to a public environment or setting up HTTPS.
- Inspect and troubleshoot requests from Plivo in real time via the inspection UI and API.
- Modify and replay Plivo webhook requests with a single click instead of reproducing events manually in your Plivo account.
- Secure your app with Plivo 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 Plivo account.
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:
- Copy the URL ngrok displays. Your app is now exposed at that URL for use with Plivo.
3. Configure Plivo to send webhooks
Plivo sends webhook requests (also called callbacks) to your app when messages arrive on your Plivo numbers. Follow Plivo’s documentation for receiving SMS messages, and set the following:- Message URL: your ngrok URL (for example,
https://1a2b-3c4d-5e6f-7g8h-9i0j.ngrok.app), with the method set to POST. - Trigger: an incoming message on an SMS-enabled Plivo number, which you assign to the application you create.
Run webhooks with Plivo and ngrok
After you assign the application to your number, Plivo sends POST requests to your app whenever that number receives a message. To trigger a request, send an SMS to your Plivo number. Confirm your localhost app receives the notification and logs both the headers and body in the terminal. You can also review the message logs in Plivo to check the callback status.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 Plivo 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 the Plivo Console, click the eye icon next to Auth Token and copy the value.
-
Create a Traffic Policy file named
plivo_policy.yml. Replace{your auth token}with the value you copied: -
Restart ngrok with the policy file:
- Send an SMS to your Plivo number to trigger the webhook.