DID THIS ARTICLE SOLVE YOUR ISSUE?
Let us know so we can improve!
Let us know so we can improve!
The Query Services APIs return standard HTTP status codes to indicate the success or failure of a request. This document provides details about the status codes and their meanings.
| Status Code | Description | Details |
|---|---|---|
| 200 OK | Request successful | The request was processed successfully and the response contains the requested data. |
| 400 Bad Request | Invalid request | The request was malformed or contained invalid parameters. Check the request syntax and parameters. |
| 403 Forbidden | Authorization failed | The request failed to pass authorization. Verify your authentication credentials and permissions. |
| 404 Not Found | Resource not found | The requested resource (callback ID, verification key, or both) was not found. |
| 422 Unprocessable Entity | Invalid attribute | The attribute name used in fields/filter parameter doesn’t exist. Verify the field names in your query. |
| 429 Too Many Requests | Rate limit exceeded | Too many requests were made in a given time period. |
| 500 Server Error | Internal error | An unexpected error occurred on the server. Contact support if the issue persists. |
When an error occurs, the response includes:
error: Error message describing the issueerrorCode: Unique identifier for the error typedetails: Additional information about the error (if available)The following are examples of error code request and responses.
1{
2 "error": "Invalid SQL query syntax",
3 "errorCode": "INVALID_SQL",
4 "details": "Syntax error at line 1: unexpected token 'FROM'"
5}1{
2 "error": "Insufficient permissions",
3 "errorCode": "FORBIDDEN",
4 "details": "User does not have permission to access this resource"
5}1{
2 "error": "Rate limit exceeded",
3 "errorCode": "RATE_LIMIT",
4 "details": "Rate limit exceeded for this organization"
5}errorCode field can be used for programmatic error handling