Webhooks
Get a signed JSON POST the moment plans, routes, and stops change — the events, the HMAC signature, retries, and the 30-day deliveries log.
Webhooks let your own systems react to what happens in Routerra without polling. As the app puts it: "Subscribe to Routerra events with a signed HTTPS endpoint. We deliver each event as JSON and retry on failure with exponential backoff." Set them up under Settings → Developer → Webhooks.
The events
Pick only the events you need — fewer events keeps your receiver fast and your logs clean. They come in three groups:
| Group | Event | Fires when |
|---|---|---|
| Plans | Plan approved | A plan was approved and routes were dispatched |
| Routes | Route started | A driver tapped Start on their route |
| Routes | Route completed | A driver finished all stops on a route |
| Stops | Stop delivered | POD captured and the stop marked delivered |
| Stops | Stop failed | A driver couldn't complete the stop |
Creating an endpoint
Add a webhook endpoint
Press Add endpoint. Give it a Name (just for you — it appears in the dashboard and delivery logs) and an Endpoint URL (use HTTPS in production).
Pick the events to send
Check the events you care about — a counter shows how many of the total you've selected.
Create the endpoint
Routerra starts POSTing signed JSON to your URL whenever a subscribed event occurs.
Verifying the signature
Every payload is signed so you can prove it came from Routerra. Each endpoint has a Signing secret used to sign the payload with HMAC SHA-256 — "Verify it on your receiver to confirm the request came from us." Reveal and copy the secret when you set up your receiver, and check the signature on every incoming request.
Retries and the deliveries log
If your endpoint is down, Routerra doesn't just drop the event — it retries on failure with exponential backoff. Every attempt is recorded in the endpoint's Deliveries tab, with status (Delivered / Failed), event, delivery ID, response code, duration, and when. You can filter by All / Succeeded / Failed and open any delivery to see the attempt time and error message. History is retained for 30 days.
Managing an endpoint
- Disable it to keep the configuration but stop delivering events.
- Delete it to stop delivery immediately (delivery history is retained for 30 days).
Webhooks vs one-click integrations
Webhooks are the raw, build-it-yourself path. If you just want SMS, you don't need a webhook — Twilio SMS is a prebuilt integration. Webhooks are for wiring Routerra into your systems (a CRM, a billing system, an ops dashboard).
What's next
- API keys and the Optimize API — driving Routerra from your code
- Connect Twilio for SMS — a prebuilt integration, no webhook required