Skip to content

update rate limits #314

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
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
9 changes: 2 additions & 7 deletions faq.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -85,15 +85,10 @@ See [resource limits](/concepts/resource-limits).
</Accordion>
<Accordion title="Do you have any rate limits in place in your public API?">

Our public API currently limits users to a maximum of 60 RPS (Requests Per Second). Specific headers are returned to indicate current quota:

- `ratelimit-limit`: indicates the total quota (60)
- `ratelimit-remaining`: indicates the current quota
- `x-rate-limit-request-forwarded-for` and `x-rate-limit-request-remote-addr`: echo back your remote IP and forwarded-for IP for debugging purposes

Our public API currently limits users to a maximum of 3600 RPM (Requests Per Minute).
When rate limits are exceeded, an error with HTTP 429 is returned with the following message: `Too many requests. Please wait and try again in a few seconds`.

This limit is on a **per IP address** basis: if you have multiple servers making requests to the turnkey API under a different IP address, each server is subject to the 60 RPS limit individually.
This limit is on a **per Organization ID** basis, every parent organization and sub-organization will get this limit individually.

Please get in touch with us ([[email protected]](mailto:[email protected])) if you need this limit adjusted for your use-case.

Expand Down