HTTP Response Codes

CompetitionSuite uses standard HTTP response codes to indicate the success or failure of API requests.

Response Code Ranges

2xx Success
The request was successful and the server has processed it as expected.

4xx Client Error
The request contains an error or cannot be fulfilled due to client-side issues, such as missing required parameters, invalid authentication, or malformed requests.

5xx Server Error
An error occurred on CompetitionSuite's servers. These errors are rare and typically indicate temporary issues with our infrastructure.

Error Handling

Client errors (4xx) may include additional error information to help with programmatic handling:

Error Code: A brief identifier for the specific error type

Error Message: A human-readable description of what went wrong

Additional Context: When applicable, details about which parameters or fields caused the issue

Common Response Codes

Code	Status	Description
200	OK	Request successful
201	Created	Resource successfully created
400	Bad Request	Invalid request format or missing required parameters
401	Unauthorized	Authentication required or invalid credentials
403	Forbidden	Valid authentication but insufficient permissions
404	Not Found	Requested resource does not exist
422	Unprocessable Entity	Valid request format but contains semantic errors
429	Too Many Requests	Rate limit exceeded
500	Internal Server Error	Unexpected server error
502	Bad Gateway	Temporary server issue
503	Service Unavailable	Server temporarily unavailable

Best Practices

Always check the HTTP status code before processing the response body

Implement retry logic for 5xx errors with exponential backoff

Parse error codes in 4xx responses for specific error handling

Log unexpected errors for debugging purposes

Errors

HTTP Response Codes#

Response Code Ranges#

Error Handling#

Common Response Codes#

Best Practices#

HTTP Response Codes

Response Code Ranges

Error Handling

Common Response Codes

Best Practices