/yatra/hotels

POST /api/yatra/hotels

Price: 20 credits

Get a Yatra hotel by id: description, address, contact numbers, coordinates, stars, check-in and check-out times, amenities by category, rooms with sizes, beds and photos, nearby landmarks, dining, guest reviews with category scores and Google rating with recent Google reviews

How to use it

Take id and city from a yatra/hotels/search result.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Yatra hotel id (examples: "00002588"; pattern: ^\d{8}$)
• city string required — City name of the hotel (examples: "Manali"; minLength: 2)

Response

• @type string (default: "YatraHotel")
• id string required
• name string nullable
• description string nullable
• description_sections array (default: [])
  • @type string (default: "YatraDescriptionSection")
  • text string nullable
• policies array (default: [])
• zone string nullable
• nidhi_id string nullable
• property_type string nullable
• categories array (default: [])
• themes array (default: [])
• star_rating number nullable
• address string nullable
• pin_code string nullable
• area string nullable
• city string nullable
• state string nullable
• country string nullable
• latitude number nullable
• longitude number nullable
• phone string nullable
• fax string nullable
• check_in_time string nullable
• check_out_time string nullable
• rooms_count integer nullable
• floors_count integer nullable
• parking_slots integer nullable
• is_yatra_smart boolean (default: false)
• couple_friendly boolean (default: false)
• pet_friendly boolean (default: false)
• women_friendly boolean (default: false)
• instant_book boolean (default: false)
• is_sold_out boolean (default: false)
• image string nullable
• images array (default: [])
• amenities array (default: [])
  • @type string (default: "YatraAmenity")
  • name string required
  • category string nullable
  • is_paid boolean nullable
  • timings string nullable
• landmarks array (default: [])
  • @type string (default: "YatraLandmark")
  • name string required
  • distance_km number nullable
• dining array (default: [])
  • @type string (default: "YatraDining")
  • name string nullable
  • cuisine string nullable
  • timings string nullable
  • kind string nullable
• rooms array (default: [])
  • @type string (default: "YatraRoom")
  • id string required
  • name string nullable
  • size string nullable
  • max_guests integer nullable
  • view string nullable
  • flooring string nullable
  • beds array (default: [])
  • amenities array (default: [])
  • images array (default: [])
• reviews array (default: [])
  • @type string (default: "YatraReview")
  • author string nullable
  • text string nullable
  • rating number nullable
  • cleanliness number nullable
  • dining number nullable
  • room number nullable
  • service number nullable
  • published_at integer nullable
• google_rating number nullable
• google_review_count integer nullable
• google_reviews array (default: [])
  • @type string (default: "YatraGoogleReview")
  • author string nullable
  • text string nullable
  • rating integer nullable
  • published_at integer 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 — No Yatra hotel under that id; hotels outside India are not available 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.