Repository navigation
docs: add the 402 row and correct the 403 and 429 explanations - #9
Merged
Merged
Conversation
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
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.
docs/troubleshooting.md: add a 402 row (expired paid subscription) and describe 403 as an IP allow-list rejection instead of a disabled key or blocked origin.docs/configuration.md: the API has no per-plan rate ceiling, sorate_limitonly paces the sync and a 429 means the credits are used up.The source of truth is the API status table on https://ipgeolocation.io/documentation/ip-location-api.html: 402 = paid subscription expired, 403 = the key has an IP allow-list and the caller IP is not on it (a disabled key or unregistered origin is 401), 429 = no credits left (the API has no per-second rate limits).