Ryanair Fare Finder

What does Ryanair Fare Finder do?

Ryanair Fare Finder finds direct Ryanair fares by city, compares nearby dates, and returns a monthly fare signal for each option. It is a focused Ryanair fare API alternative for low-cost flight monitoring; it does not compare all airlines, OTAs, or connecting itineraries.

The actor resolves Ryanair city dropdowns into route airports, checks the monthly fare calendar, and outputs structured fare rows with departure times, price per passenger, total price, monthly benchmark, dealSignal, and booking link. If no fare is found, it still returns a No matching fare row explaining why.

Why use Ryanair Fare Finder?

Use this actor when you need a fast way to monitor Ryanair fare opportunities without searching the Ryanair website manually for every date.

• Search by Ryanair city instead of airport code.
• Use dropdowns for active Ryanair cities.
• Find direct Ryanair routes between selected cities.
• Compare fares around a preferred date with dateFlexibilityDays.
• Return one-way or return-trip fare combinations.
• Calculate pricePerPassenger and totalPrice.
• Benchmark each fare against the same route and month.
• Get a simple buy, wait, avoid, or no_result signal.
• Use Apify scheduling, API access, dataset exports, webhooks, and integrations.

This actor is narrower than Skyscanner or Google Flights. Broad flight-search APIs often require paid credits, partner approval, or API keys. Ryanair Fare Finder focuses on one airline source and turns fare-calendar data into a useful monitoring dataset.

Use cases and target users

• Flight deal newsletters - find cheap Ryanair dates for selected city pairs.
• Travel planners - compare nearby dates before choosing a weekend trip.
• Travel dashboards - schedule route checks and append results to a long-lived dataset.
• Budget travel agencies - monitor low-cost route opportunities for clients.
• Developers and analysts - use the Apify API to feed fare data into sheets, alerts, or BI tools.

What data can Ryanair Fare Finder extract?

Field	Type	Description
fareStatus	string	Fare found or No matching fare
tripType	string	one_way or return
originCity, destinationCity	string	Resolved search cities
outboundDepartureAirport, outboundArrivalAirport	string/null	Route airport codes, for example LIS to STN
outboundDepartureDate, outboundDepartureTime	string/null	Outbound local date and time
returnDepartureDate, returnDepartureTime	string/null	Return date and time for return trips
passengers	number	Adult passengers used for total price
pricePerPassenger, totalPrice	number/null	Fare-calendar price before optional extras
outboundMonthlyLowestPrice, outboundMonthlyMedianPrice	number/null	Route/month benchmark values
benchmarkPrice, priceVsBenchmarkPercent	number/null	Monthly median comparison
dealSignal, dealReason	string	Fare recommendation and explanation
bookingUrl	string/null	Ryanair booking page URL when a fare is found

Run-level diagnostics such as routes checked, calendars checked, and lookup status are stored in RUN_SUMMARY.

How to scrape Ryanair fares

1. Open the actor on Apify.
2. Select originCity and destinationCity from the Ryanair city dropdowns.
3. Choose departureDate.
4. Leave returnDate blank for one-way fares, or add it for return trips.
5. Set passengers, currency, dateFlexibilityDays, and maxResults.
6. Click Start.
7. Download results as JSON, CSV, Excel, HTML, XML, or RSS.
8. For repeated checks, schedule the actor or append rows to your own dataset with datasetId.

The dropdowns include active Ryanair cities, but Apify does not support dependent dropdowns. The destination list cannot automatically hide cities that are not reachable from the selected origin. The actor validates the direct route during the run.

Cost expectations

This actor uses lightweight HTTP requests rather than browser automation. A simple one-way route check normally needs one airport list request, one route list request, and one fare-calendar request.

In a cloud validation run for Lisbon, Portugal to London, United Kingdom, the actor returned 5 rows in about 3 seconds and Apify reported roughly $0.001 of usage. Larger flexibility windows, return trips, or cities with multiple airport matches can use more requests.

Input

{
  "originCity": "Lisbon, Portugal",
  "destinationCity": "London, United Kingdom",
  "departureDate": "2026-09-12",
  "returnDate": "",
  "passengers": 1,
  "dateFlexibilityDays": 1,
  "currency": "EUR",
  "maxResults": 2
}

