Authentication and Rate Limits
Last updated
Last updated
Every request to access the Haiku Enterprise API must include a valid API key in the request headers. This ensures secure and authenticated interactions with the API.
Contact [email protected] to request an API key
Complete the integration questionnaire to verify usage requirements
Receive both production and sandbox API keys.
Once you have your API key, include it in every request as a bearer token in the api-key header.
Never expose your API key in client-side applications
Store API keys securely in backend services or environment variables
If an API key is compromised, revoke it immediately and request a new one.
OAuth-based authentication (coming soon)
Role-based access control for different API functions
To ensure fair usage and maintain system performance, the Haiku Enterprise API enforces the following rate limits
Current rate limits
Requests per minute
100
Burst limit (per second)
15
If the rate limit is exceeded, the AI will return a 429 - Too Many Requests error.
Follow these guidelines to avoid hitting rate limits:
Use caching: reduce redundant API calls by caching responses where possible.
Implement exponential backoff: when receiving 429 - Too Many Requests, wait and retry with increasing intervals.
