iconik · Rate Limits

Iconik Rate Limits

iconik applies request-rate limiting to its REST API. Per its API documentation, clients are limited to roughly 50 requests per second sustained, or 1000 requests over any 20-second window, per set of application credentials. Responses carry a RateLimit-Remaining header so callers can track their remaining budget, and exceeding the limit returns HTTP 429. Consumable resources (storage, egress, AI, and services) are governed separately by your plan's credit allowances rather than by request-rate limits.

Iconik Rate Limits is the machine-readable rate-limit profile for iconik on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests and credits.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Media Asset Management, MAM, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Media Asset ManagementMAMRate LimitingQuotas

Limits

Sustained Request Rate application
requests
~50 requests per second sustained
Per set of App-ID / Auth-Token application credentials.
Burst Window application
requests
~1000 requests per any 20-second window
Short-window burst allowance measured across a rolling 20 seconds.
Consumable Credits account
credits
per plan
Storage, egress, AI, and services are metered by plan credit allowances, not by request rate.

Policies

Rate Limit Headers
Responses include a RateLimit-Remaining header indicating how many requests remain in the current window.
Backoff Strategy
On a 429 response, back off with exponential delay and jitter before retrying.
Pagination
Use page and per_page parameters and follow returned page metadata rather than issuing large unbounded list requests.

Sources