/goibibo/buses/search

POST /api/goibibo/buses/search

Price: 20 credits

Search Goibibo bus trips between two places on a date: operator, bus type, departure and arrival times, fare and discount, seat availability by class, rating, amenities, boarding and dropping points with times

How to use it

Get place ids from goibibo/buses/places.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• from_place_id string required — Departure place id (examples: "GICC1199"; minLength: 1)
• to_place_id string required — Arrival place id (examples: "GICC1543"; minLength: 1)
• date integer required — Travel date, unix seconds (examples: 1792434600; min: 0)
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "GoibiboBus")
• id string required
• service_id string nullable
• operator_id string nullable
• operator_name string nullable
• bus_type string nullable
• from_city string nullable
• to_city string nullable
• from_place_id string nullable
• to_place_id string nullable
• departure_at integer nullable
• arrival_at integer nullable
• duration_minutes integer nullable
• fare number nullable
• fare_before_discount number nullable
• discount number nullable
• currency string (default: "INR")
• rating number nullable
• rating_count integer nullable
• bus_score number nullable
• available_seats integer nullable
• available_window_seats integer nullable
• max_seats_per_booking integer nullable
• seat_classes array (default: [])
  • @type string (default: "GoibiboSeatClass")
  • seat_type string nullable
  • condition string nullable
  • available_seats integer nullable
• amenities array (default: [])
• tags array (default: [])
• live_tracking boolean (default: false)
• is_primo boolean (default: false)
• flexible_cancellation boolean (default: false)
• boarding_points array (default: [])
  • @type string (default: "GoibiboBusStop")
  • id string required
  • name string nullable
  • location string nullable
  • address string nullable
  • landmark string nullable
  • phone string nullable
  • time integer nullable
  • latitude number nullable
  • longitude number nullable
• dropping_points array (default: [])
  • @type string (default: "GoibiboBusStop")
  • id string required
  • name string nullable
  • location string nullable
  • address string nullable
  • landmark string nullable
  • phone string nullable
  • time integer nullable
  • latitude number nullable
  • longitude number nullable
• offer object nullable
  • @type string (default: "GoibiboBusOffer")
  • description string nullable
  • seat_count integer nullable
  • terms array (default: [])
• fare_categories array (default: [])
  • @type string (default: "GoibiboFareCategory")
  • kind string nullable
  • max_seats integer nullable
  • card_required boolean (default: false)
  • card_name string nullable
  • min_age integer nullable

Errors

• 422 — The date is in the past 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.