Retrieving Barcodes
Barcodes attached to SKUs. Filter by barcode to resolve a scan to a SKU.
Use GET /api/v1/barcodes to page through every record in your organization, or GET /api/v1/barcodes/{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
Filter by barcode to turn any UPC or vendor label a handheld scans into the right Cloudbox SKU.
Store each vendor's barcode against the SKU so the dock can scan whatever label is on the box.
Pull all barcodes and compare against your SKU list to find items that still can't be scanned.
Send barcodes to your POS or WMS so every system recognizes the same scan.
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)