Whether a token is distributed via Developer Portal, OAuth grant, or the Accounts backend that serves Frame.io's own applications, all API calls to Frame.io are rate limited.
Rate limits are applied per token, are depleted and refilled progressively, and are reflected in the header responses to all calls made to the Frame.io API. Every resource path is configured with its own limits, which range from as low as 10 requests/minute, to as high as 100 requests/second.
Requests that exceed the rate limit for a particular resource will receive a
429 HTTP error in response.
The Frame.io API uses a leaky bucket strategy of progressive rate limiting, in which limits refresh gradually during their allotted time window. In other words, there is not a concept of any hard cutoff after which limits refresh for a particular resource (i.e. "fixed" and "sliding window" enforcement strategies). Rather, remaining limits are constantly refreshing at a pace relative to a resource's limit and time window.
Our recommended strategy for managing rate limits is usually referred to as "exponential backoff." In short:
- When receiving a
429, pause for a period (normally one second)
- If another
429is received, exponentially increase the wait period until normal function resumes
Responses to API requests will always include the following three headers:
|The rate limit for this resource path, measured in requests.|
|The number of requests remaining in the current time window.|
|The time window for this resource path's limits, measured in milliseconds (ms).|
The following example is from the response to
GET v2/assets/:id/children, to fetch the child assets of a Project root, folder, or Version Stack. The limit for that path is 40 requests per 60,000 ms (one minute), and there are 39 requests remaining after one has been made.
x-ratelimit-limit →40 x-ratelimit-remaining →39 x-ratelimit-window →60000
Rate limits vary greatly across resource paths in the Frame.io API. Below are some select details, expressed for readability as resource and action (e.g. "Assets -- Update" instead of
As a general rule, resource paths that create new data are limited at or below 100 calls per minute, and resource paths that fetch lists of assets are limited to 200 calls per minute.
|Resource||Action||Limit (requests)||Limit window (ms)|