Peere Network uses standard HTTP status codes to indicate the success or failure of API requests. Understanding these codes helps you handle responses appropriately in your integration.Documentation Index
Fetch the complete documentation index at: https://docs.peere.network/llms.txt
Use this file to discover all available pages before exploring further.
Success Codes
| Code | Name | Category | Description |
|---|---|---|---|
| 200 | OK | Success | The request was successful |
| 201 | Created | Success | A new resource was successfully created |
| 202 | Accepted | Success | The request was accepted but not yet processed |
| 204 | No Content | Success | Request succeeded with no response body |
| 301 | Moved Permanently | Redirection | The resource has been permanently moved |
| 302 | Found | Redirection | The resource is temporarily available elsewhere |
| 304 | Not Modified | Redirection | Cached version can be used |
| 400 | Bad Request | Client Error | Invalid request or malformed syntax |
| 401 | Unauthorized | Client Error | Authentication is required |
| 403 | Forbidden | Client Error | You do not have permission to access this resource |
| 404 | Not Found | Client Error | The resource could not be found |
| 405 | Method Not Allowed | Client Error | HTTP method is not supported for this resource |
| 409 | Conflict | Client Error | Request conflicts with current server state |
| 422 | Unprocessable Entity | Client Error | Validation failed on request data |
| 429 | Too Many Requests | Client Error | Rate limit exceeded |
| 500 | Internal Server Error | Server Error | An unexpected server error occurred |
| 502 | Bad Gateway | Server Error | Invalid response from upstream server |
| 503 | Service Unavailable | Server Error | Server is temporarily unavailable |
| 504 | Gateway Timeout | Server Error | Upstream server failed to respond in time |