Error Handling
The Glance API uses standard HTTP status codes to indicate success or failure. Errors include a JSON body with details about what went wrong.
Error Response Format
{
"error": "Bad Request",
"message": "Validation failed",
"details": [
{
"field": "email",
"message": "Must be a valid email address"
},
{
"field": "name",
"message": "Required"
}
],
"statusCode": 400
}HTTP Status Codes
| Code | Meaning | Description |
|---|---|---|
200 | OK | Request succeeded |
201 | Created | Resource created successfully |
400 | Bad Request | Invalid request body or parameters |
401 | Unauthorized | Missing or invalid API key |
403 | Forbidden | API key lacks required permissions |
404 | Not Found | Resource does not exist |
409 | Conflict | Resource already exists (e.g. duplicate SKU) |
422 | Unprocessable Entity | Valid JSON but semantic error (e.g. negative quantity) |
429 | Too Many Requests | Rate limit exceeded |
500 | Internal Server Error | Something went wrong on our end |
Validation Errors
When a request body fails validation (status 400), the response includes a details array listing each field that failed and why:
Tip: Always check the
details array for specific field-level errors before retrying a failed request.