/safaribookings/operators/reviews

POST /api/safaribookings/operators/reviews

Price: 20 credits

Get the customer reviews of a SafariBookings tour operator, optionally limited to one star rating. Every review carries the reviewer name and home country, when they travelled and when they wrote the review, their age group and how many safaris they have been on, the review title, star rating, full text and any photos they uploaded.

How to use it

Fetch customer reviews of a SafariBookings tour operator by id (p4853, 4853) or profile URL, optionally filtered to a single star rating with stars 1-5. Each review has id, author_name, author_country, visited, reviewed_date, age_group, experience_level, review_title, rating, text, images, operator_id and review_url. An operator with no reviews at the requested star rating returns an empty list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• operator string required — SafariBookings tour operator id (p4853 or 4853) or profile URL (examples: "p4853", "https://www.safaribookings.com/p4853"; minLength: 1)
• stars integer nullable — Only reviews with this star rating (min: 1; max: 5)
• count integer required — Max number of reviews to return (min: 1)

Response

• @type string (default: "SafaribookingsReview")
• id string required
• author_name string nullable
• author_country object nullable
  • @type string (default: "SafaribookingsCountryRef")
  • name string nullable
  • code string nullable
• visited string nullable
• reviewed_date string nullable
• age_group string nullable
• experience_level string nullable
• review_title string nullable
• rating number nullable
• text string nullable
• images array (default: [])
• operator_id string nullable
• operator_name string nullable
• review_url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Tour operator not found (well-formed id with no SafariBookings profile) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.