Retrieving Container Removals
Scan-outs from mixed containers: what was removed, the expected vs. measured weight drop, and the variance.
Use GET /api/v1/container-removals to page through every record in your organization, or GET /api/v1/container-removals/{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
Compare the expected weight drop to the measured one to see when someone took more than they scanned.
Filter by user_id to see who has the most variance and where extra training would help.
Review every scan-out from shared containers so each SKU's count stays accurate.
Pull removals with variance to write off losses in your books with a clear paper trail.
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)