Skip to content
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

API rate limits #56

Open
quantnik opened this issue Aug 24, 2021 · 3 comments
Open

API rate limits #56

quantnik opened this issue Aug 24, 2021 · 3 comments

Comments

@quantnik
Copy link

Hi, I was told by Gateio support to direct my query here.

The documentation regarding rate limits is unfortunately not very clear.
All it says is:

"
Spot:

300 read operations per IP per second

Futures:

200 requests/second each user for private operations
"

Questions:

  1. So for SPOT, for reads (only) it is 300, per second, per IP. There is no limit per user, or per sub-account? i.e. if I had 100 IPs, I can read 30000 per second?

  2. For SPOT, there is no limit whatsoever for writes?

  3. For SPOT, it does not matter the difference between private/public endpoints? Both are limited as per above?

  4. For FUTURES, private endpoints: 200 per second, regardless of read/write. This is across ALL sub-accounts? Or per sub-account?

  5. For FUTURES, public endpoints there is no limit?

  6. Does using a different API key make any difference to the above?

Thank you.

@revilwang
Copy link
Collaborator

Sorry for late reply.

We're in the way of redesign our new API rate limiting strategy. Current detailed rate limiting rules can be found here. If the link does not cover some questions you mentioned. You're welcomed to post more comments here.

@quantnik
Copy link
Author

Thank @revilwang , really helpful.

  1. I take it by "API key" effectively means by sub-account on the spot side?
  2. are there any plan to similarly make the futures side based on sub-accounts?

Thanks again.

@revilwang
Copy link
Collaborator

  1. For spot side, every API key has its own rate limits. So even if one user has multiple API keys, they don't share the limits. For sub accounts, you have to create their standalone API keys, which means they also have their own rate limits.
  2. Futures's rate limits are based on user ID. Sub accounts have different user ID with main account, so they don't share limits. But all API keys of one user shares his/her own limits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants