Webhook for updates to orders. Subscribe to this endpoint to receive updates. Trip updates are not sent by default and require a custom setup configured by Qargo. Contact success@qargo.com to discuss setting this up.
By default, Qargo sends payloads using the OperationalVisibilityUpdate schema:
orderforOrderUpdate,StopUpdate,DocumentUpdate,EtaUpdate, andHandlingUnitUpdateevents.
OrderImportUpdate and other events not listed above may not include order. The trip field is not populated by default; including it requires a custom webhook format configured by Qargo.
A custom webhook format configured by Qargo may use a different structure.
Events tracked in this update. PositionUpdate is not implemented yet. 🚧
Current state of the order. Included for OrderUpdate, StopUpdate, DocumentUpdate, EtaUpdate, and HandlingUnitUpdate events. Never included together with trip on the same event.
- https://api.qargo.comhttps://api.qargo.com/https://<visibility-event-receiving-endpoint>
{ "events": [ { … } ], "order": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "order_name": "INV-7980", "customer_reference_number": "string", "customer": { … }, "status": "ACCEPTED", "custom_fields": {}, "stops": [ … ], "consignment": { … } }, "trip": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "orders": [ … ], "stops": [ … ] } }