/safaribookings/countries

POST /api/safaribookings/countries

Price: 5 credits

Get a SafariBookings safari country guide by its slug: name, expert introduction, typical daily rate range per person in the requested currency, best time to go, high season and size, separate expert and traveller ratings broken down into wildlife, scenery, bush vibe and birding, pros and cons, the long-form guide sections, the headline parks and reserves, the author of the guide, how many safaris are on offer, header photo, Wikipedia link and map.

How to use it

Fetch an African safari country guide from SafariBookings by slug (kenya, tanzania, botswana, namibia, south-africa, uganda, rwanda, zambia, zimbabwe, ...) or country URL. Returns alias, name, description, rate_from/rate_to per person per day, currency, best_time_to_go, high_season, size, user_ratings and expert_ratings, pros, cons, sections, parks, expert, tour_count, image, wikipedia_url, map_url and country_url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• country string required — SafariBookings safari country slug or country URL (examples: "kenya", "https://www.safaribookings.com/tanzania"; minLength: 1)
• currency string — Currency daily rates are returned in (default: "USD"; one of: "USD", "CAD", "EUR", "CHF", "CZK", "DKK", "GBP", "HUF", "ISK", "NOK", "PLN", "RON", "RUB", "SEK", "TRY", "AUD", "NZD", "AED", "CNY", "HKD", "ILS", "INR", "JPY", "KRW", "KWD", "MYR", "QAR", "SAR", "SGD", "TWD", "EGP", "NAD", "ZAR", "ARS", "BRL", "CLP", "MXN")

Response

• @type string (default: "SafaribookingsCountry")
• alias string required
• name string required
• description string nullable
• rate_from number nullable
• rate_to number nullable
• currency string nullable
• best_time_to_go string nullable
• high_season string nullable
• size string nullable
• user_ratings object nullable
  • @type string (default: "SafaribookingsSubjectRatings")
  • rating number nullable
  • review_count integer nullable
  • sub_ratings object nullable
    • @type string (default: "SafaribookingsSubRatings")
    • wildlife number nullable
    • scenery number nullable
    • bush_vibe number nullable
    • birding number nullable
• expert_ratings object nullable
  • @type string (default: "SafaribookingsSubjectRatings")
  • rating number nullable
  • review_count integer nullable
  • sub_ratings object nullable
    • @type string (default: "SafaribookingsSubRatings")
    • wildlife number nullable
    • scenery number nullable
    • bush_vibe number nullable
    • birding number nullable
• pros array (default: [])
• cons array (default: [])
• sections array (default: [])
  • @type string (default: "SafaribookingsSubjectSection")
  • heading string required
  • text string required
• parks array (default: [])
  • @type string (default: "SafaribookingsSubjectLink")
  • name string required
  • note string nullable
  • url string nullable
• expert object nullable
  • @type string (default: "SafaribookingsSubjectExpert")
  • name string nullable
  • bio string nullable
  • image string nullable
  • links array (default: [])
  • expert_url string nullable
• tour_count integer nullable
• image string nullable
• wikipedia_url string nullable
• map_url string nullable
• country_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 — Country not found (slug with no SafariBookings country 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.