Shipments
Update Shipment
Modify shipment details before pickup
PATCH
Update shipment details such as pickup schedule, package count, or notes. If any logistics-relevant fields change (pickup date, time, package count, or weight), the existing logistics order is cancelled and a new one is created automatically. Fields you omit are preserved from the existing shipment. Updated schedule fields are validated against the pickup schedule rules.
Request
Path parameters
Shipment reference ID (e.g.,
P2604154821).Body parameters
All body parameters are optional — only include the fields you want to change.New pickup date in
YYYY-MM-DD format, interpreted in the origin location’s timezone.New earliest pickup time in
HH:MM format, interpreted as wall-clock time in the origin
location’s timezone.New latest pickup time in
HH:MM format, interpreted as wall-clock time in the origin location’s
timezone.New number of packages.
New weight in kg.
New notes or remarks. Maximum 128 characters.
Response
On success, the API returns200 OK with the updated shipment.
Shipment reference identifier.
Shipment lifecycle status. One of
pending, in_transit, delivered, fault, or cancelled.Logistics provider. One of
go, dhl, or tof.External tracking number from the logistics provider. May be
null.Pickup address. May be
null.Delivery address. Same structure as
origin. May be null.Scheduled pickup window. May be
null.Optional notes. May be
null.Chronological lifecycle events from the logistics provider (oldest first). Each entry has a
status (free-form provider-sourced label) and time (ISO 8601). Empty array if no events
observed yet.Appointments linked to this shipment, oldest-link first. Each entry is
{ id, added_at };
cross-reference each id against Get Appointment.Creation timestamp (ISO 8601).
Last update timestamp (ISO 8601). May be
null.Error responses
| Status | Description |
|---|---|
400 | Validation error — e.g., invalid date or time format. |
403 | Forbidden — your API key does not have access to this operation or the shipment is outside your access context. |
404 | Shipment not found. |
409 | Shipment cannot be modified after pickup. |
500 | Internal server error. |
502 | Logistics provider rejected the request (e.g., cancellation or re-creation failed). Includes the provider’s error message. |