Appointments
List Appointment Shipments
Retrieve shipments linked to a specific appointment
GET
Retrieve the full shipment objects linked to a given appointment. Each shipment includes a
status_updates array of lifecycle events observed by the logistics provider — use this to
derive in-transit / delivered state for the appointment without polling the appointment status
itself.
The lighter shipments array on the appointment response itself (see
Get Appointment) carries the same link set as
{ id, added_at } entries — use that when you only need to know what’s linked. This endpoint is
the bulk full-payload shortcut.
Shipments are linked to appointments at creation time via the appointment_id field on
Create Shipment, and managed afterwards via Attach Shipments
to Appointment and the inverse Attach
Appointments to Shipment. Returns an empty
array when no shipments are linked.
Shipments returned here are refreshed from the logistics provider if their last sync was more than
3 hours ago, otherwise they’re served from the DB. Stale-by-up-to-3-hours is the trade-off to
avoid re-fetching on every poll. For force-refreshed truth on a single shipment, use Get
Shipment.
Requires
shipments_manage or test_sessions_view scope.Request
Path parameters
Unique identifier (UUID) of the appointment.
Response
On success, the API returns200 OK with an array of shipment objects. See
Get Shipment for the full field list — each entry has the same
shape, including status_updates.
Error responses
| Status | Description |
|---|---|
400 | Invalid ID format. |
403 | Forbidden — your API key does not have access to this operation, or the appointment is outside your scope. |
404 | Appointment not found. |
500 | Internal server error. |