Add release notes for legacy web service HTTP status codes

Announce that the GeoIP Legacy, minFraud Legacy, and Proxy Detection web
services now return meaningful HTTP status codes (400/401/402/403) for
error conditions, while IP-not-found and the response body are unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: oschwald

content/geoip/release-notes/2026.md

@@ -9,6 +9,26 @@ outputs: ['html', 'markdown']
 [Sign up to be notified](https://comms.maxmind.com/geoip-rss-release-notes)
 whenever a new GeoIP release note is posted. {{</ alert >}}
 
+{{< release-note date="2026-06-30" title="GeoIP Legacy web service now returns HTTP status codes for errors" >}}
+
+The GeoIP Legacy web service now returns meaningful HTTP status codes for error
+conditions, so you can detect them at the HTTP layer (for example, with an edge
+or CDN rule) without parsing the response body:
+
+- `400 Bad Request` for a malformed request
+- `401 Unauthorized` for a missing or invalid license key
+- `402 Payment Required` when your account is out of queries
+- `403 Forbidden` when your account does not have permission to use the service
+- `5xx` for a server error
+
+The response body and its error-code strings are unchanged. The `IP_NOT_FOUND`
+case continues to return a `200 OK` status to avoid breaking existing
+integrations.
+
+[See the GeoIP Legacy documentation for details.](/geoip/docs/web-services/legacy/#http-status-codes)
+
+{{</ release-note >}}
+
 {{< release-note date="2026-06-11" title="City field blanked in selected cities/provinces and countries" >}}
 
 Effective Monday, June 15, 2026, we will be blanking out the city field more

content/minfraud/release-notes/2026.md

@@ -9,6 +9,28 @@ outputs: ['html', 'markdown']
 [Sign up to be notified](https://comms.maxmind.com/minfraud-rss-release-notes)
 whenever a new minFraud release note is posted. {{</ alert >}}
 
+{{< release-note date="2026-06-30" title="minFraud Legacy and Proxy Detection web services now return HTTP status codes for errors" >}}
+
+The minFraud Legacy and Proxy Detection web services now return meaningful HTTP
+status codes for error conditions, so you can detect them at the HTTP layer (for
+example, with an edge or CDN rule) without parsing the response body:
+
+- `400 Bad Request` for a malformed request
+- `401 Unauthorized` for a missing or invalid license key
+- `402 Payment Required` when your account is out of queries
+- `403 Forbidden` when your account does not have permission to use the service
+- `5xx` for a server error
+
+The response body and its error-code strings are unchanged. Warning conditions,
+including `IP_NOT_FOUND`, continue to return a `200 OK` status to avoid breaking
+existing integrations.
+
+[See the minFraud Legacy](/minfraud/minfraud-legacy/#http-status-codes) and
+[Proxy Detection](/minfraud/proxy-detection/#http-status-codes) documentation
+for details.
+
+{{</ release-note >}}
+
 {{< release-note date="2026-05-13" title="Improved readability of the risk reasons module within Transactions Details screen">}}
 
 Based on user feedback, we have updated the risk reasons module within the