Webhooks
Subscribe an integration to selected Orbit events and review its delivery attempts.
Subscribe an integration to selected Orbit events and review its delivery attempts.
Was this article helpful?
Did not find your answer?
Ask Luna, or write to our support team.
Webhooks send HTTP POST notifications to an endpoint when selected events occur in Orbit. Use them to keep an external integration up to date with changes to vehicles, carriers and other records.
Open Webhooks in Orbit MissionControl
Add the destination
Save the subscription
In the event selector, vehicle events appear under Vehicle and carrier events appear under Carrier. Select each event separately to subscribe to it.
| Event | Information in the notification |
|---|---|
vehicle-created | The vehicle that was created |
vehicle-action-created | The vehicle and the action performed on it |
vehicle-deleted | The vehicle details from before deletion |
carrier-created | The carrier that was created |
carrier-action-created | The carrier and the action performed on it |
The event name and notification shape for each event are listed in the Orbit API Reference. Choose only the events your integration needs.
In the event selector, events about Sequences appear under Sequence. Select each event separately to subscribe to it.
| Event | Information in the notification |
|---|---|
sequence-created | The Sequence that was created |
sequence-updated | The Sequence as it is after the change |
sequence-invocation-created | The run that started when the Sequence was launched for a Tour |
sequence-invocation-action-created | One step of that run, such as the carriers it selected, an offer it sent or the end of the run |
Orbit sends sequence-updated after every saved change to a Sequence:
Placing a Sequence at a position in automatic dispatch renumbers the other ranked Sequences, so you receive one notification for every Sequence whose rank changed. A request that changes nothing, such as saving a Sequence without changes or activating a Sequence that is already active, sends no notification.
Northstar Distribution subscribes to vehicle-created and vehicle-deleted so its fleet register can add vehicles and remove them when they leave Orbit. It also subscribes to carrier-created to update its carrier directory, and to sequence-updated so its dispatch dashboard shows which Sequences are active.
sequence-updated, so your integration sees each Sequence as it is now.