OpenGeocoder API
Forward geocoding, reverse geocoding, place search and the 2012 archive as plain JSON over HTTPS. No API key and no sign-up. Built for prototypes, teaching and low-volume apps.
Quick start
curl "https://opengeocoder.net/api/v1/geocode?q=Utrecht&limit=1"
Every response is JSON with CORS enabled (Access-Control-Allow-Origin: *), so you can call it directly from a web page.
| Endpoint | What it does |
|---|---|
GET /api/v1/geocode | Address or place → up to 10 candidates with point, bbox, type and address |
GET /api/v1/search | Place search for disambiguation, plus matching 2012 archive records |
GET /api/v1/reverse | Coordinates → nearest address at a chosen level of detail |
GET /api/v1/archive | Substring search of the 2012 public-domain archive |
GET /api/0.1/search | The original 2012 endpoint, preserved |
GET /api/0.1/dump | The full 2012 dataset |
What it is — and isn't
- Fair use, not unlimited. About 30 requests per minute per client network. Across all users, uncached lookups are queued so we never exceed one request per second to OpenStreetMap's public Nominatim service, as its usage policy requires.
- No bulk geocoding. Don't loop over a spreadsheet. For thousands of addresses, self-host Nominatim or use a commercial provider. Our guide to geocoding addresses explains the options.
- No SLA. If the upstream service is unavailable, you get an explicit error. You never get a made-up result.
- Attribution required. Live results are OpenStreetMap data under the ODbL. Show “© OpenStreetMap contributors” wherever you display them. Archive results are public domain.
Next: full documentation with every parameter and response field, integration examples for JavaScript, Python and Leaflet, and a tutorial on using a geocoding API well.