Plytix
Guides

Rate limits

How Plytix enforces API rate limits, what happens when you exceed them, and where to check the limits for your account plan.

Plytix enforces rate limits on the API so that no single account can degrade the platform for everyone else. This page covers how those limits work, what happens when you exceed them, and where to check the limits for your plan.

How rate limits work

Your account plan sets a limit on how many requests you can make in two time windows: per 10 seconds, and per hour. Every request counts as one hit against both limits at the same time, so you can be blocked by whichever window you exhaust first.

Rate limits are enforced across all resources available in the API, and they're based on your account plan. Some large clients have found their plan's limit too low for occasional high-volume operations, such as uploading a large catalog, and have requested a temporary rate-limit extension for those windows. If your integration needs to do something similar, ask your account manager ahead of time rather than building around the assumption that a temporary extension is automatic.

FLAG

The source material confirms the two time windows and that limits are plan-based, but doesn't give the actual numeric thresholds for either window, or a breakdown of limits by plan tier. Confirm these details with Plytix before treating them as final.

Exceeding your limit

If you reach either limit, the API returns a 429 TOO MANY REQUESTS status code. Every request you make keeps returning 429 until the time interval for the limit you hit expires.

See Status codes and error codes for the full list of HTTP status codes the API returns.

Checking your plan's limits

Rate limits vary by account plan. To find the limits that apply to your account, check the Plytix pricing page or ask your account manager.

FLAG

No source material documents a way to check your current rate limit or usage from within the API itself (for example, no rate-limit response headers). If Plytix exposes this some other way, it should be added here.

On this page