The Clopos API uses RESTful endpoints with JSON payloads and standard HTTP status codes.
Base URLs
Authentication
All API endpoints require three specific headers for authentication:x-brand- Your brand identifierx-venue- Your venue identifierx-token- Access token from/authendpoint
1
Get API credentials
Obtain your
client_id, client_secret, brand, and venue_id from your Clopos dashboard2
Generate access token
Exchange your credentials for an access token using the
/auth endpoint3
Include required headers
Add all three headers to every API request (except
/auth)Required Headers
Get Access Token
First, authenticate with your credentials:Rate Limits
API requests are rate limited to ensure fair usage:- 100 requests per minute per API key
- 1000 requests per hour per API key
When rate limits are exceeded, the API returns a
429 Too Many Requests status code.Error Handling
The API uses standard HTTP status codes and returns detailed error information:Common Status Codes
| Status Code | Description |
|---|---|
200 | Success |
201 | Created |
400 | Bad Request - Invalid parameters |
401 | Unauthorized - Invalid or missing token |
403 | Forbidden - Insufficient permissions |
404 | Not Found - Resource doesn’t exist |
429 | Too Many Requests - Rate limit exceeded |
500 | Internal Server Error |
Pagination
List endpoints support pagination usinglimit and offset parameters:
Idempotency
POST requests support idempotency using theIdempotency-Key header: