Stops must be referenced by their Qargo stop id. Location names, using location details or aliases are not supported.
Each stop must have a sequence value (starting from 0) and a start/end timestamp. Missing either will cause the import to fail.
Resources can only be assigned by their Qargo resource id — not by license plate, name, or external reference.
All stops in the payload must be unplanned. Stops that are already assigned to another trip cannot be imported.
Trips are created automatically — there is no approval or review step before the trip appears on the planning board (unlike order import).
A cancelled trip cannot receive further updates. To re-import, use a new trip_identifier.
Stop timestamps must be logically consistent: the sequence order must match the chronological order, and a delivery stop cannot precede its corresponding pickup.
Trip import is asynchronous — the endpoint does not return trip data.
Splitting a trip into multiple trips is not supported via trip import - split the order first.
Each integration instance supports either webhook or EDI routing — not both simultaneously.