Response codes
InfluxDB 3 Clustered API endpoints return standard HTTP status codes.
| Status code | Description |
|---|---|
200 OK | Request succeeded. Response body contains the requested data. |
204 No Content | Request succeeded. No response body (common for successful writes). |
400 Bad Request | Malformed request — check syntax, query, or line protocol for errors. |
401 Unauthorized | Missing or invalid token. Verify the Authorization header and token permissions. |
403 Forbidden | Valid token but insufficient permissions for the requested operation. |
404 Not Found | The requested resource does not exist — check the database name and endpoint path. |
422 Unprocessable Entity | The request body is syntactically valid but semantically incorrect. |
429 Too Many Requests | Request rate exceeds cluster limits. Retry with exponential backoff. |
500 Internal Server Error | Server error. If the error persists, contact InfluxData support. |
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB Clustered and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.