/safaribookings/search

POST /api/safaribookings/search

Price: 5 credits

Search SafariBookings across everything it publishes at once: safari countries, parks and reserves, highlights and things to do, safari tours, tour operators, expert reviews and traveller reviews. Results can be limited to a single kind of content and each one comes back with its name, snippet, rating, review count, price range and link.

How to use it

Free-text search across SafariBookings. result_type limits results to countries, parks, highlights, tours, operators, expert_reviews or user_reviews; all mixes them. Each result has result_type, name, text, rating, review_count, price_from/price_to, author_name and result_url. For filtered tour or operator discovery use safaribookings/tours/search and safaribookings/operators/search instead.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Text to search for (examples: "serengeti", "gorilla trekking"; minLength: 1)
• result_type string — Limit results to a single kind of content (default: "all"; one of: "all", "countries", "parks", "highlights", "tours", "operators", "expert_reviews", "user_reviews")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "SafaribookingsSearchResult")
• result_type string required
• name string required
• text string nullable
• rating number nullable
• review_count integer nullable
• price_from number nullable
• price_to number nullable
• author_name string nullable
• result_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 — The entity was not found, or a precondition failed 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.