Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
The Centsless API returns standard HTTP status codes with a JSON body containing a machine-readable error code and a human-readable message. Learn what each status code means.
error, a machine-readable code you can match against in your integration, and message, a human-readable description suitable for logging.
{
"error": "ERROR_CODE",
"message": "Human-readable description"
}
| Status | Meaning |
|---|---|
200 OK | Request succeeded. |
201 Created | Resource created successfully (for example, a new API key). |
400 Bad Request | Validation error — a required field is missing or a field value is not a valid enum option. |
401 Unauthorized | The x-api-key header is missing or the key is invalid. |
403 Forbidden | The API key is valid but lacks permission for the requested endpoint. |
404 Not Found | The requested transaction or resource does not exist. |
429 Too Many Requests | You have exceeded the rate limit for your API key (1,000 req/hr sandbox, 10,000 req/hr production). |
500 Internal Server Error | An unexpected error occurred on the server. Retry with exponential backoff. |
UNAUTHORIZED — 401x-api-key header is absent or the key has been revoked.
{
"error": "UNAUTHORIZED",
"message": "Invalid or missing API key"
}
FORBIDDEN — 403{
"error": "FORBIDDEN",
"message": "Insufficient permissions for this endpoint"
}
VALIDATION_ERROR — 400{
"error": "VALIDATION_ERROR",
"message": "merchant_id is required"
}
NOT_FOUND — 404{
"error": "NOT_FOUND",
"message": "Transaction not found"
}
compliance_status field in transaction responses (PASS, WARN, or FAIL) signals jurisdiction compliance issues. These are separate from HTTP errors — a transaction can return 200 OK with a compliance_status of WARN or FAIL. Check this field in every transaction response alongside the HTTP status.