/agoda/hotels/rooms

POST /api/agoda/hotels/rooms

Price: 10 credits

Get the live room rate grid for an Agoda hotel by property id (or hotel URL) for specific check-in / check-out dates and occupancy. Returns each available room type with its size, view and bed features, amenities, photos, guest review score and the list of bookable rate offers. Every offer carries the nightly price and currency, meal plan, cancellation policy, pay-later / pay-at-hotel flags, whether a credit card is required, the supplier and how many rooms are left. Prices and availability depend on the requested dates and occupancy.

How to use it

Fetch the per-room rate grid for one Agoda hotel by numeric property id (or a hotel URL containing hotelId) for given check_in and check_out dates. Set adults, children_ages (one age per child) and rooms for the occupancy, and count for how many room types to return. Returns a list of room types, each with id, room_type, is_sold_out, room_size, review_score, features, facilities, amenities, images, min_price and offers. Each offer has rate_plan_id, price, currency, price_text, price_info, meal, is_breakfast_included, cancellation, is_free_cancellation, is_pay_later, is_pay_at_hotel, is_credit_card_required, supplier_id, remaining_room_count and benefits. An empty result means the hotel has no rooms available for the selected dates.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• hotel string required — Agoda property id or a hotel URL containing it (examples: "8000", "https://www.agoda.com/the-ritz-carlton-osaka/hotel/osaka-jp.html?hotelId=8000"; minLength: 1)
• check_in string required — Check-in date in YYYY-MM-DD format (examples: "2026-06-25")
• check_out string required — Check-out date in YYYY-MM-DD format (examples: "2026-06-27")
• adults integer — Number of adult guests (default: 2; min: 1)
• children_ages array — Age of each child guest (one entry per child) (default: [])
• rooms integer — Number of rooms requested (default: 1; min: 1)
• count integer required — Max number of room types to return (min: 1)

Response

• @type string (default: "AgodaRoom")
• id string required
• room_type string nullable
• is_sold_out boolean nullable
• room_size string nullable
• review_score number nullable
• features array (default: [])
• facilities array (default: [])
• amenities array (default: [])
• images array (default: [])
• min_price number nullable
• offers array (default: [])
  • @type string (default: "AgodaRoomOffer")
  • rate_plan_id integer nullable
  • price number nullable
  • currency string nullable
  • price_text string nullable
  • price_info string nullable
  • meal string nullable
  • is_breakfast_included boolean nullable
  • cancellation string nullable
  • is_free_cancellation boolean nullable
  • is_pay_later boolean nullable
  • is_pay_at_hotel boolean nullable
  • is_credit_card_required boolean nullable
  • supplier_id integer nullable
  • remaining_room_count integer nullable
  • benefits 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 — Hotel not found (well-formed but nonexistent property id) 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.