Developer documentation
An address in.
Coordinates out.
Geocode addresses, suggest places as people type, and find what’s around a point. Start with one JSON request. No special SDK required.
This is the managed API for OpenGeocoding, the open-source geocoding engine we build and maintain. We host the engine and provide API key authentication, usage tracking and account management. The engine is open source; this hosted service is a separate commercial offering.
Prefer to run the engine yourself? See the self-hosting instructions on GitHub. The endpoints and authentication below describe the managed API, not the engine’s native interface.
Your first request
Up and running in a minute
- 01 Create a key in the dashboard.
- 02 Send a POST with your key and a JSON body.
- 03 Read coordinates and structured address fields.
curl 'https://api.opengeocoding.com/v1/search' \
-H 'x-api-key: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"addressString":"Copenhagen"}' The API domain is a placeholder until launch. Replace it with your deployed edge URL. Never expose a secret API key in browser code.
Explore the API
5 endpointsSearch
Turn an address into coordinates.
POST/v1/search
Autocomplete
Suggest places as someone types.
POST/v1/autocomplete
Retrieve suggestion
Get coordinates for a selected suggestion.
POST/v1/retrieve
Reverse geocoding
Find the addresses nearest a point.
POST/v1/reverse
List regions
List indexed countries and regions.
POST/v1/regions
Resolve regions
Find the administrative regions at a point.
POST/v1/resolve-region
Using gRPC?
The same six methods, keys and credits. Read the transport guide and use the pinned protobuf contract.
Autocomplete and regions are free of credit charges. Other successful operations spend one credit. Understand credits and limits →
Show the required data credits wherever you display results. Data attribution →