# Wizz Air Fare Calendar (`automation-lab/wizzair-fare-calendar`) Actor

Export dated Wizz Air route fares, currencies and departure times, preserving requested versus returned airports and snapshot timestamps.

- **URL**: https://apify.com/automation-lab/wizzair-fare-calendar.md
- **Developed by:** [Automation Lab](https://apify.com/automation-lab) (community)
- **Categories:** Travel
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.72 / 1,000 fare-day records

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/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Wizz Air Fare Calendar

Export the **Wizz Air fare calendar** as dated route-fare snapshots for recurring route and month comparisons. Each record contains the airline's daily minimum regular fare, source currency, departure times and snapshot timestamp.

Wizz Air can return a nearby airport instead of the airport you requested. This Actor preserves both airport pairs and flags discrepancies rather than relabeling the returned fare.

### Who is it for?

- Travel analysts comparing the cheapest departure days on a route.
- Travel planners preparing date-flexible options for clients.
- Data teams collecting repeatable route/month snapshots for spreadsheets or dashboards.

### Why use it?

The daily-fare unit makes calendar comparisons straightforward. Requested and returned airport fields protect against comparing different airports as if they were the same route. Optional exact-airport filtering removes substituted rows without changing their labels.

No account login is needed. The Actor reads public timetable data and discovers the current public backend version at runtime. It does not book flights, access customer reservations or promise a purchasable quote.

### Getting started

1. Select a Wizz Air departure and arrival airport using three-letter IATA codes.
2. Enter an inclusive future departure-date window.
3. Choose your maximum accepted fare-day records.
4. Enable **Exclude airport substitutions** if only the exact airport pair is useful.
5. Start the Actor and inspect the Dataset tab.
6. Export JSON, CSV or Excel using Apify's dataset tools.

Example input:

```json
{
  "departureIata": "BUD",
  "arrivalIata": "LTN",
  "dateFrom": "2026-11-01",
  "dateTo": "2026-11-30",
  "maxItems": 100,
  "exactAirportsOnly": false
}
```

Replace the dates with a future window before reusing this example.

### Inputs

| Field | Meaning |
| --- | --- |
| departureIata | Requested departure airport, normalized to uppercase |
| arrivalIata | Requested arrival airport, different from departure |
| dateFrom | First included departure date, YYYY-MM-DD, today or later in UTC |
| dateTo | Last included departure date; at most 366 days per search, at most 550 days ahead |
| maxItems | Global accepted record cap, default 100, range 1–366; zero/unlimited is unsupported |
| exactAirportsOnly | Default false; true excludes rows with any returned airport discrepancy |

One route per run, regular non-member fares for one adult. No passenger-count, Discount Club, round-trip, fare-bundle, price-filter or currency-conversion modes are supported.

### What data is returned?

| Field | Meaning |
| --- | --- |
| requestedDepartureIata / requestedArrivalIata | Airport pair supplied in the input |
| departureIata / arrivalIata | Airport pair actually returned by the source |
| airportMismatch | True when either returned airport differs from the request |
| departureDate | Local calendar travel date |
| price / currency | Daily minimum regular fare and source currency |
| originalPrice | Original source amount in the same currency, or null |
| departureTimes | Source local timestamps without timezone offsets |
| sourcePriceType | Source classification label, or null |
| scrapedAt | UTC timestamp when the response was collected |
| sourceUrl | Public timetable page |

**Departure times are not individually priced flights.** The daily minimum cannot be attributed to every listed departure. Arrival times, flight numbers and fare bundles are not returned.

### Output example

A representative source response to BUD–LTN included this airport substitution:

```json
{
  "requestedDepartureIata": "BUD",
  "requestedArrivalIata": "LTN",
  "departureIata": "BUD",
  "arrivalIata": "LGW",
  "airportMismatch": true,
  "departureDate": "2026-11-03",
  "price": 13890,
  "currency": "HUF",
  "originalPrice": 13890,
  "departureTimes": ["2026-11-03T06:00:00", "2026-11-03T08:30:00", "2026-11-03T17:30:00"],
  "sourcePriceType": "price",
  "scrapedAt": "2026-10-04T14:12:17.677Z",
  "sourceUrl": "https://www.wizzair.com/en-gb/flights/timetable"
}
```

Prices change. The example is an observed snapshot, not a current quote or booking offer.

### How much does it cost to export Wizz Air fare calendars?

Billing uses a one-time `start` event and the primary `item` event for each accepted fare-day saved to the dataset. Departure times within a record have no separate event charge. Excluded, duplicate and unpriced dates do not create item events.

The start fee is **$0.005 per run**. Each accepted fare-day costs:

| Apify monthly Store spend tier | Price per fare-day |
| --- | ---: |
| FREE | $0.00138 |
| BRONZE | $0.0012 |
| SILVER | $0.000936 |
| GOLD / PLATINUM / DIAMOND | $0.00072 |

Tiers follow qualifying aggregate monthly Apify Store spend, not a private per-Actor volume schedule. At BRONZE, estimated Actor charges are $0.0062 for one record, $0.029 for 20 records, and $0.125 for 100 records, including the start fee. At FREE, 20 records cost an estimated $0.0326. Consult active Apify pricing for your tier; these examples are estimates, not guaranteed invoices. No external service surcharge is charged by this Actor. Refunds, disputes, taxes, corrections and clawbacks can change final billing or publisher payout.

### Limits and completeness

Date windows are fetched sequentially in batches of at most 31 days. Records are chronological within each batch and deduplicated by returned route and date. The global cap applies after exact-airport filtering; it stops later windows when reached.

No historical fares are retrieved. The upstream airline schedule may cover less than the accepted input horizon. Days without a priced fare are omitted, not represented by synthetic prices. A valid empty calendar may therefore contain no records.

Multiple returned airport pairs can produce distinct rows on a date. Always include both returned airports in your comparison key. An exact-airport search can return fewer rows than the default search.

### Scheduling snapshots

Save the input as an Apify Task and schedule it using Apify's scheduler. Store each run's dataset with its snapshot timestamp. Scheduling is provided by Apify, not an internal polling loop in this Actor.

Group comparisons by returned airport pair, departure date and currency. Do not treat changes caused by substituted airports or different currencies as price changes for the same product. This Actor does not retain historical data or send fare alerts itself.

### Integrations

- **Google Sheets:** export fare-day rows for date-flexible planning.
- **BI tools:** ingest snapshots into a warehouse and compare route/month distributions.
- **Travel workflows:** filter `airportMismatch` before presenting options to clients.
- **Webhooks:** use Apify's completion integrations to trigger downstream ingestion.

Keep full exports in your downstream storage rather than an AI conversation's context.

### API usage

Once deployed, use the Apify API with your token supplied in an authorization header:

```bash
curl -X POST 'https://api.apify.com/v2/acts/automation-lab~wizzair-fare-calendar/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"departureIata":"BUD","arrivalIata":"LTN","dateFrom":"2026-11-01","dateTo":"2026-11-30"}'
```

JavaScript:

```javascript
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/wizzair-fare-calendar').call({
  departureIata: 'BUD', arrivalIata: 'LTN',
  dateFrom: '2026-11-01', dateTo: '2026-11-30'
});
const { items } = await client.dataset(run.defaultDatasetId).listItems({ limit: 100 });
```

Python:

```python
import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/wizzair-fare-calendar').call(run_input={
    'departureIata': 'BUD', 'arrivalIata': 'LTN',
    'dateFrom': '2026-11-01', 'dateTo': '2026-11-30'
})
items = client.dataset(run['defaultDatasetId']).list_items(limit=100).items
```

Use future dates. Follow the same run to completion before reading its dataset; API IDs are not result rows.

### MCP and AI assistants

After the Actor becomes available to your account, select its stable tool subset:

```bash
claude mcp add --transport http apify \
  "https://mcp.apify.com?tools=automation-lab/wizzair-fare-calendar"
```

Equivalent configuration for **Claude Desktop, Cursor, and VS Code** clients:

```json
{"mcpServers":{"apify":{"url":"https://mcp.apify.com?tools=automation-lab/wizzair-fare-calendar"}}}
```

Example prompt: “Export next month's BUD–LTN daily fares and highlight airport substitutions.” Authenticate through the client's supported Apify setup. Discover actual tool names and arguments with scoped `tools/list`; Actor selection also includes run and storage tools.

Start one authorized run and retain its run and storage IDs. `call-actor` waits at most 45 seconds, not necessarily until completion. If pending, check that same run with bounded 2, 4, 8, then 10-second backoff, stopping after a 120-second total deadline. On timeout, recover the known run instead of starting it again. At the deadline report pending; report terminal failures and partial rows honestly.

After success, retrieve untransformed JSON in pages of 20 source rows with explicit offset, limit and selected fields. An example consumer budget is 100 rows or 64 KiB admitted to model context, whichever comes first. Enforce bytes host-side before injection, including oversized pages; otherwise do not promise a hard byte guarantee. Track source offsets and disclose truncation and the next offset. Full exports belong outside model context. No numeric token savings are promised.

### Troubleshooting and FAQ

**Why did I request LTN but receive LGW?** The public timetable can substitute nearby airports. Inspect the requested and returned fields; use exact-airport filtering to exclude them.

**Why is the currency HUF rather than my preferred currency?** The source chooses the fare currency. The Actor does not perform conversion.

**Can I use a daily fare for every departure time?** No. Times describe available departures; the daily minimum is not a per-flight quote.

**Why are there fewer records than days?** Some days have no priced service, exact-airport filtering can remove substitutions, and your global cap can stop the search early.

**What happens when the source fails?** Transient network, 429 and 5xx failures receive at most three attempts per request. Other non-200 responses, malformed JSON or changed data shapes fail the run. Existing rows in a failed run are partial. No browser, proxy or paid fallback is silently enabled.

**Can I book tickets?** No. Verify fare, baggage, taxes and availability with Wizz Air before purchase.

### Legality and diagnostics

This unofficial Actor is not affiliated with Wizz Air. It retrieves public fare information only. Respect the source's terms and applicable laws; use reasonable scheduling intervals. No legal permission or booking guarantee is implied.

No AI model is used at runtime or to produce fare records. Wizz Air receives the requested route and date window; no passenger identities or booking credentials are collected. Apify hosts run input, datasets and logs under your account's storage retention settings. Delete run storage through Apify when no longer needed; the Actor keeps no separate history or persistent session cache.

Failed operations send sanitized diagnostic input, exceptions and Actor/build/run IDs to our private GlitchTip service for repair. Secret fields and URL query strings are removed; reports are retained for 30 days. GlitchTip is privately hosted in Germany; no AI training uses these reports. For Actor problems, contact us through the Apify Store issue/support interface with your run URL.

### Related Actors

For a different airline corpus, consider [Ryanair Flight Fares and Cheapest Routes](https://apify.com/automation-lab/ryanair-flight-fares-cheapest-routes). For fixed-date itinerary searches rather than airline daily calendars, see [Google Flights Scraper](https://apify.com/automation-lab/google-flights-scraper).

# Changelog

This Actor's version history is a separate document: https://apify.com/automation-lab/wizzair-fare-calendar/changelog.md

# Actor input Schema

## `departureIata` (type: `string`):

Requested departure IATA airport code. Trimmed and uppercased; use a real Wizz Air route. Returned airports can differ.

## `arrivalIata` (type: `string`):

Requested arrival IATA airport code, different from departure. Trimmed and uppercased. Nearby airport substitutions are preserved unless exactAirportsOnly is true.

## `dateFrom` (type: `string`):

Inclusive YYYY-MM-DD departure date, today or later (UTC). No historical fares. One adult, regular non-member fare only.

## `dateTo` (type: `string`):

Inclusive YYYY-MM-DD departure date, not before dateFrom. At most 366 days per search and 550 days ahead; upstream schedules can cover fewer days.

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

Global run cap on accepted, deduplicated daily route fares after exact-airport filtering. Default 100, range 1–366; no unlimited or zero mode. Chronological results; reaching the cap stops later windows.

## `exactAirportsOnly` (type: `boolean`):

False preserves upstream alternate-airport rows and flags the discrepancy. True excludes any row whose returned departure or arrival airport differs from the requested pair. Can reduce output to zero; never changes the returned airport labels.

## Actor input object example

```json
{
  "departureIata": "BUD",
  "arrivalIata": "LTN",
  "dateFrom": "2026-11-01",
  "dateTo": "2026-11-30",
  "maxItems": 20,
  "exactAirportsOnly": false
}
```

# Actor output Schema

## `dataset` (type: `string`):

Accepted daily fare records.

# 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 = {
    "departureIata": "BUD",
    "arrivalIata": "LTN",
    "dateFrom": "2026-11-01",
    "dateTo": "2026-11-30",
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("automation-lab/wizzair-fare-calendar").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 = {
    "departureIata": "BUD",
    "arrivalIata": "LTN",
    "dateFrom": "2026-11-01",
    "dateTo": "2026-11-30",
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("automation-lab/wizzair-fare-calendar").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 '{
  "departureIata": "BUD",
  "arrivalIata": "LTN",
  "dateFrom": "2026-11-01",
  "dateTo": "2026-11-30",
  "maxItems": 20
}' |
apify call automation-lab/wizzair-fare-calendar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,automation-lab/wizzair-fare-calendar"
        }
    }
}
```

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/UCwABtuDFpHisy3Dt/builds/SmoqFuyvOEu8lmu3Y/openapi.json