# Flightpoints & Roame Award Flight Scraper (`abotapi/flightpoints-award-scraper`) Actor

Multi-source award flight availability from Flightpoints.com + Roame.travel. Search any route and date for miles, taxes, available seats, cabins, stops, loyalty program and operating airline per itinerary — across dozens of loyalty programs. Per-cabin miles/taxes/seats/stops, fare-class.

- **URL**: https://apify.com/abotapi/flightpoints-award-scraper.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Categories:** Travel, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 62.5% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 award itineraries

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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):

```json
{
  "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.

# Actor input Schema

## `mode` (type: `string`):

Choose 'search' to run one route or a bulk list of routes, or 'url' to scrape pasted search links from flightpoints.com/search or roame.travel/search.

## `origin` (type: `string`):

Origin airport IATA code, e.g. JFK. Used with Destination + Departure date for a single-route search.

## `destination` (type: `string`):

Destination airport IATA code, e.g. LHR.

## `departureDate` (type: `string`):

Departure date as YYYY-MM-DD (within ~60 days forward). Leave blank to use the next ~30 days out.

## `routes` (type: `array`):

Optional. A list of routes to search in one run, overrides the single-route fields above. Each item is an object {"origin":"JFK","destination":"LHR","departureDate":"2026-09-16"} or a CSV-style line "JFK,LHR,2026-09-16". Paste multiple lines for a bulk campaign.

## `sources` (type: `array`):

Which award-search engines to query. Default: both.

## `urls` (type: `array`):

Only used when mode = url. Paste one or more search links, e.g. 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 . Multiple links supported.

## `searchClass` (type: `string`):

Cabin class to search on Roame. Flightpoints returns all cabins regardless.

## `daysAround` (type: `integer`):

Widen the search by +/- this many days around the departure date. Flightpoints returns every date in the window; Roame spreads the search across it.

## `directOnly` (type: `boolean`):

Return non-stop itineraries only.

## `maxItems` (type: `integer`):

Maximum number of award itineraries to return across the whole run. This is the run's cap. Use 0 for unlimited.

## `fetchDetails` (type: `boolean`):

Off by default. When on, Flightpoints results also return per-flight detail: departure/arrival times, duration, stops, distance, per-cabin cash prices and seats, the segments that make up each itinerary (with layover times — stopover info) and a booking link. Each enriched itinerary is charged a small surcharge; the base per-itinerary charge still applies.

## `proxy` (type: `object`):

Apify Proxy. Datacenter is the default and is enough for both sources; pick residential if you hit empty results from a particular network.

## `resumeFromRunId` (type: `string`):

Paste a previous run ID or dataset ID to continue a large crawl without returning or charging for itineraries already collected there. Use this after an interrupted run, or when continuing a campaign in another run. For recurring daily monitoring of the same routes, use Incremental mode below instead.

## `incrementalMode` (type: `boolean`):

Turn this on for daily or recurring monitoring. The first run returns all matching itineraries as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED itineraries. Turn on "Emit unchanged" or "Emit expired" only when you also want those itineraries returned (and billed). State is kept separately for each route/URL and detail-mode setup; use State key when you want to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.

## `stateKey` (type: `string`):

Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from the routes/URLs and detail settings — different routes then never mix state with each other.

## `emitUnchanged` (type: `boolean`):

Off by default. Turn on to also return itineraries that have not changed since the last run, marked UNCHANGED. This returns — and bills — extra rows you already have, so leave it off unless you specifically want the full snapshot every run.

## `emitExpired` (type: `boolean`):

Off by default. Turn on to also return itineraries that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked routes — not when Max itineraries capped it or when Resume was used. This returns — and bills — extra synthetic rows, so leave it off unless you need expiry tracking.

## `mcpConnectors` (type: `array`):

Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify, Settings, API & Integrations, then select it here. Notion gets a rich page-per-item export; other connectors get a best-effort write/digest. Leave empty to skip; never changes the dataset output. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).

## `notionParentPageUrl` (type: `string`):

URL or id of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.

## `maxNotifyListings` (type: `integer`):

Cap on items written to each connector per run. Does not affect the dataset.

## Actor input object example

```json
{
  "mode": "search",
  "origin": "JFK",
  "destination": "LHR",
  "sources": [
    "flightpoints",
    "roame"
  ],
  "urls": [
    "https://flightpoints.com/search?origins=JFK&destinations=LHR&date=2026-09-16"
  ],
  "searchClass": "ECON",
  "daysAround": 0,
  "directOnly": false,
  "maxItems": 20,
  "fetchDetails": false,
  "proxy": {
    "useApifyProxy": true
  },
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "maxNotifyListings": 50
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "search",
    "origin": "JFK",
    "destination": "LHR",
    "departureDate": "",
    "sources": [
        "flightpoints",
        "roame"
    ],
    "urls": [
        "https://flightpoints.com/search?origins=JFK&destinations=LHR&date=2026-09-16"
    ],
    "proxy": {
        "useApifyProxy": true
    },
    "incrementalMode": false,
    "emitUnchanged": false,
    "emitExpired": false
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/flightpoints-award-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "mode": "search",
    "origin": "JFK",
    "destination": "LHR",
    "departureDate": "",
    "sources": [
        "flightpoints",
        "roame",
    ],
    "urls": ["https://flightpoints.com/search?origins=JFK&destinations=LHR&date=2026-09-16"],
    "proxy": { "useApifyProxy": True },
    "incrementalMode": False,
    "emitUnchanged": False,
    "emitExpired": False,
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/flightpoints-award-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "search",
  "origin": "JFK",
  "destination": "LHR",
  "departureDate": "",
  "sources": [
    "flightpoints",
    "roame"
  ],
  "urls": [
    "https://flightpoints.com/search?origins=JFK&destinations=LHR&date=2026-09-16"
  ],
  "proxy": {
    "useApifyProxy": true
  },
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false
}' |
apify call abotapi/flightpoints-award-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,abotapi/flightpoints-award-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Rp0Oehz58p0885ama/builds/BVVS1bDqCBAyrltSQ/openapi.json