Update Return
Updates an existing Return’s ticket and/or its Return Shipment. Both body objects are optional — send what changes.
Identification (query parameters): standard flow — return_uuid,
return_id, or shipment_uuid; preprinted-label flow — shipment_id
or shipment_uuid.
Rules:
- Write-once fields:
return_id,cost_of_return,requested_date,shipment_id. - Do not send
tracking_numberorcarrier_reference— the Return Booking Service sets them when the return label is generated. - Ticket fields and most shipment fields replace their stored values
entirely (whole arrays, whole address objects);
tags,events,linked_shipments,documentsare add-only, as on Update Shipment. - A Return Shipment cannot be updated after a successful carrier booking.
Identical update requests are deduplicated for 30 seconds.
Authorizations
Used by every functional endpoint. Generate the token with POST /auth/oauth/token/ and send it as Authorization: Bearer {token}.
Query Parameters
Perform.AI return identifier (standard flow).
Your return identifier (standard flow).
50The Return Shipment's Perform.AI identifier (both flows).
The Return Shipment's identifier (preprinted-label flow).
50Body
The Return Ticket — the return request's own data. All fields are optional.
Same fields and constraints as Create Shipment; no field is required. Most fields replace the stored value entirely (whole arrays, whole address objects); tags, events, linked_shipments, and documents are add-only.