Error Handling

Error handling

The Hypetech API uses HTTP status codes to indicate the status of requests: - 2xx: Successful requests. - 4xx: Errors related to the data sent or the current state of entities. - 5xx: Internal service issues.

Additionally, errors follow the RFC 7807 standard, with structured details to facilitate diagnosis and resolution.

Goal: Our objective is to ensure clarity and simplicity in error handling, allowing you to diagnose and resolve issues quickly.

Error Types

This section gathers errors that could be returned by any endpoints listed in the Hypetech API.

Bad Request

Meaning: Invalid request.
HTTP Status Code: 400 Bad Request.

Forbidden

Meaning: Authenticated participant request that violates some authorization rule.
HTTP Status Code: 403 Forbidden.

Not Found

Meaning: Entity not found.
HTTP Status Code: 404 Not Found.

Gone

Meaning: Indicates that the entity existed but has been permanently removed.
HTTP Status Code: 410 Gone.

Internal Server Error

Meaning: Unexpected condition when processing request.
HTTP Status Code: 500 Internal Server Error.

Service Unavailable

Meaning: Service is currently unavailable. Requested service may be under maintenance or out of the operating window.
HTTP Status Code: 503 Service Unavailable.

Gateway Timeout

Meaning: Indicates that the service took longer than expected to return.
HTTP Status Code: 504 Gateway Timeout.