Key concepts
Errors
Qualy uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, a charge failed, etc.). Codes in the 5xx range indicate an error with Qualy’s servers.
HTTP status code summary
| Number | Error | Description |
|---|---|---|
| 200 | Ok | Everything worked as expected. |
| 400 | Bad Request | The request was unacceptable, often due to missing a required parameter. |
| 401 | Unauthorized | No valid API key provided. |
| 403 | Forbidden | The API key doesn’t have permissions to perform the request. |
| 404 | Not Found | The requested resource doesn’t exist. |
| 409 | Conflict | The request conflicts with another request. |
| 500, 502, 503, 504 | Server Errors | Something went wrong on Qualy's end. |
Error response
This is an example of what an error response looks like:
{
"statusCode": 500,
"message": "Internal server error"
}
If the request failed due to the lack of permissions, Qualy will return what roles are necessary to perform the requested operation.
{
"statusCode": 403,
"message": "This action is forbidden because the user lacks necessary roles.",
"data": {
"roles": [
"paymentIntents:edit:all",
"paymentIntents:edit:me",
"paymentIntents:edit:team"
]},
"error": "Forbidden"
}