Webhooks

RoutiGo webhooks enable you to receive real-time notifications about specific events in your routing operations. Instead of continuously polling our API for updates, webhooks push notifications to your application the moment an event occurs—making your integration more efficient and responsive.

Common Use Cases

  • Synchronize order statuses between RoutiGo and your system
  • Trigger custom workflows when routes are started or completed
  • Send notifications to customers when deliveries are made
  • Update inventory or CRM systems based on delivery events

Note for existing users: If you've been using our legacy webhook format, you can find documentation here: General information and Management API

Event triggers

After configuring your webhook subscription, RoutiGo will automatically send notifications to your endpoint whenever the specified events occur. Each notification includes:

  • A JSON payload containing event data (structure depends on the event type)
  • Optional query parameters for additional context
  • HTTP headers with metadata about the request
  • Timestamp information for when the event occurred

Getting Started: To register a webhook subscription, check out the Webhook Management API

TOUR_PLANNED

Indicates a tour has been successfully planned and released in the dashboard. At this point, the communication with the clients is performed if enabled, and the communicated time windows are set for all stops in this specific route. From this point onward the system will try and maintain the order of stops according to these new windows. This also means the route is now ready to be assigned to a driver. This state cannot be reverted.

TOUR_ASSIGNED

An event that is triggered after a tour has been assigned to or picked up by a driver. This makes the driver now responsible for driving this route and removes the option to assign this route to another driver, unless it is unassigned. The assigned driver will be displayed on the tracking page if enabled. This state can be reverted from the driver app and the RoutiGo dashboard. Reverting will trigger the `TOUR_UNASSIGNED` event. It is worth noting that a driver can only be assigned to one route at a time.

TOUR_UNASSIGNED

An event that is triggered after a tour has been unassigned/unclaimed from/by a driver. This is the reversal of the `TOUR_ASSIGNED` event and changes the state of the tour to where it can again be assigned or claimed by another driver.

TOUR_STARTED

An event that is triggered after a driver has indicated that the tour has been started. This is performed from within the RoutiGo driver smartphone app. Once this event is triggered the assumption is made that the driver starts the route, assuming it is past the planned starting time of the route (if not, route calculations will assume the planned starting time).

TOUR_FINISHED

An event that is triggered after a driver has indicated that the tour is finished and all stops are done. From this point onward the driver is now again available for route assignment.

SHIPMENT_DONE

An event that is triggered when both locations of a shipment have been marked as done.

ASSIGNMENT_DONE

An event that is triggered when a single assignment (of a stop) has been marked as done, and if applicable the registrations have been filled in. Based on this event the assignment will be given an `end status`. By default, this will be set to `DELIVERED`. This event can be triggered multiple times if the driver changes the registrations of an assignment, but can not be reverted.

Event types

The structure and content of webhook payloads are determined by the event type you configure. RoutiGo supports four event types, each providing different levels of detail:

Tour

If the EventType is set to Tour, all events will contain the entire tour and it's data. E.G; in case an ASSIGNMENT_ARRIVED event is triggered with the EventType TOUR. The tour with all stops and nested assignments will be send.

Shipment

If the EventType is set to Shipment, all events will contain a single shipment and it's data.

Assignment

If the EventType is set to Assignment, all events will contain a single assignment and it's data.

Need more context? For a comprehensive understanding of these types and their meanings, review our terminology guide.

Event Triggers & Types Compatibility

Use this matrix to determine which event types are compatible with each event trigger.

Event Trigger / Event Type
TOUR
SHIPMENT
ASSIGNMENT
TOUR_PLANNED
TOUR_ASSIGNED
TOUR_UNASSIGNED
TOUR_STARTED
TOUR_FINISHED
SHIPMENT_DONE
ASSIGNMENT_DONE