Uber Eats store reviews

GET https://api.api.sh/ubereats/v1/reviews
1 credit / call food & delivery try it in the playground →

Customer reviews of an Uber Eats store as the store page shows them: review id, author's first name and initial, text, date and age, with the store's rating and rating count and, on page 1, the featured reviews. limit sets the page size; pass next_page back as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
url string The store's ubereats.com/store/<name>/<id> link (from /ubereats/v1/stores). Example: https://www.ubereats.com/store/joes-pizza-times-square-1435-broadway/F9A-B2bKRg-ikAd0B8uzgg
id string The store's UUID instead of url. Example: F9A-B2bKRg-ikAd0B8uzgg
limit integer Reviews per page, 1-100 (default 50). Example: 50
page integer Page number (default 1). Example: 1
locale string Language and market of the texts, e.g. en-US, en-GB, fr-FR, es-MX (default en-US).

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/ubereats/v1/reviews?url=https%3A%2F%2Fwww.ubereats.com%2Fstore%2Fjoes-pizza-times-square-1435-broadway%2FF9A-B2bKRg-ikAd0B8uzgg" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.