FlixBus Scraper

Search FlixBus connections between any two European cities and get back structured trip data: prices, durations, transfer counts, operators, and booking links.

How it works

You provide a departure city and arrival city as plain text (e.g., "Brussels" and "Paris"). The actor resolves these against FlixBus's autocomplete API, then queries their search API for available trips on your chosen date. City names are fuzzy-matched, so "Brussel", "Brussels", or "Bruxelles" all work.

Sold-out trips are automatically filtered out. Only available connections are returned.

Input

Field	Type	Required	Description
fromCity	String	Yes	Departure city (e.g., "Brussels", "Berlin")
toCity	String	Yes	Arrival city (e.g., "Paris", "Amsterdam")
departureDate	String	No	Date in YYYY-MM-DD format. Defaults to tomorrow.
adults	Integer	No	Number of passengers (default: 1)
currency	String	No	ISO currency code (default: EUR)
locale	String	No	Language for results (default: en)
maxResults	Integer	No	Cap on number of trips returned (default: 50)
proxyConfiguration	Object	No	Proxy settings. The FlixBus API is public but may rate-limit heavy use.

Output fields

Field	Type	Example
departureCity	String	"Brussels"
arrivalCity	String	"Paris"
departureStation	String	"Brussels North station"
arrivalStation	String	"Paris Bercy Seine"
departureTime	String	"2026-04-10T07:30:00.000+02:00"
arrivalTime	String	"2026-04-10T11:45:00.000+02:00"
duration	String	"4h 15min"
durationMinutes	Number	255
price	Number	19.99
originalPrice	Number	24.99
currency	String	"EUR"
transfers	Number	0
operator	String	"FlixBus"
busType	String	"bus"
availableSeats	Number	23
amenities	Array	["wifi", "power_sockets"]
url	String	Booking link

Example output

{
    "departureCity": "Brussels",
    "arrivalCity": "Paris",
    "departureStation": "Brussels North station",
    "arrivalStation": "Paris Bercy Seine",
    "departureTime": "2026-04-10T07:30:00.000+02:00",
    "arrivalTime": "2026-04-10T11:45:00.000+02:00",
    "duration": "4h 15min",
    "durationMinutes": 255,
    "price": 19.99,
    "currency": "EUR",
    "transfers": 0,
    "operator": "FlixBus",
    "busType": "bus",
    "availableSeats": 23,
    "amenities": ["wifi", "power_sockets"],
    "url": "https://shop.flixbus.com/search?departureCity=...",
    "scrapedAt": "2026-04-09T14:30:00.000Z"
}

Cost

Lightweight API-based scraper. Around 0.005 compute units per run regardless of result count. Roughly $0.01 per search.

Good to know

• City name resolution is flexible but occasionally picks the wrong city for ambiguous names. If "Springfield" gives you the wrong one, try "Springfield, IL".
• Only future dates work. The API returns nothing for past dates.
• The departureDate input must be YYYY-MM-DD format. The actor converts it internally to the DD.MM.YYYY format FlixBus expects.
• FlixTrain connections also show up when available on the route.

Why use FlixBus Scraper

• Price monitoring — Track prices, stock, and promotions across FlixBus at scale
• Competitive intelligence — Compare your catalog against FlixBus pricing and assortment
• Market research — Analyze category trends, new arrivals, and rating distributions
• Lead generation — Build product datasets for affiliate sites, comparison tools, or feeds
• No login or cookies required — Authenticated access not needed; works out of the box

How to use FlixBus Scraper

1. Open the Input tab and provide a search query, category URL, or product list
2. Adjust optional filters such as maxResults or proxy settings
3. Click Start and wait for the run to complete
4. Download results from the Output tab in JSON, CSV, Excel, XML, or HTML
5. Schedule recurring runs from the Schedule tab if you need ongoing data

How to scrape FlixBus data

This Actor automates the process of extracting structured product data from FlixBus. You can run it directly from the Apify console, the Apify API, or any of the official SDKs (JavaScript, Python). The scraper handles pagination, retries, and rate limiting so you can focus on the data, not the plumbing.

Typical workflows:

• One-off export: paste a category URL or keyword, set maxResults, and run
• Scheduled monitoring: set a daily cron in the Schedule tab to track prices over time
• Programmatic integration: trigger runs from your backend via the Apify API and pull the dataset when finished
• Webhook automation: receive a callback the moment a run completes and pipe the results into Zapier, Make, n8n, BigQuery, or Google Sheets

Tips for best results

• Start small — run with maxResults: 10 before launching large jobs
• Use proxies — residential proxies reduce blocking on protected sites
• Throttle on big jobs — keep maxConcurrency modest (5–10) for stability
• Schedule runs — daily runs are usually enough for price monitoring
• Inspect the dataset schema — the Storage tab shows the full output structure

FAQ and support

Is it legal to scrape FlixBus? This Actor extracts publicly available data. Always review the website's Terms of Service before scraping at scale, and respect rate limits.

Why am I getting fewer results than expected? Some categories have hidden pagination or load more on scroll. Increase maxResults and verify your filters.

Can I extract data for a single product? Yes — provide the full product URL in startUrls and the scraper will return one item.

The site blocks me — what should I do? Enable Apify residential proxies in the input. Datacenter IPs are blocked by many e-commerce sites.

For issues, feature requests, or bug reports, open a ticket in the Issues tab on the Actor page or contact support@apify.com. We monitor every actor and ship fixes quickly when sites change.