Rate Limits Understanding TaskFlow API's rate limiting policies
Overview To ensure fair usage and maintain service stability, TaskFlow API implements rate limiting on all endpoints. Different endpoints have different rate limits based on their purpose and resource requirements.
Rate Limit Categories
Category Limit Window Applies To
Global 100 requests 15 minutes All endpoints
Authentication 5 requests 1 hour Sign in and Sign up endpoints
API 50 requests 15 minutes All API endpoints
Rate Limit Headers The API returns the following headers with each response:
  • RateLimit-Limit : Maximum number of requests allowed in the window
  • RateLimit-Remaining : Number of requests remaining in the current window
  • RateLimit-Reset : Time when the rate limit window resets (Unix timestamp)
Best Practices
💡 Tips to avoid rate limiting:
  • • Implement caching for frequently accessed data
  • • Batch operations when possible
  • • Use exponential backoff for retries
  • • Monitor the rate limit headers in responses
Rate Limit Errors When you exceed the rate limit, you'll receive a 429 Too Many Requests response with a JSON payload containing:
  • • Error message explaining the limit
  • • Suggested actions to take
  • • Time when you can resume making requests