Searches the Location catalog by free-text name or address.
Use this endpoint to resolve a textual query (for example a business name or street address) into matching Tripadvisor Locations. This endpoint is not limited by a partner's allowlist or geofencing, but each result returns only the lightweight catalog projection of a Location.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Search Locations Catalog requests
A Search Locations Catalog request takes a free-text query and returns matching Locations from the whole Tripadvisor catalogue. Unlike Search Locations, it is not restricted by your allowlist or geofencing, and each result carries only a lightweight projection of a Location.
Use it to resolve names and addresses into Tripadvisor Location IDs, then pass those IDs to the Location endpoints.
A request is an HTTP GET to a URL in the form:
https://terra.tripadvisor.com/api/catalog/locations/searchSearch Locations Catalog responses
The response is a paged object. Each entry in data carries the Location ID, names, addresses, coordinates, descriptions, overall rating and Tripadvisor URLs. Photos, categories, opening hours and reviews are not included — retrieve those from Location Details once the ID is on your allowlist.
Pages are 1-based.
Search parameters
Identical to Search Locations: query (1 to 500 characters, required), search_type (NAME, ADDRESS, COMBINED), country_code (upper-case alpha-2), geo_name, postal_code and category (RESTAURANT, ATTRACTION, HOTEL).
Limits
size must not exceed 20 and defaults to 20. A larger value returns 400.
Note: a result here is not a licence. Finding a Location in the catalogue does not make it retrievable from Location Details — add the ID to your allowlist first, or the request returns 404.
Note: the catalogue endpoints count against the same lower search rate limit as the Location search endpoints. They are intended for configuration and admin workflows rather than end-user traffic. See API Access and Limits.
Note: the Catalog and Location read endpoints share a single permission. A key that can call one can call the other.
Examples
Resolve a hotel name to a Location ID
curl "https://terra.tripadvisor.com/api/catalog/locations/search?version=1&query=Hotel%20Lutetia&geo_name=Paris" \
-H "X-API-Key: API_KEY"Check whether an address exists in the catalogue
curl "https://terra.tripadvisor.com/api/catalog/locations/search?version=1&query=45%20Boulevard%20Raspail&search_type=ADDRESS&country_code=FR" \
-H "X-API-Key: API_KEY"Related
- Guide for Managing Allowed Locations — what to do with the IDs you resolve
- Search Locations — the allowlist-scoped equivalent, with full records
- Get Catalog Location — when the ID is already known