FlixBus API Scraper
Pricing
from $0.01 / trip search
FlixBus API Scraper
Search FlixBus trips between cities on a given date. Resolves human-friendly city names via the official mobile API autocomplete, then returns full trip details: departure/arrival times, stations, duration, prices, transfers, seat availability, amenities, and more.
FlixBus Trip Search API Scraper
Search FlixBus trips between two cities on a given date and get full trip details — no browser automation, just the official FlixBus API.
What it does
Give it an origin city, a destination city, and a departure date. The actor:
- Resolves each city name to a FlixBus city ID via the official autocomplete API.
- Searches trips between those cities on the given date.
- Returns one dataset record per trip, including:
- Departure/arrival times, cities, and stations
- Trip duration
- Prices (original, discounted, with platform fee)
- Seats available, bike slots, capacity level
- Direct vs. transfer, number of legs, per-leg detail (ride ID, times, operator, amenities)
- Amenities and operators across the whole trip
Input
| Field | Required | Description |
|---|---|---|
fromCity | yes | Origin city name, e.g. Berlin |
toCity | yes | Destination city name, e.g. Munich |
departureDate | yes | Departure date (date picker) |
adults | no | Number of adult passengers (default 1) |
locale | no | Locale for city resolution and results, e.g. en, de, fr (default en) |
currency | no | ISO 4217 currency code, e.g. EUR, USD (default EUR) |
proxyConfiguration | no | Apify Proxy settings, useful if you hit rate limits |
Example input:
Output
One row per trip in the default dataset. Key fields: departureDate,
arrivalDate, departureCityName, arrivalCityName, departureStationName,
arrivalStationName, durationHours, durationMinutes, priceTotal,
priceTotalWithFee, priceOriginal, seatsAvailable, legCount, legs,
amenities, operators, bikesAllowed.
See the Dataset tab / API for the full field list and export to JSON, CSV, Excel, etc.
Notes
- City names are resolved via FlixBus's own autocomplete, so common spellings in the chosen locale should work.
- If a city can't be resolved or the date is invalid, the run fails with a clear error message.
- Use
proxyConfigurationif you're running frequent searches and want to avoid rate limiting.
