Retrieving Purchase Orders
Purchase orders with their lines and receiving history.
Use GET /api/v1/purchase-orders to page through every record in your organization, or GET /api/v1/purchase-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 POs by status to see what's ordered, partially received, and still outstanding.
Compare receiving history against vendor invoices before you approve payment.
Send purchase orders to QuickBooks or your ERP so committed spend shows up in the books.
Compare order dates to received dates to see which vendors actually deliver on time.
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)