/safaribookings/tours/days

POST /api/safaribookings/tours/days

Price: 5 credits

Get the day-by-day itinerary of a SafariBookings safari tour: for every day the title and full description, the main destination park with its tag, the best time to visit, high season and best weather for that park, the chance of spotting each of the tracked animals, the accommodation with its description and website, and the meals and drinks included.

How to use it

Fetch the day-by-day plan of a SafariBookings tour by id (t42628, 42628) or URL. Each entry has day_label, day_title, description, destination and destination_tag with destination_url, best_time_to_visit, high_season, best_weather, wildlife (animal plus sighting frequency such as Abundant/Common/Occasional/Rare/Very Rare/None), accommodation and meals.

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)

Response

• @type string (default: "SafaribookingsTourDay")
• day_label string required
• day_title string nullable
• description string nullable
• destination string nullable
• destination_tag string nullable
• destination_url string nullable
• best_time_to_visit string nullable
• high_season string nullable
• best_weather string nullable
• wildlife array (default: [])
  • @type string (default: "SafaribookingsWildlifeSighting")
  • animal string required
  • frequency string nullable
• accommodation object nullable
  • @type string (default: "SafaribookingsDayStay")
  • name string nullable
  • description string nullable
  • website string nullable
• meals array (default: [])
• highlights array (default: [])

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.