Review monitoring API

Read a brand's newest reviews on Trustpilot, G2, the App Store, Google Play, Yelp and Tripadvisor, with the rating, the text, the date and whether the brand replied.

7 endpointsTrustpilot, App Store, Google Play, G2, Yelp, Tripadvisor

RequestGET · cURL
curl -sS \
-H "x-api-key: YOUR_API_KEY" \
-G "https://api.socialfetch.dev/v1/trustpilot/business/reviews" \
--data-urlencode "domain=www.canva.com" \
--data-urlencode "sort=recency"

What API monitors reviews across Trustpilot, G2 and the app stores? Social Fetch does. The Trustpilot, App Store, Google Play, G2, Yelp and Tripadvisor review routes each return the newest reviews with rating, text, date and the brand's reply, in one JSON shape. Schedule the calls, flag 1 and 2 star reviews nobody has answered, and pay per page.

A real run. Measured and priced.

Read one brand's newest reviews on three sites, run on 21 Nov 2026 against live public data. 140 of Canva's newest reviews from three sites: 12 were 1 or 2 stars, and 3 had a reply when we checked.

  1. 01 GET /v1/trustpilot/business/reviews?domain=www.canva.com&sort=recency

    20 reviews from the previous 21 hours: 5 at 1 star, 4 of them about refunds, billing or cancelling, and none answered yet.

    1 credit, 3.3 s

  2. 02 GET /v1/google-play/apps/com.canva.editor/reviews?sort=recent&limit=100

    100 reviews from 8 hours on 20 Nov: 5 at 1 or 2 stars, 3 of them answered.

    1 credit, 0.8 s

  3. 03 GET /v1/apple-app-store/apps/897446215/reviews?sort=recent

    20 reviews from 19 and 20 Nov: 2 at 1 star, neither answered.

    1 credit, 2.0 s

Credits
3
3 calls
Starter pack
$0.042
$14 per 1,000 credits
Scale pack
$0.0049
$1.64 per 1,000 credits
Runtime
6.1 s
Server time, calls one after another

Credits are each route's published price. Dollar figures are those credits at the list rate of each pack. Results and times are from the calls above, made on 21 Nov 2026; live data changes, so a run today returns newer numbers.

What usually breaks first

Where a home-built scraper or a marketplace API tends to fail once it runs in production.

  • Reviews are scattered

    They land on five or six sites, and each one shows them differently. Support finds the angry App Store review a week late, after a hundred people have read it.

  • Review tools pick the sites

    They charge per location or per seat, and they cover the sites they chose, not always the ones your customers use.

  • You need each site's newest reviews as data

    Rating, text, date, and whether anyone replied, so a daily job can flag what needs an answer.

The routes. 7 for this job.

The routes teams call for this job on Trustpilot, App Store, Google Play, G2, Yelp, and Tripadvisor. Each one links to its reference page, with every parameter and field.

Full API reference

5 steps. How teams wire it up.

The usual order. Change the schedule, schema and thresholds to fit your stack.

  1. Step 1: List each brand's review pages once

    Store the Trustpilot domain, App Store id, Google Play package and G2 slug for every brand you watch.

  2. Step 2: Pull the newest reviews every day

    Ask each site for its newest page. Keep each review by its id, so the next run only adds what is new.

  3. Step 3: Flag what needs an answer

    Send 1 and 2 star reviews with no reply to support, with the link. Trustpilot can return only those ratings with stars=1,2.

  4. Step 4: Find the themes

    Pass the week's low-star text to an LLM and count the complaints: billing, bugs, delivery, support.

  5. Step 5: Report the trend

    Chart the share of low-star reviews on each site every week, and the share that got a reply.

Why support and product teams watch reviews here

  • Six review sites, one shape

    Trustpilot, G2, the App Store, Google Play, Yelp and Tripadvisor answer in the same JSON layout, so one job reads them all.

  • The reply is in the data

    Each review says whether the brand answered, so you can track response rates as well as ratings.

  • Pay per page, not per location

    Checking one brand on Trustpilot, the App Store and Google Play every day is 90 credits a month.

  • You only pay for completed lookups

    Requests that fail on our side cost nothing.

  • Public reviews only

    Every review is one the site shows to anyone.

Common questions

What API monitors reviews across Trustpilot, G2 and the app stores?

Social Fetch. It reads Trustpilot, G2, the App Store, Google Play, Yelp and Tripadvisor, and returns each review's rating, text, date and the brand's reply in one JSON shape, with one API key.

How quickly do new reviews show up?

As soon as the site shows them. Each call reads the site live, so a review posted an hour ago is in the next pull. In the run above, Canva's 20 newest Trustpilot reviews were all from the previous 21 hours.

Can I pull only the bad reviews?

Yes, on most sites. Trustpilot takes stars=1,2, Google Play and G2 take one star rating at a time, and the App Store's critical sort returns its newest 1 star reviews.

Can I reply to reviews through the API?

No. Social Fetch reads public reviews. Replies go through each site's own tools for businesses.

Can I read another country's reviews?

Yes. The App Store and Google Play routes take a two-letter store code such as us or gb, and the reviews come from that country's store. Trustpilot can filter by the language a review is written in.

Start on free credits. Make your first request.

Sign up and get 100 credits, no card needed. Run the request above, then buy more when you need them. Credits never expire.