/safaribookings/tours

POST /api/safaribookings/tours

Price: 10 credits

Get one SafariBookings safari tour by its id or URL: title, description, duration, price per person in the requested currency, the countries and parks visited day by day, tour features such as comfort level, group size and customization, activities and transportation, accommodation and meals per day, minimum age, and the offering tour operator with rating, review count, offices, size, address, phone and website.

How to use it

Fetch a single African safari tour from SafariBookings by id (t42628, 42628) or URL. Returns id, tour_title, description, duration_days, price, currency, countries, itinerary (day-by-day stops with park links), features, activities, accommodation (per-day lodging and meals), min_age, is_camping, operator (id, name, rating, review_count, offices, founded_in, employees, address, phone, website) and tour_url. Use safaribookings/tours/days for full day descriptions and wildlife tables, safaribookings/tours/rates for seasonal rates and inclusions.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tour string required — SafariBookings tour id (t42628 or 42628) or tour URL (examples: "t42628", "https://www.safaribookings.com/tours/t42628"; minLength: 1)
• currency string — Currency prices 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: "SafaribookingsTour")
• id string required
• tour_title string required
• description string nullable
• duration_days integer nullable
• is_available boolean (default: true)
• price number nullable
• currency string nullable
• native_currency string nullable
• countries array (default: [])
• itinerary array (default: [])
  • @type string (default: "SafaribookingsTourItineraryStop")
  • day_label string nullable
  • name string required
  • tag string nullable
  • country string nullable
  • park_url string nullable
• features array (default: [])
  • @type string (default: "SafaribookingsTourFeatureItem")
  • name string required
  • description string nullable
• activities array (default: [])
• accommodation array (default: [])
  • @type string (default: "SafaribookingsTourStay")
  • days string nullable
  • name string nullable
  • description string nullable
  • meals string nullable
  • website string nullable
• min_age integer nullable
• is_camping boolean nullable
• operator object nullable
  • @type string (default: "SafaribookingsTourOperator")
  • id string nullable
  • name string nullable
  • rating number nullable
  • review_count integer nullable
  • office_countries array (default: [])
    • @type string (default: "SafaribookingsCountryRef")
    • name string nullable
    • code string nullable
  • founded_in integer nullable
  • employees string nullable
  • address string nullable
  • phone string nullable
  • website string nullable
  • profile_url string nullable
• image string nullable
• tour_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 not found (well-formed id with no SafariBookings listing) 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.