How to Find a TripAdvisor Location ID (3 Ways, With Examples)

Every property on TripAdvisor has a unique numeric location ID.
It's how TripAdvisor's systems, and any API working with TripAdvisor data, identify a specific hotel, restaurant, or attraction.
You need it for review extraction, rating trackers, and data pipelines; if you searched for a TripAdvisor hotel ID finder, this page is that, in three methods.
Fastest first.

Method 1: Read the Location ID From the URL

The fastest way to get the location ID of a TripAdvisor property: it's printed in the URL of every listing.
Take a real example:

https://www.tripadvisor.com/Hotel_Review-g187147-d197514-Reviews-Le_Meurice-Paris_Ile_de_France.html

Step by step:
1. Open the property page on TripAdvisor.
2. Look at the URL in the address bar.
3. Copy the number between -d and the next hyphen. That's the location ID.
This works for anything with a TripAdvisor listing: hotels, restaurants, attractions, even tours.

Method 2: Look It Up via API

When you know the hotel name but don't have the URL, or you're working programmatically, a lookup API beats opening a browser.
StayAPI's meta match endpoint takes a hotel name and a platform, and returns the property's canonical URL on that platform:

curl -G "https://api.stayapi.com/v1/meta/match" \
  -H "x-api-key: YOUR_API_KEY" \
  --data-urlencode "name=Le Meurice Paris" \
  -d "platform=tripadvisor"

{
  "success": true,
  "query": { "name": "Le Meurice Paris", "platform": "tripadvisor" },
  "match": {
    "title": "LE MEURICE - Hotel Reviews (Paris, France)",
    "url": "https://www.tripadvisor.com/Hotel_Review-g187147-d197514-Reviews-Le_Meurice-Paris_Ile_de_France.html"
  }
}

The location ID is the -d segment of match.url: 197514, one regex or split() away.
The same endpoint resolves the property on Booking.com, Expedia, Agoda, and Trip.com by switching the platform parameter, which is how you map one hotel across platforms.
The first 50 requests are free, enough to look up IDs for a small portfolio without paying anything.
For a one-off lookup with no code at all, the free TripAdvisor search tool does the same job in the browser.

Method 3: Bulk Lookup for a TripAdvisor Location IDs List

The scenario: you have 50-500 hotel names in a spreadsheet and need the TripAdvisor location ID for each.
Manual URL lookup stops scaling at around 10 properties.
The workflow, no code required:
1. Put your hotel names in a Google Sheet, one per row.
2. Build an N8N or Make.com flow: read each row, send the name to the meta match endpoint with platform=tripadvisor.
3. Extract the ID from the returned URL with one regex step: -d(\d+).
4. Write the ID back to the row.
Each lookup is one API request, so a 300-hotel list is 300 requests.
For very large lists (1,000+), batch the run overnight rather than firing everything at once.

What You Can Do With a Location ID

Once you have the ID, the real work starts:

The most common next step is pulling reviews programmatically: the location ID is the input for TripAdvisor review extraction.
Cross-referencing works too: map the TripAdvisor ID to the same property's Booking.com and Expedia listings for one combined report.

FAQ

What is a TripAdvisor location ID?

A unique numeric identifier TripAdvisor assigns to every listed property: hotels, restaurants, and attractions.
It appears after -d in the property's URL.

Is the location ID the same as the geo ID?

No.
The geo ID (after -g) identifies the destination, meaning the city or region.
The location ID (after -d) identifies the specific property.

Can I look up a property from its location ID (reverse lookup)?

Yes.
A hotel-details lookup by location ID returns the property's name and details; the free TripAdvisor hotel details tool does this in the browser.

Do location IDs ever change?

Rarely.
IDs are stable unless a listing is removed and re-created, for example after a major rebrand or ownership change.

How do I get location IDs for hundreds of hotels at once?

Feed the hotel names through a lookup API in a loop, as in Method 3.
A spreadsheet plus an N8N flow handles it without code, and the first 50 lookups are free with StayAPI.