Retrieving Stations
Physical work stations where MOs are built.
Use GET /api/v1/stations to page through every record in your organization, or GET /api/v1/stations/{id} to fetch a single record. The id is a UUID, and a 404 means it doesn't exist in your organization.
API Endpoint
GET
/api/v1/stations
GET
/api/v1/stations/{id}
Current Use Cases
Show work by station
Pull every station to build a screen that shows what's being built where.
Route MOs to the right station
Use station data to send each manufacturing order to the station that can build it.
Track station output
Pair stations with completed MOs to see how much each one produces per shift.
Match instructions to stations
Link work instructions to stations so operators only see the steps for their spot.
Required Headers
Every request must include the following:
Header Key
Description
org-api-key
Your Organization API key. Contact Cloudbox Support For Access: support@cloudboxapp.com.
user-api-key
Your User API Key
Requests missing either header will return 401 Unauthorized
Example Request
bash
curl -X GET "https://app.cloudboxapp.com/api/v1/stations?limit=100" \
-H "org-api-key: YOUR_ORG_API_KEY" \
-H "user-api-key: YOUR_USER_API_KEY" \
-H "Accept: application/json"
Response Schema
Column
Type
Description
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)