Retrieving Weight Reports
Historical weight/unit readings reported by bases or entered manually.
Use GET /api/v1/weight-reports to page through every record in your organization, or GET /api/v1/weight-reports/{id} to fetch a single record. The id is a string, and a 404 means it doesn't exist in your organization.
API Endpoint
Current Use Cases
Plot readings for a container to see how fast an item gets used day by day.
Show the exact weight and time behind any count when an auditor or customer asks.
Pull readings around the time stock went missing to see exactly when the weight dropped.
Feed historical readings into your planning tool to predict when you'll run out.
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)