Update rate-limiting documentation for clarity between error limit and bucket based limiting#268
Merged
Update rate-limiting documentation for clarity between error limit and bucket based limiting#268
Conversation
The actual token returned by The SSO endpoint and used by Applications, including the official API Explorer at https://developers.eveonline.com/api-explorer has this format.
Fix JWT token 'sub' claim format
Clarify that new rate limiting headers are mutually exclusive to Error Limit documentation.
…d bucket based limiting Update rate-limiting documentation for clarity
…d bucket based limiting Enhance ESI error limit explanation
Contributor
Author
|
Sorry for the ton of commits for just a few lines addition. GitHub GUI is confusing if you've mainly used the CLI. Please squash it if you merge it, thanks. |
ccp-pinky
approved these changes
Jan 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added information about when to expect error-limit headers and when not to. Before this addition it was unclear if an error on a bucket limited endpoint also counted towards the error limit or not.