Goibibo

Return the exact per-room-type price a real guest sees in Goibibo's own app — not a metasearch or commission-inflated affiliate price. Goibibo runs on MakeMyTrip's own backend under a different brand, so this source is resolved and fetched the same way the official Goibibo Android app does. Submit a job, receive a job_id, poll for the result.

Base URL: https://api.scrapeguys.com · Auth: X-API-Key: gsk_… with the ota:goibibo scope · See the Overview.

Submit a job

Identifying the hotel

A request identifies its hotel one of three ways, exactly as on MakeMyTrip — unsurprising, since the two share a backend.

By name (hotel_name + city) is the default — resolved through Goibibo's own app autosuggest and picked by us. It works without you knowing anything about Goibibo, and is what every existing integration uses.

By Google Place ID (place_id) is the recommended way to pin a portfolio. One id identifies the property across Agoda, Booking.com, MakeMyTrip and Goibibo. The first request for a place still goes through Goibibo's own autosuggest — there's no other way in — but the id that actually returned a price is then pinned, so every later request for that place_id addresses the same property directly. A pin is written only when Goibibo names the property and that name agrees with the Place ID's own; otherwise the job still returns prices and the next request resolves again. Send hotel_name alongside it if you have it — it's used as the search text for that one resolution; without it we look the name up from the Place ID itself.

By Goibibo's own id (ota_hotel_id, its numeric hotelId, e.g. "201709071828297454") is the fastest and most direct route once you hold it. The whole resolution step disappears, and the answer cannot drift to a different hotel between runs. It is the same id MakeMyTrip uses — if you already have a portfolio of MakeMyTrip hotelIds, they work here unchanged. The id's format is checked at submit (digits only): a malformed id is rejected with 400 before any job is created or billed. A well-formed id from another OTA cannot be told apart and is priced as Goibibo's own id — Agoda, MakeMyTrip and Goibibo ids are all plain numbers.

Checking we priced the hotel you meant. Read result.origin_hotel_name — the origin's own name for the property it priced, sourced from the same deeplink field MakeMyTrip's parser always reads. That makes it a genuine statement from the origin, not an echo of your text, even though (see Response schema below) the URL it's read from is never published as source_url on a Goibibo result. result.hotel_name cannot answer this question at all — it is your own search text echoed back, not a confirmation signal.

Device pricing — device_type

device_type is accepted and validated on Goibibo — desktop or mobile are accepted; app_android, the app route Agoda and Booking.com offer, and anything else 400 — and echoed back on the job envelope, but it has no effect on which prices you get.

Poll for results

Poll the poll_url every ~2 seconds until status is completed or failed. Statuses: pending → processing → completed | failed. Job IDs are scoped to this endpoint — a Google Hotels job ID 404s here, and vice versa.

Response schema

The poll response is a job envelope: id, status, ota, hotel_name, city, ota_hotel_id, place_id, check_in, check_out, adults, children_ages, tax_required, tax_scope, rooms, currency, device_type, result, error_message, created_at, started_at, completed_at, duration_seconds, bandwidth_kb — the same shape as every other OTA on this endpoint (children_ages is always [] here, since Goibibo rejects a non-empty one at submit; tax_required / tax_scope echo what you submitted). On completion, result holds the pricing object, which nests HotelRoomPricing → room_types[] → offers[].

Object fields

Taxes and fees — the split costs nothing here

Goibibo's room grid states its own tax line's components, so tax_amount — taxes and fees combined, the same shared contract every OTA here publishes — can be split into tax alone and the fee beside it without a second request. Agoda pays one booking-form request per rate for the same answer and Expedia two (a prepare-checkout call, then the checkout page); an itemized Goibibo job issues exactly as many requests as an ordinary one, and is one unit of quota like any other job.

Ask for the split the same way as on Agoda:

Measured 20 Sep 2026 over 306 live rates across 10 properties x 2 stay windows: 82 (27%) carry a fee inside tax_amount — a median 46% of the figure, up to 58% — e.g. a 2,333.88 combined figure that was 1,034.00 Hotel GST beside 765.00 hotelier service charge and 534.88 Goibibo service fee. Those are exactly the rows where tax_amount / price reads noticeably higher than the rest, which is why publishing the combined figure with nothing saying so was a real gap.

tax_percentage stays null on Goibibo, itemized or not — this backend states amounts, never a rate. tax_scope sent without tax_required: true is still a 400, same rule as every other OTA on this endpoint.

MakeMyTrip shares this parser and now publishes the same free tax_basis — but its tax_amount stays combined, and tax_required is still a 400 there. Booking.com has no components to read at all on its default route, so tax_required is a 400 there too — but its app_android route does itemize, free, from the app's own room list.

Result outcomes

Submitting can 4xx (validation 400, auth 401, missing scope 403, throttling 429) or, rarely, a 5xx if we couldn't accept the job on our side — retry the submit. Once a job is accepted, polling always returns HTTP 200 — you distinguish scrape outcomes by fields, never by status code:

A scrape failure is never a 4xx/5xx on the poll — it is a failed job with an explanation.

Goibibo-specific notes

• Gated while it soaks: it needs the ota:goibibo scope and an environment where the scraper is switched on — contact us to enable it on your key.
• One room per request. A value > 1 is accepted at submit but fails the job, not rejected outright — see the callout under Submit a job.
• No children yet. children_ages is rejected with 400 at submit.
• Currency: INR only.
• Device: ignored — every scrape is the Android app route, regardless of device_type.
• Price basis: always per_night_before_taxes, shared with MakeMyTrip.
• Tax split is free. tax_required splits tax_amount into tax + fee at no extra request — see Taxes and fees.
• Identity: shares MakeMyTrip's numeric hotelId space — an id you already hold for MakeMyTrip works here unchanged.
• Numeric channel code 5, added 21 September 2026 — see Addressing an OTA by number. Accepted on /ota-price/ only; a code does not imply Rate Shop offers this OTA.
• Not offered on Rate Shop. /ota-price/ only, until it has proven itself on single-property jobs, where one failure costs one job rather than a whole shop — held out under its name and its numeric code alike.
• source_url / source_url_scope are always null — see the callout under Response schema.

Next: Destination Search →