Troubleshooting
This section describes possible solutions to the issues that you might experience when using the Database API.
HTTP error codes
The Database API uses the following error codes:
Error code | Description |
---|---|
400 Bad Request | The request is incorrect. Make sure the request body follows the schema. |
401 Unauthorized | The authentication credentials are missing or invalid. Check if your access token hasn't expired. |
403 Forbidden | You aren't authorized to view or modify the requested resource. Make sure you are in the right access group. |
405 HTTP Method Not Allowed | The method that you used isn't supported for the requested resource. For all the available methods, see API reference. |
408 Request Timeout | The server timed out waiting for the request. Try again. |
424 Failed Dependency | The request failed because it depended on another request that failed. Try again or contact support if the error persists. |
500 Internal Server Error | An unexpected error ocurred. Contact support. |
503 Service Unavailable | Database Service is temporarily unavailable. Try again in a few minutes. You can also use the health check endpoint to learn more. |
Response times out
When a response times out, Database Service might be temporarily unavailable. Try again after a few minutes.
Health check endpoint
To verify the current state of the Database Service, use the health check endpoint:
GET {baseUrl}/management/health
Sample response:
{
"status": "UP",
"groups": ["liveness", "readiness"]
}
Was this page helpful?