Retrieving Operations
Routing: the planned operations (with resource, minutes, and cost) to make a product/SKU. MOs copy these into their own operations.
Use GET /api/v1/operations to page through every record in your organization, or GET /api/v1/operations/{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
Add up minutes and cost per operation to price a product before you quote it.
Total the planned minutes per resource to see if a machine or crew is overbooked.
Send the step-by-step routing for each product to your ERP or MES.
Match planned operations against what each MO actually logged to find slow steps.
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)