Placements API

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

Retrieving Placements

Specific spots within a section (e.g. "B2").

Use GET /api/v1/placements to page through every record in your organization, or GET /api/v1/placements/{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/placements
GET
/api/v1/placements/{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/placements?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
name
string
Sortable
section_id
string (uuid), nullable
Section (area within a location) ID. Filterable (exact)
active
boolean
Filterable (exact)
sequence
integer, nullable
Sortable
created_at
string (ISO 8601)
Creation timestamp (UTC). Sortable
updated_at
string (ISO 8601)
Last update timestamp (UTC)
section
object
Detail endpoint only. Related record: id, name, location_id

Filters

limitPage size (default 100, max 1000)
offsetNumber of records to skip (default 0)
sortOne of: name, sequence, created_at
orderasc | desc
searchCase-insensitive partial match on name
section_idPlacements in this section
activeOnly active (true) or inactive (false) (boolean)
default sortname ascending

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)