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

Checking rate limits #13

Open
Oidaho opened this issue Feb 10, 2025 · 0 comments
Open

Checking rate limits #13

Oidaho opened this issue Feb 10, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@Oidaho
Copy link
Owner

Oidaho commented Feb 10, 2025

When you receive a response, you can view the headers and find out how many requests are left before the limit is reset.

The limit is reset once a minute.

The rate limit is implemented using the "point stack" method. In other words, each request has its own weight.
The maximum request weight is 2. Therefore, all requests should be considered as having a weight of 2.

As far as is currently known, each token has its own "point stack":

  • Application token: 400 points
  • User token: 200 points

However, this information is not accurate, and it is subject to verification.
Necessary to create a mechanism that can save or take into account the rate limits for API requests.

@Oidaho Oidaho added the enhancement New feature or request label Feb 10, 2025
@Oidaho Oidaho added this to the Stalcraft API interface milestone Feb 10, 2025
@Oidaho Oidaho self-assigned this Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant