Skip to content

Rate limits clarification #5585

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.

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
Oct 25, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion src/connections/rate-limits.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Events ingested by Segment have a limit of **10,000** properties per individual

## Inbound data ingestion API rate limit

If any sources send more than 20,000 events per second without prior arrangement, Segment reserves the right to queue any additional events and process those at a rate that doesn't exceed this limit.
If any sources send more than 20,000 events per second in a workspace without prior arrangement, Segment reserves the right to queue any additional events and process those at a rate that doesn't exceed this limit. To request a higher limit, contact [Segment](mailto:friends@segment.com).

> warning "Engage rate limit"
> Engage has a limit of 1,000 events per second for inbound data. Visit the [Engage Default Limits documentation](/docs/engage/product-limits/) to learn more.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,9 @@ Segment welcomes feedback on API responses and error messages. [Reach out to sup

## Rate limits

Segment recommends you to not exceed 20,000 requests per second with the HTTP API. For [`batch` requests](#batch), there's a limit of 500 KB per request.
For each workspace, Segment recommends you to not exceed 20,000 requests per second with the HTTP API. If you exceed this, Segment reserves the right to queue any additional events and process those at a rate that doesn't exceed the limit. To request a higher limit, contact [Segment](mailto:friends@segment.com).

For [`batch` requests](#batch), there's a limit of 500 KB per request.

> warning "Engage rate limit"
> Engage has a limit of 1,000 events per second for inbound data. Visit the [Engage Default Limits documentation](/docs/engage/product-limits/) to learn more.
Expand Down