[Home](/)[Blog](/blog)How to Find a TripAdvisor Location ID (3 Ways, With Examples)

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

 ![Denis Gramm](/blog_post_author.png)

By Denis Gramm· Jul 03, 2026 ·5 min read

I hope you enjoy reading this blog post. If you want our team to help you with hotel data integration, [click here](/book-demo).

Quick summary

Three ways to find a TripAdvisor location ID: from the URL in seconds, via an API lookup, or in bulk for a whole spreadsheet of hotels.

## Table of contents

- [Method 1: Read the Location ID From the URL](#method-1-read-the-location-id-from-the-url)
- [Method 2: Look It Up via API](#method-2-look-it-up-via-api)
- [Method 3: Bulk Lookup for a TripAdvisor Location IDs List](#method-3-bulk-lookup-for-a-tripadvisor-location-ids-list)
- [What You Can Do With a Location ID](#what-you-can-do-with-a-location-id)
- [FAQ](#faq)

![How to Find a TripAdvisor Location ID (3 Ways, With Examples) — StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6OTMsInB1ciI6ImJsb2JfaWQifX0=--519ead203feec7d980e78e05bdbbebbe19d11586/hero_a.png?disposition=inline)

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 | Best when | Time |
| --- | --- | --- |
| **1. Read the URL** | You have the property page open in a browser | 10 seconds |
| **2. API lookup** | You have a hotel name, not a URL, or you're doing it in code | 1 request |
| **3. Bulk lookup** | You have a spreadsheet of 50+ properties | One no-code flow |

## Method 1: Read the Location ID From the URL

![Method 1: Read the Location ID From the URL — StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6OTYsInB1ciI6ImJsb2JfaWQifX0=--95e5cac3136094a9e6318755955dd88f462a5ba8/method_1_read_the_location_id_from_the_url_b.png?disposition=inline)

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
```

| Segment | What it is | In this example |
| --- | --- | --- |
| `g187147` | Geo ID: the destination (city or region) | Paris |
| `d197514` | Location ID: the specific property | Le Meurice hotel |

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

![Method 2: Look It Up via API — StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6OTgsInB1ciI6ImJsb2JfaWQifX0=--b479f5ed4d80051ad6603d5b4d2ea2707b67efac/method_2_look_it_up_via_api_b.png?disposition=inline)

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](https://stayapi.com/docs/endpoints/meta-match) 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](https://stayapi.com/users/sign_up), 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](https://stayapi.com/free-tools/tripadvisor-search) does the same job in the browser.

## Method 3: Bulk Lookup for a TripAdvisor Location IDs List

![Method 3: Bulk Lookup for a TripAdvisor Location IDs List — StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6MTAwLCJwdXIiOiJibG9iX2lkIn19--a1947b3027f38d5e6458a6983aa99c9cb6ea5826/method_3_bulk_lookup_for_a_tripadvisor_location_ids_list_b.png?disposition=inline)

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:

| Use | Input | What you get |
| --- | --- | --- |
| **Review extraction** | Location ID | Full review text, ratings, dates, in JSON |
| **Rating tracker** | Location ID + a daily schedule | Score and review-count trends the TripAdvisor dashboard doesn't show |
| **Comp set monitoring** | Your comp set's IDs, collected once | Their reviews and ratings tracked alongside your own |

The most common next step is [pulling reviews programmatically](https://stayapi.com/blog/tripadvisor-reviews-api): 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](https://stayapi.com/free-tools/tripadvisor-hotel-details) 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.

Ship in 3 days
## Ready to simplify your hotel data?

Join other developers using StayAPI to build the next generation of travel applications. Get started for free today.

[Start Building Free](/users/sign_up)[Book a Demo](/book-demo)

[← Back to Blog](/blog)[Previous: Hotel Review Sentiment Analysis: How Revenue Managers Use It to Drive ADR →](/blog/hotel-review-sentiment-analysis)

Hotel data
### Want accurate hotel data?

Stop building data pipelines and start building product. Reliable access to hotel reviews, prices, and details with StayAPI.

[Book a Demo](/book-demo)

## Table of contents

- [Method 1: Read the Location ID From the URL](#method-1-read-the-location-id-from-the-url)
- [Method 2: Look It Up via API](#method-2-look-it-up-via-api)
- [Method 3: Bulk Lookup for a TripAdvisor Location IDs List](#method-3-bulk-lookup-for-a-tripadvisor-location-ids-list)
- [What You Can Do With a Location ID](#what-you-can-do-with-a-location-id)
- [FAQ](#faq)

About StayAPI

StayAPI: Hotel Data API

For travel-tech developers

We collect, clean, and standardize hotel data so you can build amazing travel products without maintaining your own data collection.

50+ Endpoints

5 Major Platforms

Supported sources

Booking.comTripAdvisorAirbnbAgodaGoogle Hotelsand more
