/safaribookings/tours/rates

POST /api/safaribookings/tours/rates

Price: 5 credits

Get the seasonal rates of a SafariBookings safari tour: for every start-date period the price for a single traveler in their own room and the per-person price when sharing rooms, plus the full list of what the tour price includes and excludes and the notes on children and tipping. Prices are returned in the requested currency.

How to use it

Fetch price breakdown of a SafariBookings tour by id (t42628, 42628) or URL. Returns tour_id, currency, seasons (period with single_price and sharing_price), included, excluded and notes.

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 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: "SafaribookingsTourRates")
• tour_id string required
• currency string nullable
• native_currency string nullable
• seasons array (default: [])
  • @type string (default: "SafaribookingsSeasonRate")
  • period string required
  • single_price number nullable
  • sharing_price number nullable
• included array (default: [])
• excluded array (default: [])
• notes 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.