Geocoding · head-to-head

API Découpage Administratif (API Geo) vs Nominatim

API Découpage Administratif (API Geo)

Etalab's Découpage Administratif API looks up and cross-references France's administrative hierarchy — communes, EPCIs, départements, and régions — by name, postcode, SIREN, or geographic coordinates, with no API key required. The stored api.gouv.fr/api/geoapi.html link had gone stale, 301-redirecting to a generic data.gouv.fr listing page instead of the live docs; the real service and interactive documentation are hosted at geo.api.gouv.fr. A live Origin-header probe against the real /communes endpoint confirms open CORS, reflecting back whatever Origin is sent.

Nominatim

Nominatim provides worldwide forward and reverse geocoding built entirely on OpenStreetMap data, needing no API key — only a descriptive User-Agent or Referer header identifying the calling application (the policy states a stock HTTP-library User-Agent will not do). The public instance at nominatim.openstreetmap.org mainly exists to power the search bar on openstreetmap.org and runs on donated servers with very limited capacity: its usage policy caps requests at an absolute maximum of 1 per second, forbids autocomplete-style querying outright, and requires results to be cached on the caller's side. Bulk geocoding is restricted rather than banned — a smaller one-time task is permissible on a single thread and a single machine, with distributed scripts disallowed and anything running longer than a day capped at 4 requests per minute. The policy points larger users first at commercial third-party providers, and the largest at running their own Nominatim instance.

API Découpage Administratif (API Geo)Nominatim
AuthenticationNoneNone
Pricingfreefree
FormatsJSON, GeoJSONJSON, XML, GeoJSON
CORSyesyes
HTTPSYesYes

Nominatim supports 3 response formats, while API Découpage Administratif (API Geo) offers fewer — pick Nominatim for more integration flexibility.

More comparisons