Skip to main content
Rate limits protect the API from abuse and ensure fair usage for all consumers.

​
Limits

​
Response When Limited

When you exceed a rate limit, the API returns:
  • HTTP 429 Too Many Requests
  • Error code: RATE_LIMIT_EXCEEDED
  • Retry-After header: number of seconds to wait before retrying

​
Rate Limit Headers

Every response includes standard rate limit headers per the IETF RateLimit header fields specification:

​
Best Practices

  1. Respect Retry-After — when you receive a 429, wait for the specified number of seconds
  2. Monitor rate limit headers — parse the RateLimit header to check remaining requests and throttle proactively
  3. Use exponential backoff — if retrying, increase delay: 1s, 2s, 4s
  4. Cache results — Human Design charts for the same birth data are deterministic. Cache responses to avoid redundant calls
  5. Batch wisely — if generating multiple charts, space requests evenly rather than bursting