Skip to main content
The Tibbie API enforces rate limits to ensure fair usage and platform stability.

Limits

Rate limits are applied per authenticated user. If you’re not authenticated, limits are applied per IP address.

Response headers

Every API response includes headers to help you track your current rate limit usage:

Handling rate limits

When you exceed a rate limit, the API returns a 429 Too Many Requests response.

Response

Check the x-ratelimit-reset header for when the limit resets, or simply wait and retry.

Exponential backoff

Use exponential backoff to handle rate limits gracefully:

Best practices

  • Space out requests — Don’t batch too many at once
  • Cache responses — Reuse data when possible
  • Monitor headers — Check x-ratelimit-remaining proactively
  • Queue requests — For bulk operations, use a job queue with delays
Last modified on February 21, 2026