HTTP Status Codes
This page is a quick reference for HTTP response codes commonly used in the client REST API.
Success
| Code |
Meaning |
| 200 |
Request completed successfully |
| 201 |
Resource created successfully |
| 202 |
Request accepted for asynchronous processing |
| 204 |
Request completed successfully with no body |
Client Errors
| Code |
Meaning |
| 400 |
Invalid request payload or validation error |
| 401 |
Authentication failed or authorization token is missing |
| 403 |
Authenticated, but access to the resource is forbidden |
| 404 |
Requested resource was not found |
| 405 |
HTTP method is not allowed for this endpoint |
| 409 |
Request conflicts with the current resource state |
| 422 |
Request is syntactically correct but semantically invalid |
| 429 |
Too many requests |
Server Errors
| Code |
Meaning |
| 500 |
Internal server error |
| 501 |
Requested method or capability is not implemented |
| 502 |
Invalid response from an upstream service |
| 503 |
Service temporarily unavailable |
| 504 |
Upstream timeout |
Notes
- The platform usually returns a machine-readable
error field in the response body.
- Endpoint-specific pages are the source of truth for exact validation rules and response semantics.
- Some business-level failures still use HTTP
400 together with a domain-specific error code.