Error handling
Learn how to handle errors when using Hyperline’s API
The Hyperline API uses conventional HTTP response codes to indicate the success or failure of an API request. This page details how to handle errors effectively and what to expect in error responses.
HTTP Status Codes
The API uses standard HTTP status codes to indicate the success or failure of requests:
- 2xx Success: The request was successful
- 4xx Client Error: The request was invalid or cannot be processed
- 5xx Server Error: An internal server error occurred
Error Response Format
When an error occurs, the API returns a JSON response with a message
property containing a human-readable description of the error:
Common Error Codes
400 Bad Request
The request was malformed or contains invalid parameters.
401 Unauthorized
The request lacks valid authentication credentials.
404 Not Found
The requested resource was not found.
429 Too Many Requests
The request rate limit has been exceeded. See Rate Limiting for more details.
Getting Help
If you encounter an error that you cannot resolve, please:
- Check the error message for guidance
- Verify your request format and parameters
- Ensure your authentication credentials are valid
- Contact our support team with the error details and request information