Retrieving Pick Orders
Picking runs, each batching lines from one or more sales orders in route order.
Use GET /api/v1/pick-orders to page through every record in your organization, or GET /api/v1/pick-orders/{id} to fetch a single record with its related data. The id is a UUID, and a 404 means it doesn't exist in your organization.
API Endpoint
Current Use Cases
Pull open pick orders with their lines in route order so pickers walk the floor once.
Filter by status and assigned_to to see who is picking what right now.
Filter by location_id to group picks for one building and cut walking time.
Compare created and completed times to see how long picking takes per order.
Required Headers
Every request must include the following:
Requests missing either header will return 401 Unauthorized
Example Request
Response Schema
Filters
Errors
Cloudbox uses standard HTTP status codes to indicate API success or failure:
- 200–299 – Request succeeded
- 400 – Bad request (missing parameters, invalid values)
- 401 – Unauthorized (missing or invalid API keys)
- 404 – Resource not found
- 429 – Too many requests (rate limited)