In this article

The DNSFilter API includes rate limiting, aimed at strengthening system reliability and security.

Rate limiting ensures that all customers enjoy consistent, uninterrupted service by maintaining balanced performance across our platform.

With rate limiting in place, we can:

• Guarantee fair access for every customer, preventing any single set of requests from affecting overall performance
• Protect system stability by proactively managing unexpected or unusual usage patterns
• Provide clear communication by notifying customers when rate limits are exceeded, so usage can be easily adjusted

This reinforces our commitment to delivering a stable, secure, and high-quality experience for all DNSFilter users.

How API Rate Limiting Works

The current API rate limit is 2,000 requests per 300 seconds per Organization. 

API requests include direct API users utilizing API tokens and users accessing the platform via web or mobile apps. This ensures fair usage across all access methods and prevents excessive load on our systems.

When a user exceeds their allotted API request limit, the system will return an HTTP 429 Too Many Requests response. This response includes standard rate-limit headers to help developers monitor and manage API usage efficiently:

• Retry-After – Specifies the waiting period before making a new request

• RateLimit-Policy – Outlines the rate-limiting policy

• RateLimit – Displays the current request count and limits

• RateLimit-Limit – Indicates the maximum allowed requests within a timeframe

• RateLimit-Remaining – Shows the number of requests left before reaching the limit

• RateLimit-Reset – Provides a timestamp for when limits reset

By monitoring these headers, users can optimize their API interactions and avoid disruptions.

For further assistance, review our API documentation or submit a request to our Support team.