Paytm Flights

Live flight pricing from Paytm (INR, India region) — the same job-based /scrape/ contract as Google Flights, MakeMyTrip and Cleartrip, selected with "source": "paytm". Search, fare families and review detail (fare breakup including Paytm's convenience fee, refundability, cancellation windows, add-ons) are all available, and every call is read-only.

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

The three stages

Paytm uses the same L1 / L2 / L3 vocabulary as the other flight sources. Each stage is an ordinary job — submit, get a job_id, poll — and each later stage takes a flight_index from the search it came from.

Paytm's convenience fee — the amount that turns a listed fare into what a traveller actually pays — is available at review with no extra steps on your side. grand_total is the fee-inclusive figure.

Submit a search

curl -X POST 'https://api.scrapeguys.com/api/v1/flight-scraper/scrape/' \
  -H 'Content-Type: application/json' -H 'X-API-Key: fsk_...' \
  -d '{"origin":"DEL","destination":"BOM","departure_date":"2026-11-18",
       "adults":1,"cabin_class":"economy","currency":"INR",
       "source":"paytm"}'
# {"job_id":"9f2b...","status":"pending","poll_url":"/api/v1/flight-scraper/scrape/9f2b.../"}

Round trips — send platform=desktop

On platform=desktop a return_date prices a round trip, domestic or international, as sellable combinations (an onward + return pair) rather than two leg fares added together:

{"source": "paytm", "platform": "desktop", "origin": "DEL", "destination": "BOM",
 "departure_date": "2026-11-18", "return_date": "2026-11-22"}

On the default app client a return_date is refused at submit rather than run as a one-way, which would drop the leg you asked to price and return a result that looks complete. An omitted platform is app, so an unqualified round trip is refused too:

{"return_date": ["Paytm's app client prices one-way only. Send platform=desktop to price a round trip on Paytm's web funnel, or use source=google_flights."]}

A round trip returns both directions and the sellable pairs from the original search, so /scrape/return/ does not apply to Paytm. per_leg_fares is refused on both clients: a round trip is quoted as one combination, and the pair price is the pair's.

Poll for results

Poll every 1–2 seconds until status is completed or failed. The envelope is the one every source uses — flights, return_flights, search_context, error, error_category — so an existing parser needs no changes. flights is sorted cheapest first. Paytm adds:

{
  "flights": [{
    "airlines": ["IndiGo"], "carrier_code": "6E", "flight_numbers": ["2134"],
    "origin": "DEL", "destination": "BOM",
    "departure_time": "06:10", "arrival_time": "08:25",
    "departure_date": "2026-11-18",
    "duration": "2h 15m", "stops": 0, "layover_airports": [],
    "price": 5421, "total_price": 5421, "currency": "INR",
    "refundable": "Refundable", "bookable": true,
    "segments": [ ... ], "layovers": [ ... ],
    "paytm_ids": { "provider": "...", "flightid": "...", "solution_id": "...", "fare_options": [ ... ] }
  }],
  "return_flights": [],
  "nearby_airport_options": [ ... ],
  "search_context": {
    "source": "paytm", "platform": "app", "no_results": false,
    "trip_type": "one_way", "applied_currency": "INR",
    "requestid": "...", "stops_filtered_out": 0
  },
  "search_metadata": {
    "source": "paytm", "retrieved_at": "2026-11-10T09:30:12+00:00",
    "total_options": 60, "nearby_airport_count": 12
  },
  "error": null, "error_category": ""
}

• price is per adult; total_price is the whole party. Neither includes Paytm's convenience fee — that arrives with fare families and review.
• stops_filtered_out is a count, not a flag: how many bookable options max_stops excluded. 0 with no_results: true means the route genuinely has nothing. Same name and meaning as on MakeMyTrip and Cleartrip.
• bookable: false marks an option listed without a sellable fare. Skip it if you pick your own option rather than using the expansions.
• paytm_ids is what the expansions need, including every fare option the flight was listed with. You never send it — they take an index.

An empty route is not an error

A route Paytm does not sell comes back status: "completed", error: null and search_context.no_results: true. Check no_results, not error.

Substituted airports — nearby_airport_options

Paytm answers some route searches with flights that do not fly the route you asked for. A DEL → BOM search comes back with HDO → BOM and DXN → BOM rows (Hindon and Noida standing in for Delhi) and DEL → NMI rows (Navi Mumbai standing in for Mumbai). Paytm flags each of these itself.

• flights[] answers the route you asked for. Substituted-airport itineraries are published in result.nearby_airport_options[] instead, in the same row shape, and search_metadata.nearby_airport_count gives how many there are.
• Nothing is discarded. They are real, priced, bookable fares — just not the journey you searched. This matters because they can be cheap: left in flights, one could read as the cheapest fare for a trip that flies neither of your airports.
• This is the same key with the same meaning as on MakeMyTrip. (Cleartrip reaches a similar place differently: it drops them unless you send include_nearby_airports.)

Batch scraping

POST /api/v1/flight-scraper/batch/ and /batch/results/ accept "source": "paytm" with the same rules as /scrape/. GET /usage/ is unchanged.

Expansion endpoints

The search context and its TTL

Expansions resume the search using values stored on the job, so you never pass them — but they expire (30 minutes by default). Past that the expansion is refused before any request is made, with error_category: "invalid_input". Retrying cannot help; re-run the search and expand a row from the new result.

Fare families

curl -X POST 'https://api.scrapeguys.com/api/v1/flight-scraper/scrape/fares/' \
  -H 'Content-Type: application/json' -H 'X-API-Key: fsk_...' \
  -d '{"job_id":"9f2b...","flight_index":0,"source":"paytm"}'
# 202, then poll the returned job

Paytm lists a flight's fare options with the search itself, so result.fare_families[] is built from the stored search — no new search is run. Each family carries name, per_adult, total and refundable.

• The selected family (the one the search ranked cheapest) is repriced once, which fills conv_fee and grand_total — the convenience-fee-inclusive total the listing omits.
• The other families carry conv_fee: null and grand_total: null. Their fee is not computed in this release; do not compare a family's listed price against the selected family's grand_total.

Review

POST /scrape/review/ returns the fare breakdown, the cancellation and modification rules, and (by default) the add-on catalogue for one itinerary. Same request shape as fares: job_id, flight_index, "source": "paytm".

What a review returns

• result.review — totalfare, base_fare, total_tax, conv_fee_per_adult, order_conv_fee and grand_total, where grand_total = totalfare + order_conv_fee. grand_total is the figure a traveller pays.
• result.minirules — refundable plus per-sector cancellation and modification rules.
• result.ancillaries — addons (insurance and partner add-ons with a per-traveller premium), seats (seat-map summary per sector), ancillary (meal and extra-baggage availability) and promos (applicable promo codes, often empty). Promo codes are listed but not priced.

Errors on this source

The same vocabulary as every other source, so existing dashboards and retry logic work unchanged.

Not supported on this source

• Round trips on platform=app — one-way only there; use platform=desktop.
• Checkout and payment — not part of this API.
• Calendar / price-per-day — no endpoint exists.
• Promo-code pricing — codes are listed on review but not applied or compared.
• Currencies and regions other than INR / in.

Next: Google Flights · MakeMyTrip Flights · Cleartrip Flights