Skip to content

Search API

by tomtom.com

API keyHTTPSGeocoding
Open documentation ↗

Overview

Search API is a RESTful API that allows developers to run a single line fuzzy search for addresses and POIs. Search API returns the latitude/longitude of a specific address, cross street, geographic feature, or point of interest (POI).

Search is a geocoding API from tomtom.com. Requests are authenticated with an API key. It is served over HTTPS. Its OpenAPI description documents 19 endpoints.

At a glance

Authentication
API key
HTTPS
Yes
CORS
Unknown
Category
Geocoding
Base URL
https://api.tomtom.com
Version
1.0.0
Endpoints
19
Spec updated
2020-03-22

Make a first request

Replace the placeholders; the documentation says exactly where credentials go.

cURL
curl -X GET "https://api.tomtom.com/search/VERSIONNUMBER/additionalData.EXT" \
  -H "Accept: application/json" \
  -H "X-API-Key: YOUR_API_KEY"
JavaScript
const response = await fetch("https://api.tomtom.com/search/VERSIONNUMBER/additionalData.EXT", {
  method: "GET",
  headers: {
    "Accept": "application/json",
    "X-API-Key": "YOUR_API_KEY",
  },
});
const data = await response.json();
console.log(data);
Python
import requests

response = requests.request(
    "GET",
    "https://api.tomtom.com/search/VERSIONNUMBER/additionalData.EXT",
    headers={
    "Accept": "application/json",
    "X-API-Key": "YOUR_API_KEY",
    },
    timeout=30,
)
print(response.json())

Endpoints

MethodPathWhat it does
GET/search/{versionNumber}/additionalData.{ext}Additional Data
GET/search/{versionNumber}/cS/{category}.{ext}deprecatedLow Bandwith Category Search
GET/search/{versionNumber}/categorySearch/{query}.{ext}Category Search
GET/search/{versionNumber}/geocode/{query}.{ext}Geocode
GET/search/{versionNumber}/geometryFilter.{ext}Geometry Filter
POST/search/{versionNumber}/geometryFilter.{ext}Geometry Filter
GET/search/{versionNumber}/geometrySearch/{query}.{ext}Geometry Search
POST/search/{versionNumber}/geometrySearch/{query}.{ext}Geometry Search
GET/search/{versionNumber}/nearbySearch/.{ext}Nearby Search
GET/search/{versionNumber}/poiSearch/{query}.{ext}Points of Interest Search
GET/search/{versionNumber}/reverseGeocode/crossStreet/{position}.{ext}Cross Street lookup
GET/search/{versionNumber}/reverseGeocode/{position}.{ext}Reverse Geocode
GET/search/{versionNumber}/routedFilter/{position}/{heading}.{ext}deprecatedRouted Filter
POST/search/{versionNumber}/routedFilter/{position}/{heading}.{ext}deprecatedRouted Filter
GET/search/{versionNumber}/routedSearch/{query}/{position}/{heading}.{ext}deprecatedRouted Search
GET/search/{versionNumber}/s/{query}.{ext}deprecatedLow bandwith Search
GET/search/{versionNumber}/search/{query}.{ext}Fuzzy Search
POST/search/{versionNumber}/searchAlongRoute/{query}.{ext}Along Route Search
GET/search/{versionNumber}/structuredGeocode.{ext}Structured Geocode

Questions

Does the Search API need an API key?

Yes. The Search API uses API key authentication; the documentation explains how to get credentials.

Does the Search API support HTTPS?

Yes, the Search API is served over HTTPS.

How many endpoints does the Search API have?

Its OpenAPI description lists 19 endpoints in version 1.0.0. All of them are shown on this page.

What are alternatives to the Search API?

Other Geocoding APIs include Bing Maps, ip-api, OpenStreetMap, GeographQL, IP Address Details.

Compare alternatives →

Listed from APIs.guru (CC0).