Errors
Global error reference for the Glass Next API — status codes, formats, and handling strategies.
What this means in plain English
When something goes wrong, the API returns a clear error response. This page is your reference for understanding every error type and building robust error handling into your integration.
Coming soon
The global error reference is being expanded for vendor, product, and order endpoints. Auth-related errors are documented below.
Standard error format
All API errors return JSON in this structure:
{
"statusCode": 400,
"message": "Description of what went wrong",
"error": "Bad Request"
}Common status codes
| Code | Name | When it happens |
|---|---|---|
| 200 | OK | Request succeeded |
| 201 | Created | Resource created |
| 400 | Bad Request | Invalid input or validation failure |
| 401 | Unauthorized | Missing or invalid authentication |
| 403 | Forbidden | Authenticated but not permitted |
| 404 | Not Found | Resource doesn't exist |
| 422 | Unprocessable Entity | Valid JSON but business logic rejected |
| 429 | Too Many Requests | Rate limit exceeded |
| 500 | Internal Server Error | Unexpected server error |
Authentication errors
These errors are returned by POST /api/v1/auth/login:
| Status | Message | Meaning |
|---|---|---|
| 401 | Invalid credentials | Wrong email/password, or account is inactive/suspended |
| 403 | USER_NOT_VERIFIED | Account exists but email verification is incomplete |
| 429 | Rate limit exceeded | More than 10 login attempts in 15 minutes |
See the Login endpoint reference for full request/response examples.