FlixBus Connections Scraper avatar

FlixBus Connections Scraper

Pricing

from $0.50 / 1,000 search results

Go to Apify Store
FlixBus Connections Scraper

FlixBus Connections Scraper

Scrape bus connections from FlixBus with departure dates, prices, vacancy levels, and more.

Pricing

from $0.50 / 1,000 search results

Rating

5.0

(2)

Developer

Jindřich Bär

Jindřich Bär

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Flixbus connection scraper

Search bus connections via the Flixbus API and get back a structured dataset of routes, times, leg-by-leg breakdowns, and prices.

What it does

Given a departure city, a destination, and an optional date, the actor:

  1. Resolves the city names to Flixbus city IDs via the Flixbus autocomplete endpoint.
  2. Calls the Flixbus connection-search API for the requested date.
  3. Walks forward day by day until enough connections are collected or the day-scan cap is hit.

For each connection you get:

  • Departure and arrival as ISO 8601 timestamps with timezone offsets
  • Total travel time in minutes
  • Number of transfers
  • Per-leg breakdown: ride ID, from/to station + city, departure / arrival, operator, brand, amenities
  • Total price and price including the Flixbus platform fee, in the requested currency
  • Seat availability and whether bikes can be booked

Inputs

FieldRequiredDefaultDescription
fromyesDeparture city name (resolved via Flixbus autocomplete)
toyesDestination city name (resolved via Flixbus autocomplete)
datenotodayDeparture date (date picker, ISO YYYY-MM-DD)
adultsno1Number of adult passengers (affects the returned price)
currencynoEURISO 4217 currency code used to price the connections
localenoen_USLocale passed to the Flixbus API
onlyDirectConnectionsnofalseOnly return single-leg, no-transfer connections
maxResultsno20Maximum number of connections to push to the dataset

Example input

{
"from": "Prague",
"to": "Berlin",
"date": "2026-05-20",
"adults": 1,
"currency": "EUR",
"onlyDirectConnections": true,
"maxResults": 20
}

Output

Each item in the dataset describes one connection.

Example item

{
"id": "direct:93d81544-1986-4a6d-a112-162812c4ff17:9b6adf5b-3ecb-11ea-8017-02437075395e:dcbb994f-9603-11e6-9066-549f350fcb0c",
"from": "Prague ÚAN Florenc",
"to": "Berlin Südkreuz",
"fromCity": "Prague",
"toCity": "Berlin",
"departure": "2026-05-20T01:00:00+02:00",
"arrival": "2026-05-20T05:50:00+02:00",
"timeLengthMinutes": 290,
"changesCount": 0,
"transferType": "Direct",
"status": "available",
"provider": "flixbus",
"legs": [
{
"rideId": "93d81544-1986-4a6d-a112-162812c4ff17",
"from": "Prague ÚAN Florenc",
"to": "Berlin Südkreuz",
"fromCity": "Prague",
"toCity": "Berlin",
"departure": "2026-05-20T01:00:00+02:00",
"arrival": "2026-05-20T05:50:00+02:00",
"timeLengthMinutes": 290,
"meansOfTransport": "bus",
"operator": "FlixBus DACH GmbH",
"brand": "FlixBus",
"amenities": ["WIFI", "POWER_SOCKETS"]
}
],
"price": 22.49,
"priceWithPlatformFee": 26.48,
"currency": "EUR",
"seatsAvailable": 59,
"bikesAllowed": true
}

price is in the currency requested via the currency input; null means the price could not be retrieved. changesCount is 0 for direct, single-leg connections.

Pricing

The actor uses Apify pay-per-event pricing — one search-result event is charged for every connection pushed to the dataset.

Agentic use

The actor is built for use by AI agents:

  • Structured input schema. Every input has a title, type, description, and validation rules.
  • Structured output schema. Each dataset item has a stable, typed shape — agents can read fields like departure, price, or changesCount without parsing prose.
  • ISO timestamps. Departures and arrivals are emitted as ISO 8601 strings with the original timezone offset, ready to be diffed, sorted, or compared.
  • Numeric quantities. timeLengthMinutes, changesCount, price are numbers, not formatted strings — no parsing required.
  • Predictable output. Connections are returned in chronological order; duplicates are removed.
  • Event-level cost control. Pay-per-event billing means an agent that sets a small maxResults pays only for what it consumes.

Typical agent prompts that map cleanly onto this actor:

  • "Find the cheapest Flixbus from Prague to Berlin tomorrow."
  • "How long does the direct Flixbus from Berlin to Madrid take?"
  • "List all direct overnight Flixbus rides from London to Paris in the next two weeks."