/safaribookings/parks/reviews

POST /api/safaribookings/parks/reviews

Price: 5 credits

Get the reviews of a SafariBookings national park or reserve, either the traveller reviews or the reviews written by the site's safari experts. Every review carries the author with their home country, when they visited, the overall rating plus separate wildlife, scenery, bush vibe and birding scores, the full text and, for expert reviews, the author biography and how many people found it helpful.

How to use it

Fetch reviews of an African safari park from SafariBookings by slug (masai-mara, serengeti, kruger). Set author to user for traveller reviews or expert for the reviews of the site's safari experts. Each review has id, author_type, author_name, author_country, author_bio, author_url, visited, reviewed_date, age_group, experience_level, review_title, rating, sub_ratings, helpful_count, text and review_url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• park string required — SafariBookings park slug or park URL (examples: "masai-mara", "https://www.safaribookings.com/serengeti"; minLength: 1)
• author string — Whether to return traveller or safari-expert reviews (default: "user"; one of: "user", "expert")
• count integer required — Max number of reviews to return (min: 1)

Response

• @type string (default: "SafaribookingsSubjectReview")
• id string required
• author_type string required
• author_name string nullable
• author_country object nullable
  • @type string (default: "SafaribookingsCountryRef")
  • name string nullable
  • code string nullable
• author_bio string nullable
• author_url string nullable
• visited string nullable
• reviewed_date string nullable
• age_group string nullable
• experience_level string nullable
• review_title string nullable
• rating number nullable
• sub_ratings object nullable
  • @type string (default: "SafaribookingsSubRatings")
  • wildlife number nullable
  • scenery number nullable
  • bush_vibe number nullable
  • birding number nullable
• helpful_count integer nullable
• text 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 — Park not found (slug with no SafariBookings park guide) 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.