Skip to content
Docs
Guest reviews

Agoda reviews

Agoda guest reviews for one property id, newest first by default.

POST/v1/ota/agoda/reviews
2 creditsTry it

Agoda shows Booking.com's reviews next to its own; each row says which in provider. Agoda pages per provider (a page of 10 holds up to 10 of each); providers filters after the fetch. Ratings 0-10; the property's reply and its date ride on the row. total (page 1 only) is Agoda's combined count across providers.

Request

POSThttps://api.scrapercompany.com/v1/ota/agoda/reviews

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

Run this request on your own API key from this page, with the values you type. Signed out? Sign in or get an API key.

Body

JSON object. Unknown fields are rejected with 422.

  • property_idstringrequiredmin length 1, pattern ^\d+$

    Numeric id from POST /v1/ota/agoda/search, or the hotel_id in an Agoda URL.

  • pageintegerdefault 1min 1, max 500

    Page, from 1.

  • page_sizeintegerdefault 10min 1, max 50

    Reviews per page per provider.

  • sortstringdefault recent

    Agoda's own sort options.

    One ofrecentrating_highrating_lowhelpful

  • providersarray of string | null

    Keep only these providers' reviews.

Example request

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

Response

200 — Agoda's own and Booking.com-sourced reviews, each row naming its provider. Metered responses carry x-credits-charged and x-credits-remaining headers (see credit headers).

200 response
{
  "source": "agoda",
  "property_id": "746293",
  "total": 5291,
  "offset": 0,
  "limit": 10,
  "rating_scale": 10,
  "next_page_token": "2",
  "count": 2,
  "pages_fetched": 1,
  "reviews": [
    {
      "source": "agoda",
      "review_id": "1180961352",
      "rating": 10,
      "title": "Exceptional",
      "text": "Good service clean and well priced",
      "date": "2026-09-13",
      "author": "Guest A",
      "author_country": "Egypt",
      "trip_type": "Couple",
      "stay_date": "2026-09-10",
      "room_type": "Superior King",
      "management_reply": "Dear Guest, thank you for staying with us.",
      "helpful_votes": 0,
      "provider": "agoda",
      "stay_info": "Stayed 3 nights",
      "management_reply_date": "2026-09-21",
      "rating_scale": 10
    },
    {
      "source": "agoda",
      "review_id": "1187623323",
      "rating": 9,
      "text": "Location + food + ambience",
      "negative_text": "Warm aircon",
      "date": "2026-09-22",
      "author": "Guest D",
      "author_country": "Australia",
      "trip_type": "Group",
      "stay_date": "2026-09-18",
      "helpful_votes": 0,
      "provider": "booking",
      "rating_scale": 10
    }
  ],
  "provenance": {
    "schema_version": 1,
    "observation_id": "rateobs_a84d8c8e368f9625974317eb8c53a860",
    "collection_id": "ratecol_0123456789abcdef0123456789abcdef",
    "observed_at": "2026-10-03T05:30:00.000Z",
    "source": "agoda",
    "source_kind": "reviews",
    "source_property_id": "746293",
    "price_basis": "unknown",
    "derivation": "upstream"
  },
  "elapsed_s": 1.42,
  "collection_id": "ratecol_0123456789abcdef0123456789abcdef",
  "observed_at": "2026-10-03T05:30:00.000Z",
  "warnings": []
}

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: the account's credits mode is enforce (mode in GET /v1/billing) and the request costs more than the available credits. Nothing is run or charged.

{"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 (in enforce credits mode) 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

Press Try it above to run this request on your own key, with the values you type (sign in first). For a no-code walkthrough, use the workspace’s guided Try it.

  1. Export your key: export SCRAPERCOMPANY_API_KEY=sk_... (no key yet? start a free trial).
  2. Copy the cURL example above and run it in a terminal.

Credits

2 credits per successful call. Failed, blocked and empty results are free.

Questions about this page?

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

Email support