Geocode an address, partial address or just the name of a place.
Address geocoding is the process of taking a string and attempting to match this with possible real world locations.
This is the opposite process of reverse geocoding.
Once a location is found you can then retrieve the geographic coordinates as latitude and longitude.
If more than one location is found for a given string then results are ordered by most relevant to the original search address and with the highest geographic accuracy.
Use this API to:
Display geocoded locations on a map component
Validate postal addresses
Search for postal codes
Extract address components like city, state and country details
Implement auto-complete for address inputs
Fuzzy search for the nearest locations from partial or misspelled addresses
This API accepts both structured and unstructured addresses.
To geocode a structured address set the fields: 'house-number', 'street', 'city', etc.
To geocode an unstructured address just set the 'address' field.
If the 'address' field is set it always takes precedence.
The full address, partial address or name of a place to try and locate. Comma separated address components are preferred.
The house/building number to locate
The street/road name to locate
The city/town name to locate
The county/region name to locate
The state name to locate
The postal code to locate
Limit result to this country (the default is no country bias)
The language to display results in, available languages are:
de, en, es, fr, it, pt, ru, zh
If no matches are found for the given address, start performing a recursive fuzzy search until a geolocation is found. This option is recommended for processing user input or implementing auto-complete. We use a combination of approximate string matching and data cleansing to find possible location matches
The number of possible matching locations found
Array of matching location objects:
The location latitude
The location longitude
The complete address using comma-separated values
The components which make up the address such as road, city, state, etc
The city of the location
The state of the location
The ISO 3166-2 region code for the location
The country of the location
The ISO 2-letter country code of the location
The ISO 3-letter country code of the location
ISO 4217 currency code associated with the country
The postal code for the location
The formatted address using local standards suitable for printing on an envelope
The detected location type ordered roughly from most to least precise, possible values are:
address - indicates a precise street address
street - accurate to the street level but may not point to the exact location of the house/building number
city - accurate to the city level, this includes villages, towns, suburbs, etc
postal-code - indicates a postal code area (no house or street information present)
railway - location is part of a rail network such as a station or railway track
natural - indicates a natural feature, for example a mountain peak or a waterway
island - location is an island or archipelago
administrative - indicates an administrative boundary such as a country, state or province
Array of strings containing any location tags associated with the address. Tags are additional pieces of metadata about a specific location, there are thousands of different tags. Some examples of tags: shop, office, cafe, bank, pub
Map containing timezone details for the location:
The time zone ID as per the IANA time zone database (tzdata)
The full time zone name
The time zone abbreviation
The current date at the time zone (ISO 8601 format 'YYYY-MM-DD')
The current time at the time zone (ISO 8601 format 'hh:mm:ss.sss')
The UTC offset for the time zone (ISO 8601 format '±hh:mm')
Average RTT for requests within the same data center/region
Maximum inbound request rate. Exceeding this will result in request throttling
Maximum concurrent/simultaneous requests. Exceeding this will result in error code 06 [TOO MANY CONNECTIONS]