Error Handling & Debugging

The Haiku Enterprise API provides detailed error responses to help developers quickly identify and resolve issues. All API errors follow standard HTTP response codes, and additional details are provided in the response body.

If an API request fails, follow these steps:

1. Check the Error Message: Read the messagefield in the JSON response for specific details.

2. Verify Request Formatting: Ensure all request headers are included and confirm the request matches the expected structure.

3. Confirm API Key Validity: Xheck if the API key is valid and not expired. Run a simple test with GET /tokenList to see if authentication works.

4. Handle Rate Limits Properly: If you get a 429 error, check the rate limit headers.

5. Check Haiku API Status: Look at the status page for known outages or maintenance.

6. Contact Support: If the issue persists, reach out to support with:

   1. The error response JSON

   2. The request payload

   3. The timestamp of the request

   4. Any relevant logs or transaction IDs

Status Code	Error Type	Description
400	Bad Request	The request is malformed or contains invalid parameters
401	Unauthorized	Missing or invalid API key
429	Too Many Requests	The rate limit has been exceeded
500	Internal Server Error	Unexpected issue on the API side

When an error occurs, the API responds with a structured JSON error message.

Example: 400 Bad Request (Invalid Parameters)

{
  "status": "error",
  "message": "Invalid request parameters",
  "code": 400
}

Example: 401 Unauthorized (Missing API Key)

Verify the API key is included and valid.

{
  "status": "error",
  "message": "Unauthorized. Please provide a valid API key.",
  "code": 401
}

Example: 429 Too Many Requests (Rate Limit Exceeded)

Reduce request frequency and implement rate limit handling.

{
  "status": "error",
  "message": "Too many requests. Please wait before retrying.",
  "code": 429
}

Example: 500 Internal Server Error

If the error persists, contact [email protected].

{
  "status": "error"
  "message": "Internal server error."
  "code": 500
}