Changelog

Product and API changes, newest first. Breaking changes to documented behaviour will always be introduced under a new version prefix (/v2, …). A fix that brings the API back in line with what this documentation already describes is not one of them: it ships on /v1 and is announced here. See the versioning policy.

2026-07​

• countrycodes on /v1/autocomplete now behaves like it does on /v1/geocode. fr designates no index of its own, so next to another code it is that other code that decides: gp,fr now returns exactly what gp returns (it used to query all six regions), fr,eu searches the continental index, and fr,de returns nothing, like de alone. This changes previously documented behaviour — the old reference stated that fr overrode any alias next to it — so check any stored countrycodes value that mixes fr with another code. fr on its own is unchanged: the whole covered area.
• Public OpenAPI specification published at /openapi.json — import it into Postman, Insomnia, or a client generator.
• Documentation overhaul: pricing tables, response schemas, quota header names, and all code examples verified against the live API; new FAQ, Geographic Coverage, and Licensing & Attribution pages.
• Playground fixes: map-matching and snap-to-road tabs now parse the real API response format.
• Security hardening: stricter CORS policy, Host-header validation, stronger password policy (12 characters minimum), and privacy-preserving (pseudonymized) server logs.
• Public status page at status.geocodeme.net with per-component health (API, geocoding, routing).

2026-06 and earlier​

• Launch of the developer dashboard: API key management, usage statistics, Stripe subscriptions (Free / Startup / Pro).
• Geocoding (/v1/geocode, /v1/reverse), map matching (/v1/match), and snap-to-road (/v1/nearest) endpoints with Redis caching, per-second rate limits, and monthly quotas.
• Interactive documentation Playground with live map.