Rate limits on API requests help maintain the API's health and stability. Every Linode API operation applies a rate limit on a per-user basis as determined by the OAuth token for authenticated requests, or the IP address for public operations.
Each rate limit consists of a total number of requests and a time window. For example, if an operation has a rate limit of 1600 requests per minute, then up to 1600 requests over a one minute window are permitted.
Subsequent requests over a rate limit return a 429 error. You need to wait for the rate limit window to reset before you can make additional requests.
Linode API rate limits
With the Linode API, these basic rate limits apply:
-
GET-based operations that return paginated data collections have a rate limit of 200 requests per minute, unless called out in Specific operation rate limits.
-
All other operations have a rate limit of 1600 requests per minute, unless called out in Specific operation rate limits.
Rate limiting may be applied at other levels, outside of the API. For example, rate limits can be applied at a load balancer.
Specific operation rate limits
These specific operations have their own unique rate limits.
| Operation | Limit |
|---|---|
| Administration/Support | |
| Accept a service transfer | Accepting service transfers has a dedicated rate limit of 2 requests per minute. |
| Open a support ticket | When opening support tickets you're limited to 2 requests per minute. |
| Images | |
| List images | Listing images has a dedicated rate limit of 20 requests per minute. |
| Linode instances | |
| Create a Linode | Creating Linodes has a dedicated rate limit of 20 requests per 15 seconds. |
These Linode statistics (/stats) operations have their own dedicated rate limits of 50 requests per minute. | |
| Linode StackScripts | |
| List StackScripts | Listing StackScripts has a dedicated rate limit of 60 requests per minute. |
| Monitor (Akamai Cloud Pulse) | |
| These Metrics sub-category GET operations have a rate limit of 100 requests per minute. | |
| Get an entity's metrics | This operation has a rate limit of 300 requests per minute per account, per service type. This limit is shared across all users on your account. For example, combined requests from all users on your account to this operation, targeting the dbaas service type can't exceed 300 over the span of one minute. |
| Object Storage | |
These operations have the following rate limits:
| |
| Reserved IPs | |
| Get a reserved IP address | The configured limit for retrieving reserved IP addresses is 5 requests per 15 seconds. |
| Volumes (Block Storage) | |
| Create a volume | Creating volumes has a dedicated rate limit of 100 requests per minute. |
Rate limit HTTP response headers
The API and CLI include the following HTTP response headers, which help you avoid hitting rate limits that might disrupt your applications:
-
X-RateLimit-Limit. The maximum number of permitted requests during the rate limit window for this operation. -
X-RateLimit-Remaining. The remaining number of permitted requests in the current rate limit window. -
X-RateLimit-Reset. The time when the current rate limit window rests in UTC epoch seconds. -
Retry-After. The remaining number of seconds until the current rate limit window resets.
Some or all of these headers may be available, based on the specific operation. For example, the
X-RateLimit-Resetheader isn't currently available with the Get an entity's metrics operation.
