Bulk Mark Ready for Collection
Send the second signal for multiple non-dedicated orders when their goods are ready for collection. Supply 1–100 distinct order UUIDs from data.id, not short order codes. UUIDs must be unique regardless of letter case. Use the same bearer token and API access as the single-order endpoint, with Accept: application/json and Content-Type: application/json.
Returns 202 Accepted when the updates have been accepted for background processing, before individual readiness updates are confirmed. Each order is processed independently and must belong to the initiating customer’s active workspace membership; another customer in the same workspace cannot update it. Only orders created with requires_ready_for_collection: true are eligible. Unknown, inaccessible, ineligible or terminal orders fail individually during processing without preventing other items from continuing. Individual results are not included in this response.
The existing readiness rules apply: successful repeated signals preserve the original readiness timestamp and do not restart an operational order. Acceptance does not confirm driver assignment or physical collection. Invalid request payloads return 422 and do not enqueue any updates.
Authentication
Request
Response
Updates accepted for background processing; individual readiness updates are not yet confirmed.
