/safaribookings/operators

POST /api/safaribookings/operators

Price: 5 credits

Get one SafariBookings tour operator by its id or profile URL: company name, customer rating with the review count per star level, short description and full company profile, the countries it has offices in and the destinations it sells, the kind of tours it runs, staff size and founding year, price range per person per day in the requested currency, how many tours it offers in total and per country, postal address, phone, website, logo and team photo.

How to use it

Fetch a single African safari tour operator from SafariBookings by id (p4853, 4853) or profile URL. Returns id, name, rating, review_count, rating_breakdown, description, company_profile, office_countries, destinations, tour_types, employees, founded_in, price_from/price_to per person per day, currency, tour_count, tours_by_country, address, phone, website, image (logo), photo and profile_url. Use safaribookings/operators/reviews for its customer reviews and safaribookings/operators/tours for its tour portfolio.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• operator string required — SafariBookings tour operator id (p4853 or 4853) or profile URL (examples: "p4853", "https://www.safaribookings.com/p4853"; minLength: 1)
• currency string — Currency the price range is 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: "SafaribookingsOperator")
• id string required
• name string required
• rating number nullable
• review_count integer nullable
• rating_breakdown array (default: [])
  • @type string (default: "SafaribookingsRatingBreakdown")
  • stars integer required
  • review_count integer nullable
• description string nullable
• company_profile string nullable
• office_countries array (default: [])
  • @type string (default: "SafaribookingsCountryRef")
  • name string nullable
  • code string nullable
• destinations array (default: [])
  • @type string (default: "SafaribookingsCountryRef")
  • name string nullable
  • code string nullable
• tour_types string nullable
• employees string nullable
• founded_in integer nullable
• price_from number nullable
• price_to number nullable
• currency string nullable
• tour_count integer nullable
• tours_by_country array (default: [])
  • @type string (default: "SafaribookingsOperatorCountryTours")
  • country string required
  • tour_count integer nullable
• address string nullable
• phone string nullable
• website string nullable
• image string nullable
• photo string nullable
• profile_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 operator not found (well-formed id with no SafariBookings profile) 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.