Cycle Counts API

Get access to your cycle counts data through Cloudbox's v1 API.

Retrieving Cycle Counts

Cycle-count sessions (container or SKU mode) with their counted lines.

Use GET /api/v1/cycle-counts to page through every record in your organization, or GET /api/v1/cycle-counts/{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

GET
/api/v1/cycle-counts
GET
/api/v1/cycle-counts/{id}

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/cycle-counts?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
id
string (uuid)
Unique ID
mode
string, nullable
Filterable (exact)
status
string, nullable
Filterable (exact)
user_id
string (uuid), nullable
Filterable (exact)
base_id
string, nullable
started_at
string (ISO 8601), nullable
Sortable
ended_at
string (ISO 8601), nullable
notes
string, nullable
created_at
string (ISO 8601)
Creation timestamp (UTC). Sortable
lines
array of objects
Detail endpoint only. Related records: id, session_id, sku_id, container_id, unit_mode, counted_units, counted_weight, prior_units, prior_weight, gross_weight, tare_weight, net_weight, unit_weight_used, prior_fluid_ounce_qty, final_fluid_ounce_qty, user_id, created_at

Filters

limitPage size (default 100, max 1000)
offsetNumber of records to skip (default 0)
sortOne of: started_at, created_at
orderasc | desc
statusactive | completed | cancelled
modecontainer | sku
user_idCounts performed by this user
started_sinceOnly records started at or after this ISO 8601 timestamp
default sortcreated_at descending

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)