Response codes
InfluxDB Cloud Serverless API endpoints return standard HTTP status codes. The following table summarizes the most common response codes.
| Status code | Meaning |
|---|---|
200 OK | Success. |
201 Created | The resource was created. |
204 No Content | Success with no response body (typically after write or delete). |
400 Bad Request | Request parameters or body are malformed or invalid. |
401 Unauthorized | Missing or invalid credentials. |
403 Forbidden | Credentials lack permission for the requested resource. |
404 Not Found | The requested resource does not exist. |
413 Payload Too Large | Request body exceeds the maximum allowed size. |
422 Unprocessable Entity | Request body is well-formed but semantically invalid. |
429 Too Many Requests | Rate limit exceeded. |
500 Internal Server Error | Unexpected server error. |
503 Service Unavailable | Server is overloaded or under maintenance. |
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 Cloud Serverless and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.