100 free credits — no credit card required.Start building
Logo
Use case

Review monitoring API across sites and app stores

Read what customers say about a product wherever they said it. Trustpilot, the App Store and Google Play are the reliable core, and Reddit sits alongside them as the unfiltered cross-check on a rating that looks too clean.

/v1/prism

Reviews from every source

  • GET /v1/trustpilot/reviews
  • GET /v1/app_store/app-reviews
  • GET /v1/google_play/app-reviews
  • GET /v1/prism/product-reviews

A review monitoring API returns customer reviews for a business, app or product as structured records you can score, store and diff over time. SocialCrawl covers Trustpilot by domain, the App Store and Google Play by app, and Reddit as the unfiltered cross-check, on one API key and one shared schema, so a review study spans sources instead of trusting one.

What teams build with it

Every one of these runs in production today. The endpoint chain under each card is the actual call sequence.

Resolve a business, then read its reviews

Search for the business to get the record, then pull its reviews sorted by recency. A clean two-step funnel, and the most reliable review lane we run.

Endpoint chainbusiness-search -> trustpilot/reviews

Both app stores in one call

Send an app name once and get reviews from the App Store and Google Play together. Cross-store comparison is the point: the same release usually lands very differently on the two platforms, and one store alone will mislead you.

Endpoint chainprism/app-reviews (both stores at once)

Store-by-store when you need control

Call each store directly when you want per-store parameters, country scoping or your own pagination strategy. Review endpoints are the healthy surface on both stores, so build here rather than on listing metadata.

Endpoint chainapp_store/app-reviews + google_play/app-reviews

Multi-merchant product reviews

Run one product across merchants to see whether a complaint is about the product or about who sold it. Merchant coverage varies by product and region, so check what came back before you treat a gap as a finding.

Endpoint chainprism/product-reviews (multi-merchant)

The unfiltered cross-check

Search Reddit for the same product. Nobody moderates a subreddit for the brand's benefit, which is exactly why every serious review study we see includes this step alongside the star ratings.

Endpoint chainreddit/search (the unfiltered cross-check)

Review integrity checks

Run a composite pass over a review set to look at timing, repetition and distribution rather than the average score. A five-star average built in one week reads very differently from the same average built over two years.

Endpoint chainprism/review-integrity

How the review monitoring API works

Four calls cover business reviews, both app stores and the multi-merchant view. Start where your subject actually lives.

Reads are priced in credits. Empty result sets are not billed on list endpoints, and failed upstream calls are refunded automatically.

  1. GET /v1/trustpilot/business-search

    Find the business

    Search by name or domain to resolve the business record before you ask for its reviews. Necessary because brand names and review-site listings rarely match exactly.

    per call
  2. GET /v1/trustpilot/reviews

    Pull the reviews

    Request reviews by domain with sorting, then cursor through for the full history rather than the first page.

    per page
  3. GET /v1/prism/app-reviews

    Add both app stores

    One composite call returns App Store and Google Play reviews for the same app, which is what makes a cross-store comparison a single step.

    per call
  4. GET /v1/prism/product-reviews

    Widen to merchants

    Run the product across merchants to separate a product complaint from a fulfilment complaint.

    per call

Where the reviews come from

Each of these is a lane in the same review study. Follow a link to see that platform's full endpoint surface.

Compared with the usual setup

Most teams either buy a reputation dashboard per site or scrape one review page and call it coverage. Here is what changes.

CapabilitySocialCrawlTypical setup
CoverageOne key spans review sites, both app stores, merchants and Reddit.One site per vendor, so a single source becomes the whole answer.
Cross-checkingA disputed rating has a second and third source on the same key.One rating, taken on trust, with no way to test it.
Response shapeOne shared schema across every source, so scoring code is written once.A different response shape per vendor, normalised by hand.
HistoryCursor pagination through the full review history, dated and storable.The most recent page, refreshed in place.
Pricing modelNever-expire credit packs, priced per call, with refunds on upstream failures.Monthly seats per location or per listing.
Building a product on topPermitted for transformed, customer-facing views. The terms say so in writing.Usually restricted or negotiated case by case.

Review monitoring API questions

What is a review monitoring API?

A review monitoring API returns customer reviews for a business, app or product as structured records rather than a dashboard. You get the review text, rating, date and author handle, which means you can score them yourself, store them and watch how the picture changes between runs.

Which review sources do you cover?

Trustpilot by domain, the App Store and Google Play by app, Tripadvisor for places, Google Shopping across merchants, TikTok Shop by region, and Reddit as the unfiltered cross-check. Amazon product and seller data is available on the same key, with the caveat below.

Are Amazon reviews reliable through this API?

Not currently, and we would rather say so than sell you a page that fails. Amazon review extraction is the least stable source we carry right now. Build the reliable core of a review workflow on Trustpilot and the app stores, and treat Amazon as supporting evidence until that upstream is fixed.

Can I compare the same app across both stores?

Yes, and it is the most common pattern here. One composite call returns App Store and Google Play reviews together, which matters because the same release usually reads very differently on the two stores. Review endpoints are the healthy surface on both.

Why does Reddit belong in a review workflow?

Because nobody moderates a subreddit for the brand's benefit. Star ratings tell you the score, Reddit tells you why, and the two disagreeing is itself a finding. In production, review work and Reddit search travel together almost without exception.

Can I detect fake reviews?

You can inspect the shape of a review set: timing, repetition, rating distribution and how the average was built over time. That is what the integrity composite reads. It is evidence for a judgement rather than a verdict, and no honest provider will hand you a definitive fake or genuine label.

How much does review monitoring cost?

Reads are priced in credits from never-expire packs, so you pay per call rather than per listing or per location. A weekly sweep of one brand across sources is a handful of calls. Signup includes 100 free credits and no card is required.

Pull your first review set

100 free credits on signup. No card, no sales call, no per-listing pricing.

Request
curl -G "https://socialcrawl.dev/v1/trustpilot/reviews" \
  -H "x-api-key: $SOCIALCRAWL_API_KEY" \
  --data-urlencode "domain=stripe.com" \
  --data-urlencode "sort=recency"
curl -G "https://socialcrawl.dev/v1/prism/app-reviews" \
  -H "x-api-key: $SOCIALCRAWL_API_KEY" \
  --data-urlencode "query=Notion"

Both calls run against live data. Swap the key and the domain and they work as written.