- Develop and test Mux webhooks locally without deploying to a public environment or setting up HTTPS.
- Inspect and troubleshoot requests from Mux in real time via the inspection UI and API.
- Modify and replay Mux webhook requests with a single click instead of reproducing events manually in your Mux account.
- Secure your app with Mux 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 Mux 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 Mux.
3. Configure Mux to send webhooks
Mux can send webhook requests to your app when events occur in your account. To register for those events:- Sign in to Mux.
- Click Settings in the left menu and then Webhooks.
- On the Webhooks tab, click Create new webhook.
- Select your environment and enter your ngrok URL in URL to notify (for example,
https://1a2b-3c4d-5e6f-7g8h-9i0j.ngrok.app). - Click Create Webhook.
Run webhooks with Mux and ngrok
Mux sends different request body contents depending on the event. To trigger new calls from Mux to your app:- On the Mux dashboard, click Assets and then Create New Asset.
- On the Create a new asset popup, click Run Request.
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 Observability 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 Mux 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 Mux, go to Settings and Webhooks.
- On the Webhooks tab, click Show Signing Secret for your webhook and copy the value.
-
Create a Traffic Policy file named
mux_policy.yml. Replace{your signing secret}with the value you copied: -
Restart ngrok with the policy file:
- Create a new asset in Mux to trigger the webhook.