Qargo Use case / Subcontractor dispatch API
Required api role: not applicable (push/push) Purpose: This interface allows an external party to integrate with 3rd party transport management systems for subcontracting. The subcontractor dispatch uses a push/push model: Qargo pushes a dispatch payload to an external endpoint. The third party then updates Qargo using our webhook endpoint:  Subsequent updates or cancellations will also be sent via this webhook, using the same payload format. The dispatch format has the following structure:  The destination of this webhook can be a RESTful interface or file base protocol like SFTP The [status update endpoint](/docs/use-case-subcontractor-dispatch/subcontractor-status-update-webhook) can be used to receive information about the stops back to Qargo. Status update date-time values, including `event_time`, `eta_start`, and `eta_end`, must include a timezone offset such as `Z` or `+02:00`.