/safaribookings/reviews/search

POST /api/safaribookings/reviews/search

Price: 20 credits

Get the newest customer reviews written across the whole SafariBookings marketplace, most recent first. Every review carries the reviewer name and home country, when they travelled and when they wrote the review, their age group and safari experience, the review title, star rating, full text, any photos they uploaded and the tour operator the review is about.

How to use it

Stream the latest safari reviews from across SafariBookings, newest first. Each review has id, author_name, author_country, visited, reviewed_date, age_group, experience_level, review_title, rating, text, images, operator_id, operator_name and review_url. For the reviews of one operator use safaribookings/operators/reviews.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• 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 — The entity was not found, or a precondition failed 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.