Skip to content
Docs
Apple App Store

App Store reviews

One page (up to 20, Apple's cap) of written App Store reviews.

POST/v1/app_store/reviews
2 creditsTry it2 per page (an empty page and failed requests are free)

From the App Store web client's own catalog reviews endpoint — no browser, no token. sort: most_helpful (the App Store page's order), most_recent, most_favorable, most_critical. Each review: id, title, text, stars, author, date (Apple's ISO), whether it was edited, and the developer's response with its date. Page with offset = the previous answer's next_offset (absent on the last page). Ratings without text are not reviews and never appear here. An empty page is free; an unknown app is a 404.

Request

POSThttps://api.scrapercompany.com/v1/app_store/reviews

Authenticate with your API key in the x-api-key header (see Authentication).

Body

JSON object. Unknown fields are rejected with 422.

  • app_idstringrequiredpattern ^(id)?\d{1,12}$

    Numeric App Store id, e.g. 324684580: the number after id in an apps.apple.com URL (apps.apple.com/us/app/spotify-…/id324684580) or app_id from POST /v1/app_store/search. An id prefix is accepted.

  • countrystringdefault uspattern ^[A-Za-z]{2}$

    App Store storefront, two letters (us, gb, jp). Price, currency and ratings are per storefront.

    251 allowed values

    ad, ae, af, ag, ai, al, am, ao, aq, ar, as, at, au, aw, ax, az, ba, bb, bd, be, bf, bg, bh, bi, bj, bl, bm, bn, bo, bq, br, bs, bt, bv, bw, by, bz, ca, cc, cd, cf, cg, ch, ci, ck, cl, cm, cn, co, cr, cu, cv, cw, cx, cy, cz, de, dj, dk, dm, do, dz, ec, ee, eg, eh, er, es, et, fi, fj, fk, fm, fo, fr, ga, gb, gd, ge, gf, gg, gh, gi, gl, gm, gn, gp, gq, gr, gs, gt, gu, gw, gy, hk, hm, hn, hr, ht, hu, id, ie, il, im, in, io, iq, ir, is, it, je, jm, jo, jp, ke, kg, kh, ki, km, kn, kp, kr, kw, ky, kz, la, lb, lc, li, lk, lr, ls, lt, lu, lv, ly, ma, mc, md, me, mf, mg, mh, mk, ml, mm, mn, mo, mp, mq, mr, ms, mt, mu, mv, mw, mx, my, mz, na, nc, ne, nf, ng, ni, nl, no, np, nr, nu, nz, om, pa, pe, pf, pg, ph, pk, pl, pm, pn, pr, ps, pt, pw, py, qa, re, ro, rs, ru, rw, sa, sb, sc, sd, se, sg, sh, si, sj, sk, sl, sm, sn, so, sr, ss, st, sv, sx, sy, sz, tc, td, tf, tg, th, tj, tk, tl, tm, tn, to, tr, tt, tv, tw, tz, ua, ug, uk, um, us, uy, uz, va, vc, ve, vg, vi, vn, vu, wf, ws, xk, ye, yt, za, zm, zw

  • sortstringdefault most_helpful

    Apple's own review order. - most_helpful: Most helpful (the App Store page's own order) - most_recent: Newest first - most_favorable: Most favorable first - most_critical: Most critical first

    One ofmost_helpfulmost_recentmost_favorablemost_critical

  • offsetintegerdefault 0min 0, max 50000

    Reviews to skip: 0 for the first page, then the previous answer's next_offset (steps of 20).

Example request

curl -X POST "https://api.scrapercompany.com/v1/app_store/reviews" \
  -H "x-api-key: $SCRAPERCOMPANY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "app_id": "324684580"
  }'

Response

200 — One page of App Store reviews (sort most_recent) with next_offset. Metered responses carry x-credits-charged and x-credits-remaining headers (see credit headers).

200 response
{
  "search_parameters": {
    "engine": "app_store_reviews",
    "app_id": "1010865877",
    "country": "us",
    "sort": "most_recent",
    "offset": 0
  },
  "reviews": [
    {
      "review_id": "14626730862",
      "title": "Year later update",
      "text": "Same satisfaction as last post.…",
      "rating": 5,
      "author": "Reviewer A",
      "date": "2026-10-04T13:25:50Z",
      "edited": true,
      "developer_response": {
        "id": "61336294",
        "text": "Thanks for posting this encouragement!…",
        "date": "2026-04-17T04:16:19Z"
      }
    },
    {
      "review_id": "14628768234",
      "title": "Super Capable Budgeting App",
      "text": "This is the best subscription I have.…",
      "rating": 5,
      "author": "Reviewer B",
      "date": "2026-10-05T00:42:40Z",
      "edited": false
    }
  ],
  "total": 2,
  "next_offset": 20,
  "meta": {
    "source": "app_store",
    "wire_bytes": 19543,
    "elapsed_s": 0.069
  }
}

Errors

Errors return a JSON body with a detail field. Failed requests are not charged. See Errors for the full list and retry advice.

StatusMeaningRetry?
401Unauthorized

Missing or invalid API key.

{"detail":"missing or invalid API key"}
No, fix the request
402Payment Required

Not enough credits for this request. Only returned once credit enforcement is switched on; during the beta metering runs in shadow mode and never blocks.

{"detail":"insufficient credits: this request costs 5, 0 available. Credits renew 2026-11-01."}
No, fix the request
404Not Found

The property, stay, job or record was not found.

{"detail":"job not found"}
No, fix the request
422Unprocessable Content

Request validation failed. detail is a list of problems for schema errors, or a string for semantic checks performed by the endpoint.

{"detail":[{"loc":["body","name"],"msg":"Field required","type":"missing"}]}
No, fix the request
429Too Many Requests

Too many requests: the key's requests-per-minute limit was exceeded, or (once credit enforcement is on) the plan's concurrent-request limit. No rate-limit or Retry-After headers are sent; back off and retry.

{"detail":"rate limit 60/min exceeded"}
Yes, with backoff
502Bad Gateway

The upstream source failed, blocked the request or returned an unusable answer. Safe to retry later; failed requests are not charged.

{"detail":"RuntimeError"}
Yes, with backoff
503Service Unavailable

Temporarily unavailable: a dependency of this endpoint is down, or the upstream source changed its contract. Retry later.

{"detail":"database unavailable: OperationalError"}
Yes, with backoff

Try it

The quickest way: open this endpoint in Try it. It runs on your account with the example request filled in, shows the cost before you run, and shows the answer as a readable table next to the JSON and the code. Signed out? You sign in first and come straight back.

  1. Export your key: export SCRAPERCOMPANY_API_KEY=sk_... (no key yet? request access).
  2. Copy the cURL example above and run it in a terminal.
  3. Or open the interactive playground on api.scrapercompany.com, paste your key and pick this endpoint.

Credits

2 credits per successful call (2 per page (an empty page and failed requests are free)). Failed, blocked and empty results are free. Credit metering is in beta and does not block requests yet.

Questions about this page?

Send the page link and your question, and the team will answer.

Email support