Skip to content

feat: increase rate limits #1836

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 27, 2025
Merged

feat: increase rate limits #1836

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bbb5cc5
feat: increase rate limits
tobice Aug 25, 2025
e364944
chore: CR feedback
tobice Aug 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions apify-api/openapi/openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -398,18 +398,18 @@ info:
### Per-resource rate limit
<span id="/introduction/rate-limiting/per-resource-rate-limit"></span>

The default per-resource rate limit is _30 requests per second per resource_, which in this context means a single Actor, a single Actor run, a single dataset, single key-value store etc.
The default per-resource rate limit is _60 requests per second per resource_, which in this context means a single Actor, a single Actor run, a single dataset, single key-value store etc.
The default rate limit is applied to every API endpoint except a few select ones, which have higher rate limits.
Each API endpoint returns its rate limit in `X-RateLimit-Limit` header.

These endpoints have a rate limit of _100 requests per second per resource_:
These endpoints have a rate limit of _200 requests per second per resource_:

* CRUD ([get](#/reference/key-value-stores/record/get-record),
[put](#/reference/key-value-stores/record/put-record),
[delete](#/reference/key-value-stores/record/delete-record))
operations on key-value store records

These endpoints have a rate limit of _200 requests per second per resource_:
These endpoints have a rate limit of _400 requests per second per resource_:
* [Run Actor](#/reference/actors/run-collection/run-actor)
* [Run Actor task asynchronously](#/reference/actor-tasks/runs-collection/run-task-asynchronously)
* [Run Actor task synchronously](#/reference/actor-tasks/runs-collection/run-task-synchronously)
Expand Down
4 changes: 2 additions & 2 deletions sources/platform/storage/dataset.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -450,8 +450,8 @@ See the [Storage overview](/platform/storage/usage#sharing-storages-between-runs

### Rate limiting

The rate limit for pushing data to a dataset through the [API](/api/v2/dataset-items-post) is capped at _200 requests per second_ for each dataset, a measure to prevent overloading Apify servers.
The rate limit for pushing data to a dataset through the [API](/api/v2/dataset-items-post) is capped at _400 requests per second_ for each dataset, a measure to prevent overloading Apify servers.

For all other dataset [API endpoints](/api/v2/storage-datasets) , the rate limit is _30 requests per second_ for each dataset.
For all other dataset [API endpoints](/api/v2/storage-datasets) , the rate limit is _60 requests per second_ for each dataset.

Check out the [API documentation](/api/v2#rate-limiting) for more information and guidance on actions to take if you exceed these rate limits.
4 changes: 2 additions & 2 deletions sources/platform/storage/request_queue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -627,8 +627,8 @@ CRUD ([add](/api/v2/request-queue-requests-post),
[get](/api/v2/request-queue-request-get),
[update](/api/v2/request-queue-request-put),
[delete](/api/v2/request-queue-request-delete))
operation requests are limited to _200 requests per second_ per request queue. This helps protect Apify servers from being overloaded.
operation requests are limited to _400 requests per second_ per request queue. This helps protect Apify servers from being overloaded.

All other request queue API [endpoints](/api/v2/storage-request-queues) are limited to _30 requests per second_ per request queue.
All other request queue API [endpoints](/api/v2/storage-request-queues) are limited to _60 requests per second_ per request queue.

Check out the [API documentation](/api/v2#rate-limiting) for more information and guidance on actions to take if you exceed these rate limits.
2 changes: 1 addition & 1 deletion sources/platform/storage/usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ Use this tool to estimate storage costs by plan and storage type.

## Rate limiting

All API endpoints limit their rate of requests to protect Apify servers from overloading. The default rate limit for storage objects is _30 requests per second_. However, there are exceptions limited to _200 requests per second_ per storage object, including:
All API endpoints limit their rate of requests to protect Apify servers from overloading. The default rate limit for storage objects is _60 requests per second_. However, there are exceptions limited to _400 requests per second_ per storage object, including:

* [Push items](/api/v2/dataset-items-post) to dataset.
* CRUD ([add](/api/v2/request-queue-requests-post),
Expand Down