Fair usage policy

The feeds are a shared resource used by hundreds of resellers. To keep them fast and reliable for everyone, fair usage limits apply.

The limit

The limit is counted per account key — every download made with any of your feed URLs counts toward the same allowance, whichever feed, format or currency it is, and wherever the request comes from.

These limits are live as of 3 September 2026.

Response codes

Retrying after a 429 will get you blocked

This is the single most common way integrations break.

Once you have had a 429, further calls in that same hour still count. If the total reaches 15 requests in the hour, your account key is automatically blocked and every feed URL on your account starts returning 403 — not just the one that tripped the limit. A sync that retries on failure can cross that line in seconds without anyone noticing.

Make sure your integration treats 429 as "stop until next hour", not as a transient error to retry through. Neither 429 nor 403 is recoverable by trying again.

Staying within the limit

The recommended intervals are built to fit: the update feed once an hour, the full feed once a day off-peak. Feed data refreshes roughly every 5 minutes, so polling more often than hourly gains you very little.

If you pull more than one currency or more than one format, count them together — they share the same allowance. A single hourly update feed plus a daily full feed uses 2 in the hour the full feed runs; two currencies uses 4. Keep some headroom.

• Poll on a schedule, not on demand — a server-side cron job, not a page-visit trigger.
• Pull only the feeds you actually use. If you don't need a second format, don't fetch it.
• Cache what you've downloaded rather than re-fetching the same feed twice in one cycle.
• Never retry a 429 within the same hour.
• Remember that testing counts. Previews from import tools, staging environments and manual downloads all draw on the same allowance.
• If your integration runs from more than one server, make sure they aren't each pulling on their own schedule — the allowance is shared across all of them, regardless of where they run.

Your feed URL is a credential

Your feed URL contains your account key. It is not tied to an individual user login — anyone holding the URL can download your feed and see your account pricing, and every request made with it counts toward your limit.

That means usage you don't control is still counted as yours: your live site, your staging site, import-tool previews, and anyone you have passed the URL to. If someone else uses your URL heavily, your account key is what gets blocked — your own sync stops working, not theirs. Don't share your feed URLs, publish them, or commit them to public repositories.

If your URL has been shared or exposed, contact your account manager and we will issue you a new key. The old URL then stops working, so update your integration when you receive the new one.

Blocking

Blocks apply to your account key, and blocked requests return 403 Forbidden on every feed URL for that account.

Blocks are lifted manually — there is no automatic expiry. If your sync starts returning 403, contact your account manager rather than retrying.

Because the block follows the key rather than a network address, changing server, connection or IP address will not restore access, and it makes no difference whether your integration is dual-stack or moves between addresses.

Need more than 5 per hour?

If your integration has a genuine need for a higher allowance, talk to your account manager — we'd rather size it correctly with you than have your sync break. Tell us what you're pulling: which feeds, which formats and currencies, how often, and from how many servers.