# Qatar Airways Flight Scraper (`rl1987/qatarairways-api-scraper`) Actor

Scrapes Qatar Airways economy cash fares and fare families, a dated fare calendar, and live flight status, straight from the Qatar Airways mobile API. Read-only public travel data.

- **URL**: https://apify.com/rl1987/qatarairways-api-scraper.md
- **Developed by:** [R.L.](https://apify.com/rl1987) (community)
- **Stats:** 2 total users, 1 monthly users, 92.9% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 flight options

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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

## Qatar Airways Flight Scraper ✈️ — dated lowest fares & live flight status

> ## ℹ️ Fare coverage note (September 2026)
>
> Qatar Airways moved **per-flight cash fares** (`POST /flight-search/flight-offers`) behind Akamai
> Bot Manager: it now needs a device-bound `X-acf-sensor-data` sensor token and returns `403 Access
> Denied` to any headless client (on every proxy type and TLS fingerprint). So `schedules` mode now
> returns Qatar's **dated lowest-fare calendar** — real economy fares from the same API, one row per
> day — instead of per-flight cash fares. **`flightStatus` mode is unaffected.** If Qatar drops the
> sensor requirement, per-flight fares resume automatically with no change.

**Qatar Airways Flight Scraper** reads Qatar Airways' own mobile API directly, so it's **fast,
reliable and complete** — no flaky HTML parsing, no headless browser. Read-only public travel data.
Export to **JSON, CSV, Excel, or an API**.

#### Two modes

**`schedules`** (default) — Qatar Airways' **dated lowest-fare calendar** (economy) for a route
around your date: one record per day with the lowest available fare and any promo discount. The
calendar is returned by default. (Per-flight cash fares with fare families are attempted too, but
Qatar now serves that specific endpoint behind Akamai Bot Manager — see **Good to know** — so it is
best-effort and usually returns nothing; the lowest-fare calendar is the reliable fare signal.)

**`flightStatus`** — live operational status, one record per flight: arrived / on-time / delayed,
aircraft type, and scheduled, estimated **and actual** departure/arrival times. Set
`origin` + `destination` + `departureDate` for every flight on a route/date, or set `flightNumber`
(e.g. `QR11`) to track a single flight. An empty date means **today**.

```jsonc
// dated lowest fares DOH -> LHR (calendar is on by default)
{ "origin": "DOH", "destination": "LHR" }

// live status of every DOH -> LHR flight today
{ "mode": "flightStatus", "origin": "DOH", "destination": "LHR" }

// one specific flight
{ "mode": "flightStatus", "flightNumber": "QR11" }
```

Every row — flight, calendar and status — shares one flat schema, so a mixed export stays a single
table; fields that don't apply to a row type are `null`.

#### Timestamps

Times keep their **original UTC offsets** (e.g. `2026-10-06T01:10:00+03:00`), so local times are
unambiguous and no timezone is assumed on your behalf.

### ⚙️ Input

| Field | Type | Default | Description |
| --- | --- | --- | --- |
| `mode` | string | `schedules` | `schedules` = dated lowest-fare calendar (economy). `flightStatus` = live status for a route/date or one flight. |
| `origin` | string | `DOH` | Origin airport IATA code. |
| `destination` | string | `LHR` | Destination airport IATA code. |
| `departureDate` | string | – | Date, or a relative value like "30 days". Schedules: empty = +30 days. Status: empty = today. |
| `returnDate` | string | – | Schedules only. Set for a round trip. Empty = one way. |
| `adults` | integer | `1` | Number of adult passengers. |
| `currency` | string | `USD` | 3-letter currency code for fares. |
| `includeCalendar` | boolean | `true` | Schedules only. Emit one record per date from the lowest-fare calendar (the reliable fare signal). Set `false` to skip it. |
| `flightNumber` | string | – | Flight-status only. One flight, e.g. `QR11`. Empty = every flight on the route/date. |
| `maxItems` | integer | `100` | 0 = all results. |
| `proxyConfiguration` | object | RESIDENTIAL | The Akamai edge blocks datacenter IPs; a residential proxy is set by default. |

### 📤 Output

A flat record per flight / calendar date / status. Flight rows carry `flight_numbers`, `aircraft`,
`departure_time`/`arrival_time`, `duration_minutes`, `stops`, `fare_family`, `price_base`,
`price_total`, `currency`, `available_seats` and a `fare_offers` array (every fare family with its
total and seat count). Calendar rows carry `calendar_date` / `calendar_lowest_price` /
`calendar_discount_code`. Status rows carry `status`, `status_detail` and scheduled/estimated/actual
departure & arrival times.

### 📌 Good to know

- **Economy only.** Qatar's mobile fare API serves economy on this channel; Business/First return a
  gateway error and are not offered rather than shipped as an option that fails.
- **Cash per-flight fares are behind Akamai Bot Manager.** As of app v26.10.x, Qatar's mobile
  fare-offers endpoint requires a device-bound `X-acf-sensor-data` sensor token and returns HTTP 403
  "Access Denied" to any client without it (on every residential/mobile exit and TLS fingerprint) —
  so per-flight cash fares and fare families are not available headlessly. The actor returns the
  **dated lowest-fare calendar** instead (real economy fares, still from Qatar's own API), and
  **flight status is unaffected**. If Qatar removes the sensor requirement, per-flight fares resume
  automatically with no change.
- **No login, no booking, no PNR lookup** — read-only public search, exactly what the app shows a
  signed-out user. There is no request signing, API key or OAuth on this surface.
- Fare availability and prices are point-in-time and market/currency-scoped.

### 💰 Pricing — pay per result

Charged per record returned (flight option, calendar date or status row).

# Actor input Schema

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

What to scrape. "Schedules & fares" returns Qatar Airways' dated lowest-fare calendar for a route/date (economy); note that cash per-flight fares are currently blocked by the airline's Akamai Bot Manager and are attempted best-effort only. "Flight status" returns live status (on-time/arrived/delayed, aircraft, scheduled/estimated/actual times) for a route/date, or for a single flight number — unaffected by the fare-search block.

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

Origin airport IATA code, e.g. DOH.

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

Destination airport IATA code, e.g. LHR.

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

Outbound date. Pick a date or use a relative value like "30 days". Schedules mode: empty = 30 days from today. Flight-status mode: empty = today.

## `returnDate` (type: `string`):

Schedules mode only. Set for a round-trip search. Empty = one way.

## `adults` (type: `integer`):

Number of adult passengers.

## `currency` (type: `string`):

Currency for fares.

## `includeCalendar` (type: `boolean`):

Schedules mode. Emit one record per date from Qatar Airways' dated lowest-fare calendar around your departure date. On by default: cash per-flight fares (flightOffers) are currently blocked by the airline's Akamai Bot Manager, so this dated lowest-fare calendar is the working fare signal. Set to false to skip it.

## `flightNumber` (type: `string`):

Flight-status mode only. One flight, e.g. "QR11" or "11". Empty = every flight on the route/date.

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

0 = all results.

## `proxyConfiguration` (type: `object`):

The Qatar Airways edge (Akamai) blocks datacenter IPs, so a RESIDENTIAL proxy is strongly recommended and set by default.

## Actor input object example

```json
{
  "mode": "schedules",
  "origin": "DOH",
  "destination": "LHR",
  "adults": 1,
  "currency": "USD",
  "includeCalendar": true,
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `results` (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 = {
    "origin": "DOH",
    "destination": "LHR",
    "departureDate": "",
    "returnDate": "",
    "flightNumber": "",
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("rl1987/qatarairways-api-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 = {
    "origin": "DOH",
    "destination": "LHR",
    "departureDate": "",
    "returnDate": "",
    "flightNumber": "",
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("rl1987/qatarairways-api-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 '{
  "origin": "DOH",
  "destination": "LHR",
  "departureDate": "",
  "returnDate": "",
  "flightNumber": "",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call rl1987/qatarairways-api-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,rl1987/qatarairways-api-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/ounfSi0JtKVBHhXR7/builds/DPIe3wQHBG2KntsAW/openapi.json