With the TravelTime Geocoding API you can:
- Convert addresses, postcodes, zip codes, place names and venues into latitude and longitude
- Reverse geocode coordinates into full structured addresses
- Power address autocomplete in search boxes
- Filter results by country or bounding box, and return them in the user’s language
- Geocode without using your wider API usage limits
What the TravelTime Geocoding API returns
The TravelTime Geocoding API returns GeoJSON features for each match: coordinates, a full address label, structured address components (house number, street, postcode, city, region, country) and a confidence score from 0 to 1. Forward search matches a text query to locations. Reverse geocoding matches a coordinate to the nearest address.
Try TravelTime Geocoding API
API lite demo
Disabled3 results
What can the TravelTime Geocoding API do?
Forward geocoding
Reverse geocoding
Address autocomplete
Geocoding API at a glance
Quick overview of TravelTime Geocoding API specifications.
| Endpoints | Geocoding search (forward), reverse geocoding |
|---|---|
| Input | Address, postcode or venue (forward); latitude and longitude (reverse) |
| Output format | GeoJSON FeatureCollection |
| Returned fields | Coordinates, full address label, house number, street, postcode, neighbourhood, city, county, region, country, ISO country code, confidence score |
| Results per query | 1 to 50 |
| Languages | Any available language via BCP 47, with English as the fallback |
| Usage limits | Geocoding requests are never counted towards your hits per minute |
| Coverage | Global |
Scalable, repeatable and storable
Geocode without limits
Consistent, structured results
Store results in your platform
Geocode then calculate travel times
Address to isochrone
Address to commute times
Label results with addresses
Geocoding in GIS and no-code tools
Pricing
How we price the TravelTime APIs
Geocoding and Reverse Geocoding are included with your TravelTime licence and never counted towards your usage limits.
Chat to our teamGeocoding API FAQs
A geocoding API converts an address, postcode or place name into geographic coordinates. Reverse geocoding does the opposite, converting coordinates into a readable address.
GeoJSON features with coordinates, a full address label, structured address components such as street, postcode, city and country, and a confidence score between 0 and 1.
No. Geocoding requests are never counted towards your hits-per-minute limit.
Yes. Return up to 50 suggestions per query, filtered by country or bounding box. Throttle requests on the client side for fast typers, and handle responses arriving out of order.
Yes. Restrict results to one or more countries using ISO 3166-1 codes, or to a bounding box.
Yes. Request results in any available language using a BCP 47 language tag. Where a language isn't available, results fall back to English.
Reverse geocoding works for points on land. Points far out at sea return an error.