title: HTTP Status Codes
description: HTTP status codes returned by the Wontopos API and their meanings.
HTTP Status Codes
Standard HTTP status codes with Wontopos-specific context.
Success codes
| Code | Name | Wontopos usage |
|---|---|---|
200 | OK | Request succeeded. Response body contains the requested data. |
201 | Created | Resource created successfully. Returned by POST endpoints. |
204 | No Content | Request succeeded with no response body. Returned by DELETE endpoints. |
Client error codes
| Code | Name | Wontopos usage |
|---|---|---|
400 | Bad Request | Invalid parameters, malformed JSON, or missing required fields. |
401 | Unauthorized | Missing, expired, or invalid API key. |
403 | Forbidden | Valid authentication but insufficient scope or permissions. |
404 | Not Found | The requested resource does not exist or has been deleted. |
405 | Method Not Allowed | The HTTP method is not supported for this endpoint. |
409 | Conflict | Attempting to create a resource that already exists. |
422 | Unprocessable Entity | Request is well-formed but fails business logic validation. |
429 | Too Many Requests | Rate limit or daily quota exceeded. Check Retry-After header. |
Server error codes
| Code | Name | Wontopos usage |
|---|---|---|
500 | Internal Server Error | Unexpected server error. Retry or contact support with the request_id. |
502 | Bad Gateway | Upstream API returned an invalid response. |
503 | Service Unavailable | The API is temporarily down for maintenance. Check the status page. |
504 | Gateway Timeout | Upstream API did not respond in time. |
Error details
All 4xx and 5xx responses include a JSON error body with `code`, `message`, `status`, and `request_id`. See [Error Codes](/docs/reference/error-codes) for the full list.