Flightpoints & Roame Award Flight Scraper

Scrape award flight availability — flights you can book with airline miles and credit-card points — from Flightpoints and Roame in a single actor. Give any route and date and get the miles, taxes, available seats, cabins, stops, loyalty program and operating airline for every itinerary, from both sources, in one clean schema.

Why use this scraper

• Two sources, one schema. Flightpoints + Roame normalised into identical rows — more coverage than any single-source award scraper, no glue code.
• Per-cabin detail. Economy, premium, business and first — each with its own miles, taxes, seat count and stops.
• Dozens of loyalty programs. Aeroplan, Flying Blue, AAdvantage, Alaska, Avios, LifeMiles, SkyMiles, KrisFlyer and more — across Star Alliance, oneworld and SkyTeam.
• Fare-class detail, stopovers and booking links. Turn on Add flight detail for per-flight segments (with layover times), aircraft, cash prices and a booking link.
• One route or bulk. Search a single origin/destination/date, pass a list of routes (paste CSV-style lines), or paste search links.
• Monitoring. Incremental mode returns only what changed on every scheduled run (NEW / UPDATED / REAPPEARED / EXPIRED).

Overview

The actor queries the live award-search engines behind Flightpoints and Roame, polls each until the search completes, and returns one normalised row per award itinerary. Built for points-and-miles tools, availability monitors and travel-hacking dashboards. Export as JSON, CSV or Excel.

Supported inputs

Input	Example
Single route	origin: JFK, destination: LHR, departureDate: 2026-09-16
Bulk routes	routes: [{ "origin":"JFK","destination":"LHR","departureDate":"2026-09-16" }, …] or "JFK,LHR,2026-09-16" per line
Pasted links	https://flightpoints.com/search?origins=JFK&destinations=LHR&date=2026-09-16 or https://roame.travel/search?from=JFK&to=LHR&departureDate=2026-09-16
Sources	["flightpoints","roame"] (default both)
Cabin	searchClass: ECON | PREM | BUS | FIRST (Roame)
Filters	daysAround (± date window), directOnly (non-stop only)
Details	fetchDetails — per-flight segments, stopovers and booking links (billed)

Dates must be within ~60 days forward (the award engines' limit).

Input configuration

Field	Type	Description
mode	enum	search (routes + filters) or url (pasted links).
origin / destination	string	Airport IATA codes (single-route mode).
departureDate	string	YYYY-MM-DD, within ~60 days.
routes	array	Bulk list of {origin,destination,departureDate} or "ORIGIN,DEST,DATE" lines; overrides single route.
urls	array	Pasted search links (url mode).
sources	array	flightpoints and/or roame. Default both.
searchClass	string	ECON / PREM / BUS / FIRST (Roame).
daysAround	integer	Widen by ± N days.
directOnly	boolean	Non-stop itineraries only. Applies to both sources.
maxItems	integer	Cap on itineraries (0 = unlimited). Default 20.
fetchDetails	boolean	Add per-flight segments / stopovers / booking links. Billed per enriched itinerary.
incrementalMode	boolean	Recurring monitoring: only NEW / UPDATED / REAPPEARED (and optionally EXPIRED) itineraries.
resumeFromRunId	string	Continue one specific previous run / dataset.
proxy	object	Apify Proxy (datacenter by default; residential optional).

Output

One record per itinerary. Flightpoints rows are per loyalty program with a per-cabin breakdown; Roame rows are per fare. Example (illustrative values):

{
  "id": "fp|AA|JFK|LHR|2026-09-16",
  "source": "flightpoints",
  "origin": "JFK",
  "destination": "LHR",
  "departureDate": "2026-09-16",
  "program": "AA",
  "programName": "AAdvantage",
  "airline": "American Airlines",
  "alliance": "oneworld",
  "cabins": {
    "economy":  { "miles": 30000, "taxes": 5.6,  "seats": 1, "stops": 0, "airlines": ["AA", "BA"] },
    "business": { "miles": 57500, "taxes": 19.7, "seats": 1, "stops": 0, "airlines": ["AA", "BA"] }
  },
  "lastSeen": "2026-08-07T19:35:17Z",
  "scrapedAt": "2026-08-08T09:00:00Z"
}

With fetchDetails on, Flightpoints rows also carry departureTime, arrivalTime, durationMinutes, distance, bookingUrl and a segments array (one entry per flight leg with flight number, aircraft and layover time). Roame rows are per-fare: fareClass, cabinClasses, awardPoints, surcharge, roameScore, availableSeats, operatingAirlines, flightNumberOrder, equipmentTypes, itineraryHash.

Key output fields

Field	Description
source	flightpoints or roame
origin / destination / departureDate	The searched route + date
program / programName	Loyalty program (issuer code + name)
airline / alliance	Operating airline(s) + alliance
cabins{economy|premium|business|first}	Per-cabin miles, taxes, seats, stops, airlines
fareClass / cabinClasses	Fare class of a Roame fare
awardPoints / surcharge / roameScore	Roame's points, taxes and value score
availableSeats	Seats left on the fare
segments / bookingUrl	Per-flight legs (stopovers) and booking link (with details)
changeType / changedFields	NEW / UPDATED / REAPPEARED / EXPIRED + what changed (incremental mode)
lastSeen / scrapedAt	Source freshness + scrape time

FAQ

Which sources? Flightpoints and Roame — both free, public award-search engines — in one actor with one schema.

Do I need a paid account? No. Both sources are queried anonymously.

How fresh is availability? Live — each run starts a real search and polls until complete. Award seats change fast, so a row reflects availability at scrape time.

Why are some cabins missing? A cabin only appears when award space exists for it on that itinerary.

How far out can I search? ~60 days forward, the limit of the underlying engines.

Can I scrape many routes at once? Yes — pass a routes array (or CSV-style lines); each route is searched on each selected source.

How does monitoring work? Turn on Incremental mode for the same routes you run daily. The first run returns everything as NEW; later runs return only NEW, UPDATED, REAPPEARED (and, if you opt in, EXPIRED) itineraries, so you can alert on award openings and price drops.

Proxy

Both sources are public and answer from the default exit, which keeps runs cheap. If you ever get empty results, switch to a different exit profile in the run settings — some networks score certain exits more strictly.

Send results into your apps (MCP connectors)

Optionally pipe the scraped itineraries into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape — the Apify dataset is never changed.

1. Authorize a connector once under Apify → Settings → Integrations (Notion, Linear, Airtable, or Apify).
2. Select it in the mcpConnectors input field ("Pipe results into your apps"). If the picker is empty, you haven't authorized a connector yet.
3. For Notion, also set notionParentPageUrl to the page where items should be created.
4. Use maxNotifyListings to cap how many itineraries are written to each connector per run (does not affect the dataset).

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave mcpConnectors empty to skip.

Billing

A flat charge for each run start, a per-itinerary charge for each row returned, and a small per-itinerary surcharge only when Add flight detail is on (it returns extra rows with segments and booking links). You only pay for what you get.

Disclaimer

This actor queries publicly available award-search results and does not access any account behind a login. Award availability changes constantly and a scraped row does not guarantee bookability. You are responsible for using the data in compliance with each source's terms and applicable laws. Use responsibly and lawfully.