Key fields:

• originCity, destinationCity - Ryanair cities from the dropdown.
• departureDate, returnDate - outbound and optional return dates in YYYY-MM-DD.
• passengers - adult passengers used to calculate totalPrice.
• dateFlexibilityDays - days before and after the selected dates to compare.
• currency - requested fare currency.
• maxResults - maximum rows returned after sorting.
• datasetId, runId - optional workflow fields.

Output

Example fare row:

{
  "fareStatus": "Fare found",
  "tripType": "one_way",
  "originCity": "Lisbon",
  "destinationCity": "London",
  "outboundDepartureAirport": "LIS",
  "outboundArrivalAirport": "STN",
  "outboundDepartureDate": "2026-09-10",
  "outboundDepartureTime": "20:55",
  "passengers": 1,
  "pricePerPassenger": 38.99,
  "totalPrice": 38.99,
  "currency": "EUR",
  "outboundMonthlyLowestPrice": 32.99,
  "outboundMonthlyMedianPrice": 52.17,
  "benchmarkPrice": 52.17,
  "priceVsBenchmarkPercent": -25.3,
  "dealSignal": "buy",
  "dealReason": "Fare is at least 10% below the monthly median for this route.",
  "bookingUrl": "https://www.ryanair.com/gb/en/trip/flights/select?..."
}

Example no-results row:

{
  "fareStatus": "No matching fare",
  "tripType": "return",
  "originCity": "Skiathos, Greece",
  "destinationCity": "Faro, Portugal",
  "outboundDepartureDate": "2026-06-30",
  "returnDepartureDate": "2026-07-24",
  "pricePerPassenger": null,
  "totalPrice": null,
  "benchmarkPrice": null,
  "dealSignal": "no_result",
  "bookingUrl": null
}

API access

curl "https://api.apify.com/v2/acts/trovevault~ryanair-fare-finder/runs" \
  -X POST \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -d '{
    "originCity": "Lisbon, Portugal",
    "destinationCity": "London, United Kingdom",
    "departureDate": "2026-09-12",
    "returnDate": "",
    "passengers": 1,
    "dateFlexibilityDays": 1,
    "currency": "EUR",
    "maxResults": 2
  }'

Fetch results:

curl "https://api.apify.com/v2/datasets/DATASET_ID/items?clean=true" \
  -H "Authorization: Bearer $APIFY_TOKEN"

You can also use schedules, webhooks, Make, Zapier, Google Sheets exports, or Apify-compatible MCP workflows.

Deal signal logic

• buy - fare is at least 10% below the monthly median, or close to the monthly low.
• wait - fare is near the monthly median.
• avoid - fare is at least 25% above the monthly median.
• no_result - no direct route or fare matched the selected date window.

This is a route-and-month benchmark, not a long-term historical average or a guarantee that the fare will rise or fall.

Troubleshooting and support

Why did my selected city pair return No matching fare?

Ryanair may not operate a direct route between the selected cities, or no fare may exist in the selected date window. Try a larger dateFlexibilityDays, a different month, or a nearby Ryanair city.

Are prices final checkout prices?

No. Prices are fare-calendar snapshots before baggage, priority boarding, seats, payment fees, and other optional extras.

Does it need my Ryanair login or API key?

No. The actor does not require a Ryanair account or user API key.

Is this legal to use?

The actor reads publicly reachable route and fare-calendar information. It does not extract private user data. Use it ethically, avoid excessive request volumes, and make sure your use complies with applicable laws and terms. If unsure, consult your lawyers.

Where can I get help?

Use the Issues tab on the Apify actor page. Include your input and run ID when reporting an empty, failed, or surprising run.

Limitations

• Covers direct Ryanair routes only.
• Does not compare all airlines, OTAs, or connecting flights.
• Fare-calendar prices may change after the run.
• Final checkout totals may differ after optional extras.
• If public Ryanair endpoints change, extraction may need maintenance.

Related actors

• Hotel Stay Price Comparison
• Ticketing Comparison, planned
• Broader Airline Flight Price Comparison, parked until a reliable multi-airline source is available

Changelog

• 0.1.0 - Initial Ryanair fare finder with city dropdowns, route discovery, flexible dates, monthly benchmarks, return trips, booking links, and no-results rows.