The Frame.io API may return the following common errors:
|Unauthorized -- Invalid API token. Check to make sure you're using Bearer Token authentication, and passing your token via the Authorization header.|
|Usage exceeded -- You have gone over your Frame.io plan limits.|
|Forbidden -- You do not have access to that resource. Returned for both user access and token scope.|
|Not Found -- Resource not found.||Resource has been moved or deleted.|
|Invalid arguments -- One or more parameters supplied were invalid.|
|Rate Limited -- You have hit the rate limit for the API.|
|Server Error -- Our server doesn't know how to interpret your request.||Malformed request URL or body.|
When using a valid API token to perform common tasks, the most common errors are
A 403 error will usually indicate one of three scenarios:
- The token used in the request, and/or the User to which the token belongs, does not have sufficient access to the area of the Frame.io Account where the resource was requested.
- The token does not have sufficient Scopes for the resource requested. For example: calling
GET /comments/without the
- A network traffic problem is preventing the Frame.io API from processing the request. If you suspect your requests are being blocked by a network traffic problem, please contact Customer Support.
A 404 error will usually indicate a resource no longer exists -- it has been moved or deleted.
A 500 error usually indicates a malformed request URL or body.
The Frame.io API applies rate limits per token. The default limit for a token is 50 calls per second. Some methods have lower limits (e.g. POST
/assets/:id/children is rate limited to 5 assets per second).
All limits are subject to change, and when hit, will return a 429 HTTP error. We suggest using an exponential back-off approach to handling rate-limiting.
Check out our guide on rate-limits to learn more.