Document HTTP status codes for legacy web services#1683
Conversation
The minFraud Legacy, proxy detection, and GeoIP Legacy web services now return meaningful HTTP status codes for authentication and funds errors: 401 for missing or invalid license keys and 402 when the account is out of queries. IP-not-found and warning conditions continue to return 200, and the response body error codes are unchanged. Documenting these status codes lets customers act on them at the HTTP layer (for example, with edge or CDN rules) without parsing the response body.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Deploying dev-site with
|
| Latest commit: |
16b6892
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://93cf6dbd.dev-site-4ua.pages.dev |
| Branch Preview URL: | https://greg-stf-67-legacy-web-servi.dev-site-4ua.pages.dev |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds documentation about HTTP status codes to the legacy GeoIP, minFraud, and Proxy Detection web services documentation pages. The new sections explain how HTTP status codes (such as 200, 400, 401, 402, and 5xx) are used to indicate specific error conditions. Feedback on the changes suggests fixing an inline code block in legacy.md that is split across lines, which could cause rendering issues in some Markdown parsers.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| `INVALID_LICENSE_KEY` error code; only the HTTP status differs (`402 Payment | ||
| Required` rather than `401 Unauthorized`). The `IP_NOT_FOUND` case continues to |
There was a problem hiding this comment.
The inline code block 402 Payment Required is split across lines 90 and 91. This can cause rendering issues or display an unexpected newline/space inside the code block in some Markdown parsers. Keeping the entire inline code block on a single line ensures correct rendering and better readability.
| `INVALID_LICENSE_KEY` error code; only the HTTP status differs (`402 Payment | |
| Required` rather than `401 Unauthorized`). The `IP_NOT_FOUND` case continues to | |
| `INVALID_LICENSE_KEY` error code; only the HTTP status differs | |
| (`402 Payment Required` rather than `401 Unauthorized`). The `IP_NOT_FOUND` case continues to |
References
- Technical identifiers such as method names, properties, and language keywords must be formatted as code using backticks when referenced in prose. (link)
1 participant
Draft — do not merge until the service change has shipped to production.
This is the public-docs companion to the MaxMind internal service change tracked
as STF-67 (internal PR #44529). It documents a customer-facing behavior change;
it should be merged only once that change is live in production.
Customer-facing behavior change
The legacy web services now return meaningful HTTP status codes for
authentication and funds errors. Previously these conditions were reported only
as an error-code string in the response body (with a
200 OKstatus). Now:failure ->
401 Unauthorized; account out of queries ->402 Payment Required.401 Unauthorized; accountout of queries ->
402 Payment Required(newly added).200 OK(not404), to avoidbreaking existing integrations. Other warnings also continue to return
200.for GeoIP Legacy an out-of-queries condition still returns the body error code
INVALID_LICENSE_KEY; only the HTTP status line changed (now402).This lets customers detect these conditions at the HTTP layer (for example, with
an edge or CDN rule) without parsing the response body.
Files changed
content/geoip/docs/web-services/legacy.mdcontent/minfraud/minfraud-legacy.mdcontent/minfraud/proxy-detection.mdThe modern GeoIP2/minFraud REST documentation (
responses.md) already documents401/402and is not affected by this change.Opened by Claude, on Greg's behalf.
Generated with Claude Code