Retrieves the full details of multiple Tripadvisor Locations in a single request.
This is the batch (multi-GET) counterpart to the single Location Details endpoint; supply a set of Location IDs and receive the corresponding Locations. IDs that you are not licensed to access, or that do not exist, are omitted from the response rather than causing the whole request to fail.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Multiple Locations Details requests
A Multiple Locations Details request takes a set of Tripadvisor Location IDs and returns the full details of each, in a single call. It is the batch counterpart to Location Details.
Pass the IDs as a comma-separated list in the id parameter. The parameter is id, singular; there is no ids parameter.
A request is an HTTP GET to a URL in the form:
https://terra.tripadvisor.com/api/locationsMultiple Locations Details responses
The response is an object containing a data array of Location objects. The envelope is present even when a single ID is requested, which differs from Location Details, where the Location is returned directly.
Each Location carries the same fields as Location Details. Fields with no data are omitted rather than returned as null or {}.
IDs that do not exist, or that you are not licensed to access, are omitted from data rather than causing the request to fail. The array can therefore be shorter than the list of IDs requested. Compare data[].id against the requested IDs to detect omissions.
Billing
This endpoint is billed per Location returned. A request for three IDs that all resolve is billed as three entities; omitted IDs are not billed. Most other endpoints are billed once per call. See Usage-based Pricing.
Examples
Retrieve three Locations
curl "https://terra.tripadvisor.com/api/locations?version=1&id=187147,188151,190420" \
-H "X-API-Key: API_KEY"The response is in the form:
{
"data": [
{ "id": 187147, "names": [], "addresses": [] },
{ "id": 188151, "names": [], "addresses": [] }
]
}Only two of the three requested IDs resolved. The third was either not found or not licensed.
Retrieve Locations in two locales
locale is repeatable. Translated fields return one entry per resolved locale; enum labels such as category and award names resolve using the first locale only.
curl "https://terra.tripadvisor.com/api/locations?version=1&id=187147,188151&locale=es-MX&locale=fr-FR" \
-H "X-API-Key: API_KEY"Related
- Location Details — a single Location, and the full field reference
- Multiple Geos Details — the same pattern for destinations
- Supported Locales — locale codes and the fallback chain