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

expose rate limits #1376

Open
guiguilechat opened this issue May 29, 2024 · 3 comments
Open

expose rate limits #1376

guiguilechat opened this issue May 29, 2024 · 3 comments

Comments

@guiguilechat
Copy link

guiguilechat commented May 29, 2024

Context

Several people have been banned for the reason of exceeding expected usage.
If such an usage is not provided, it can't be expected. And by contra position, if it is expected, it must be provided.

AFAIK

Feature

new path : GET:/status/rates
description : provide requested dynamic maximum rates for paths, with a per-second and per-hour value. ESI users are expected to abide those values.
provide : array[pathrate]
with pathrate : path(string), persecond(float), perhour(float)
200 example :

[
 {
  "path":"get_characters_character_id_mail",
  "persecond":2.5,
  "perhour":7200
 }
]

expires : this path is cached for 5 minutes (300s)

@GoldenGnu
Copy link
Member

I would suggest making a PR to the documentation with the information: https://github.com/esi/esi-docs

At least that would have a chance of improving the issue.

I think the likelihood of a new endpoint being added is currently zero.

@guiguilechat
Copy link
Author

guiguilechat commented May 31, 2024

I don't disagree with your estimation of an infinite ETA.

I don't have that information though. CCP is the one who has it.

This ticket exists mostly as a trace of the issue. When new people come and ask about rates, we can redirect: them to it.

@guiguilechat
Copy link
Author

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

No branches or pull requests

3 participants