Routific Webhooks

Receive real-time notifications from Routific when key delivery events happen

📘

Looking for the REST API?

The REST API and webhooks are complementary, not competing. Use the REST API to push orders into Routific and pull data on demand. Use webhooks to receive data from Routific the instant something happens. See Routific Platform API for the full REST reference.

Overview

Routific Webhooks let your systems react to events the moment they occur inside Routific. Instead of repeatedly calling the REST API to check whether something has changed, you register an HTTPS endpoint and Routific pushes a payload to it automatically whenever a subscribed event fires.

This is the right integration pattern for anything event-driven: a route being published, a driver's ETAs changing in real time, or an order being completed or missed. These are state-change signals — they happen once, at a specific moment — and webhooks are purpose-built to carry them.

Webhooks v Polling REST API

If you're currently polling the /routes or /orders endpoints to detect changes, webhooks replace that pattern entirely.

REST API (polling)Webhook
How it worksYou request data on a scheduleRoutific pushes data when events fire
LatencyUp to your polling intervalNear real-time
Server LoadGenerates requests even when nothing changedRequest only sent when an event fires
ImplementationRequires a polling loop and diff logicRegister a URL, receive the payload
Best ForOn-demand queries, pulling data you needReacting to delivery events as they happen

Getting Started

Webhooks are configured per Company in Routific's dashboard. Only users with an Admin role can create or modify webhooks.

To get started:

  1. Navigate to Company Settings -> Routific webhook
  2. Create a webhook and Activate
  3. Test the connection
  4. Save your signing secret

📘

Validating Webhook Signatures

Routific signs every webhook request so you can verify that the payload came from Routific and has not been tampered with. Signature validation is optional on your end — but strongly recommended for production integrations.

Every webhook request includes a signature header. Use the signing secret from your webhook settings to validate it against the raw request body before processing the payload.

If a signature does not match, discard the request.

🚧

Rotating the signing secret

If your secret is ever compromised, rotate it immediately from the Webhooks settings page. After rotation, a 24-hour grace period applies during which both the old and new secrets are valid — giving you time to deploy the updated secret on your end without downtime. If you need to invalidate the old secret immediately (e.g. due to suspected compromise), contact support.

Routific Webhook Events

With these Webhooks you can integrate with your own systems and trigger downstream workflows based on real time updates from Routific:

Route Published

Subscribe to this event if you plan on:

  1. Packing and labeling - Trigger your warehouse management system to generate packing lists and print labels for each route the moment it's published, in the correct stop sequence.
  2. Dispatch notifications - Automatically send route manifests to drivers or third-party dispatch systems without anyone having to export or copy data.
  3. Sync to external systems - Update your order management system, WMS, or TMS with confirmed route assignments and stop sequences as soon as routes are locked in.

Route ETAs Updated

Subscribe to this event if you plan on:

  1. Live ETA notifications to customers - Send customers an updated "your driver is X stops away, arriving around [time]" message whenever the driver's progress changes. No polling required.

Order Completed

Subscribe to this event if you plan on:

  1. Order status sync - Automatically flip orders from "in progress" to "delivered" or "failed" in your OMS or ERP the moment a driver resolves them — no polling loop, no lag.
  2. Trigger post-delivery workflows - Fire a customer satisfaction survey, send a delivery confirmation email, or initiate an invoicing workflow immediately after a successful delivery.
  3. Failed delivery handling - When status is missed, trigger your rescheduling or customer contact flow automatically.
  4. Proof of delivery distribution - Push POD photos and signatures to your document management system or share them with shippers as soon as a stop is resolved.

What you build on top of these events is totally up to you — Routific simply ensures the signal reaches your system the moment it happens.