Retrieving SKUs
Individual batches/lots of a product, each with its own quantity, tracking ID, expiry, and Location > Section > Placement.
Use GET /api/v1/skus to page through every record in your organization, or GET /api/v1/skus/{id} to fetch a single record with its related data. The id is a string, and a 404 means it doesn't exist in your organization.
API Endpoint
Current Use Cases
Pull every batch with its expiration date and sort by it to see which lots need to move first.
Each SKU carries its Location, Section, and Placement, so your WMS or pick sheets point people to the exact spot.
Look up a SKU by tracking_id to tie a Cloudbox batch to its METRC, BioTrack, or WMS record.
Use updated_since on a schedule to sync just the SKUs whose counts changed since your last run.
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)