Multi-location brands
One feed of every new review across every branch, so a bad week at one location is seen the same day you run the job.
Use cases · Reputation
Review monitoring for local businesses. Google Maps, Yelp, Tripadvisor and Booking.com.
Collect reviews for your locations, or a competitor's, from four review sites into one feed. Each platform has a reviews operation that takes up to ten places per call and returns text, rating, date and the owner's reply where there is one.
- Google Maps
- from $0.000225 per record
- Yelp
- from $0.000225 per record
- Tripadvisor
- from $0.0018 per record
- Booking.com
- from $0.0018 per record
Updated 21 October 2026
The workflow
- List each location's URLs: a Google Maps place URL, a yelp.com/biz/ URL, a Tripadvisor place URL and a booking.com/hotel/ URL.
- Run Google Maps reviews with sort "newest" for the latest reviews, or "rating_low" to read the worst first.
- Run Yelp reviews with the same businesses' URLs or slugs.
- Run Tripadvisor reviews with since set to the day of your last run, and Booking.com reviews with sort "newest" and since.
- Read the free history operation on each platform to chart rating and review count from what earlier captures stored.
- Run it on a schedule from your own job, and alert on low ratings or reviews with no reply.
Who uses it
Agencies
Monthly reputation reports for clients: rating trend, review volume and how often the owner replied.
Hotels
Booking.com and Tripadvisor reviews carry traveler or trip type and sub-ratings, so you can see what families and business guests each say.
Operations used
List prices per record. A call can carry a minimum, so quote first: the quote is free, and a record that does not come back is not charged.
| Step | Operation | What comes back | Price |
|---|---|---|---|
| 1 | Google Maps reviews | Text, stars, date, reviewer, owner response | $0.000225 per record |
| 2 | Yelp reviews | Text, rating, date, reactions, reviewer, owner reply | $0.000225 per record |
| 3 | Tripadvisor reviews | Text, rating, dates, trip type, sub-ratings, owner response | $0.0018 per record |
| 4 | Booking.com reviews | Liked and disliked text, score, date, traveler type, property response | $0.0018 per record |
The operations in this workflow
Questions people ask.
How many reviews come back per call?
Each reviews call takes up to ten places, and limit sets how many reviews come back, up to 100.
Can I get only negative reviews?
Yes. Sort Google Maps reviews by "rating_low", keep ratings 1 and 2 on Tripadvisor with ratings, and use scoreBands "poor" and "average" or sort "rating_low" on Booking.com.
Do I get the owner's reply?
Yes, where there is one: owner response on Google Maps and Tripadvisor, owner reply on Yelp, and the property response on Booking.com.
Does history cost anything?
No. The history operations are free and read only what earlier captures already stored. They do not fetch new reviews.
Try it in a minute. $0.10 free.
The playground runs any endpoint by hand: pick a platform and what you want from it, fill a short form named in plain words (or press Use sample input), see the free quote on the Run button, run it, then read the answer as a table or JSON and download it as CSV or JSON. The same call is written out as cURL, Python and Node while you type.
Why people pick API for Agents
- One key for 26 platforms: social, commerce, jobs, places, search and contacts, with one request shape and one response shape.
- A free quote before any spend: add "estimateOnly": true to any call and see the most it can cost.
- Pay per record in US dollars. No subscription, nothing expires, top-ups from $5.
- $0.10 free to try, no card. An AI agent can sign itself up in one request; a person claims it later.
- Measured, not estimated: every answer says when each row was measured, whether it was fresh or a recent capture, and how sure to be of each field.
- Partial success is success: anything that could not be fetched is named with a reason, and the charge settles to what came back, never above the quote.
- Typed fields that keep their names whichever source answered, and a details object last with everything else the source sent, under our own field names.
- Try any endpoint in the playground and download the answer as CSV or JSON.
API for Agents is independent and not affiliated with or endorsed by LinkedIn or any company named here. LinkedIn is a trademark of LinkedIn Corporation; other names belong to their owners. Public data only: nothing behind a login.