Skip to main content

Rate Limits

FLTR uses rate limiting to ensure fair usage and system stability.

Overview

Rate limits are enforced per account based on authentication method:

Rate Limit Headers

Every API response includes rate limit information:
integer
Total requests allowed per hour
integer
Requests remaining in current window
integer
Unix timestamp when limit resets

Check Your Usage

When Rate Limited

If you exceed your limit, you’ll receive a 429 status code:
The retry_after field indicates seconds until you can retry.

Best Practices

1. Implement Exponential Backoff

2. Cache Frequent Queries

3. Use Batch Endpoints

4. Monitor Usage

Track your usage to avoid hitting limits:

5. Spread Requests

Instead of bursting requests, spread them out:

Increase Your Limits

Upgrade to OAuth

OAuth authentication provides 15x higher limits:
  • API Key: 1,000 requests/hour
  • OAuth: 15,000 requests/hour

OAuth Setup

Upgrade to OAuth for higher limits →

Enterprise Plans

Need even higher limits? Contact sales for:
  • Custom rate limits
  • Dedicated infrastructure
  • SLA guarantees
  • Priority support

Contact Sales

Discuss enterprise pricing →

Rate Limit Scope

Per Account

Rate limits are per account, not per API key.
Creating multiple API keys does not increase your limit.

Per Hour

Limits reset every hour on a rolling basis:

Separate Limits

Each service has independent limits:
  • FLTR API: 1,000/hour
  • Webhooks: Unlimited (deliveries don’t count)

Endpoint-Specific Limits

Some endpoints have additional constraints:

Fair Use Policy

While there are technical rate limits, we also have a fair use policy: Allowed:
  • Production applications
  • Automated workflows
  • Integration services
  • Testing and development
Not Allowed:
  • Excessive scraping
  • DoS attacks
  • Reselling API access
  • Violating ToS
Accounts violating fair use may be suspended.

Monitoring in Production

Log Rate Limit Metrics

Alert on High Usage

Dashboard Metrics

Track over time:
  • Requests per hour
  • Peak usage times
  • Rate limit hit frequency
  • Average remaining quota

Testing Rate Limits

Simulate Rate Limiting

Load Testing

Test your implementation:

FAQ

Q: Can I request a temporary limit increase? A: Yes, contact support@fltr.com with your use case. Q: Do failed requests count toward the limit? A: Yes, all requests count including 4xx and 5xx errors. Q: Does listing datasets use the same limit as queries? A: Yes, all API endpoints share the same rate limit. Q: Can I purchase additional requests? A: We offer enterprise plans with custom limits. Contact sales. Q: How long are limits enforced after exceeding them? A: Limits reset hourly on a rolling basis.

Resources

Authentication

Upgrade for higher limits

Batch Query

Reduce requests with batching

Troubleshooting

Common issues and fixes

Contact Support

Need help with limits?