Challonge API is RESTful and uses conventional HTTP response codes to indicate the success or failure of the API request. The table below will help you identify the meaning and the implication of error responses. Additionally, the documentation for many of the endpoints shows sample error responses.As a general rule of thumb:2xx range codes indicate success
4xx range codes indicate a failure from the given information (e.g missing API identifiers, invalid parameters, failed transactions, etc.)
5xx range codes indicate an error on the platform itself.
HTTP Status Codes#
Retrieving and updating a resource uses 200 HTTP code.
Creating a resource uses 201 HTTP Code.
Deleting a resource uses 204 HTTP Code.
The request was not understood, often causes by missing parameters, invalid payload format, validation or processing errors.
You are not authenticated. You might not be passing the Access Token properly.
You are authenticated in the AP but the resource you are accessing is not allowed. This might be missing permissions.
The requested resource or the API endpoint does not exist.
The updated resource was unable to be processed due to an error.
500 Internal Server ErrorSomething went wrong on Challonge's end. Please let us know 🙏
Error Response#
A standard JSON error response is returned whenever an issue is encountered:{
"errors": [
{
"status": 422,
"detail": "Tournament Format is invalid",
"source": {
"pointer": "/data/attributes/tournament_format"
}
}
]
}
400 or 422
A developer-friendly error message of a single error. This can also be used as an error message to inform your end users of the issue that hey encountered. However, if you feel that the detail does not match you needs, you can utilize your own to provide a more suitable, custom error message.
This attribute exists if the error originated from the JSON payload. IF the error is related to the query parameter, for example the :id parameter when retrieving a certain resource, this attribute is not returned. Modified at 2025-11-03 16:52:10
