Rate limiting ensures the stability and reliability of the AnydealsUK API for all users. This page explains how rate limits work, the limits associated with each subscription tier, how the system enforces fair usage, and how to avoid being temporarily rate-limited.

1. Why Rate Limits Exist #

Rate limits prevent excessive or abusive API usage that could:

• Slow down feed delivery for other users
• Overload the API infrastructure
• Cause unnecessary server strain

Fair usage ensures a consistent and predictable experience for everyone.

2. How Rate Limits Are Applied #

Rate limits are calculated on a per-hour basis, depending on your subscription tier.

When you exceed the limit:

• The API returns 429 Too Many Requests
• A retry_after_seconds value is provided
• You must wait until the window resets

Limits automatically refresh every hour.

3. Rate Limits by Subscription Tier #

Below are the general rate limits associated with each tier.

These limits apply to all API endpoints combined, not just feeds.

4. How the System Counts Requests #

The rate-limit counter increments when you:

• Fetch CSV / XML / RSS / JSON feeds
• Call /status
• Call /networks
• Use the link validation endpoint
• Use any other API endpoint

Static assets (like images) do not count toward API limits.

5. Example Scenarios #

Example A — Telegram Bot Pulling 10-Minute Feed #

Ultra Pro allows ~12 requests/hr.

If your bot checks every 5 minutes:

12 requests/hr → WITHIN LIMIT

Example B — WordPress Cron Import #

Pulse Pro feed refreshed every 30 minutes:

2 requests/hr → VERY SAFE

Example C — Custom App Polling Too Often #

Polling every 2 minutes:

30 requests/hr → WILL BE RATE-LIMITED

6. 429 Rate-Limited Error Explained #

When the API returns:

{
  "error": "Rate Limited",
  "retry_after_seconds": 60,
  "code": 429
}

It means you exceeded your plan’s hourly limit.

To resolve:

• Reduce polling frequency
• Implement caching
• Wait for the rate-limit window to reset

7. Recommendations to Avoid Rate Limiting #

A. Cache Feed Responses #

Instead of reloading feeds unnecessarily, cache the last response.

B. Match Feed Requests to Your Tier #

If you’re on a 60-minute plan, do not request feeds every 5 minutes.

C. Avoid Large Bursts #

Spread out requests instead of hitting the API with dozens of calls at once.

D. Use Conditional Requests (future feature) #

Checking only when new deals are available reduces load.

8. What Happens During Excessive Abuse #

If repeated abuse occurs:

• Temporary IP bans may be applied
• API keys may be locked for security
• You will be contacted if abnormal usage is detected

This ensures service reliability for all subscribers.

9. How to Request Higher Limits #

If you legitimately require a higher rate limit:

• Contact support via your dashboard
• Provide details of your use case
• Higher limits may be granted, dependent on use

10. Summary #

API rate limits ensure stable and fair access to AnydealsUK services for all users. By respecting the limits and following best practices such as caching and responsible polling, you can maintain unrestricted access while keeping system performance optimal.

Next: API Response Examples.

_End of Pa