In this article
The DNSFilter API has rate limiting to enhance system stability and security. Before this update, our core API did not restrict incoming requests, which has led to instances where excessive usage by a single customer negatively impacted system performance for all users and could potentially compromise system integrity.
The implementation of API rate limiting aims to:
-
Prevent service disruptions caused by excessive API requests, ensuring fair access for all users
-
Reduce the risk of system instability due to misuse or malicious activity
-
Implement messaging to notify users when they exceed rate limits
How API Rate Limiting Works
The current API rate limit is 4,000 requests per 300 seconds.
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.
Comments
0 comments
Please sign in to leave a comment.