# FlixBus

> FlixBus is the long-distance coach brand of Flix SE (formerly FlixMobility), a Munich-headquartered mobility provider that also runs FlixTrain in Europe and Greyhound in North America. Flix owns the brand, network planning, pricing, distribution and technology while regional bus partners operate the vehicles. Its partner-facing Flix API is documented on the Flix Developer Portal but gated behind a Microsoft Entra ID sign-in; its schedule data is published openly as first-party GTFS Schedule feeds.

This file was generated by API Evangelist from publicly reachable material. Flix does not
publish an llms.txt of its own — https://developer.api.flixbus.com/llms.txt returns the
portal's HTML shell, not a document.

## APIs

- [Flix API](https://developer.api.flixbus.com/): Partner-facing REST/JSON API for search, availability, booking and ticketing. Base URL https://global.api.flixbus.com. Access requires a distribution-partner agreement — the developer portal requires a Microsoft Entra ID sign-in and the gateway returns 401/403 to anonymous callers. No OpenAPI is publicly reachable.
- [Flix GTFS Schedule Feeds](https://www.transit.land/feeds/f-u-flixbus): Open, unauthenticated GTFS Schedule archives for the FlixBus and FlixTrain networks, published by FlixMobility Tech GmbH under ODbL-1.0.

## Specs and data

- [GTFS Schedule — Europe](https://gtfs.gis.flix.tech/gtfs_generic_eu.zip)
- [GTFS Schedule — United States](https://gtfs.gis.flix.tech/gtfs_generic_us.zip)
- [GTFS Schedule — Great Britain](https://gtfs.gis.flix.tech/gtfs_generic_gb.zip)
- [GTFS specification](https://gtfs.org/): the open standard these feeds implement

## Docs

- [Flix Developer Portal](https://developer.api.flixbus.com/): API references, getting-started guides, per-API changelogs and example Postman collections (sign-in required)
- [Partner programs](https://global.flixbus.com/company/partners)
- [Affiliate and distribution partners](https://global.flixbus.com/company/partners/affiliate-partners): static integration via AWIN; dynamic integration (API, GTFS, white label, metasearch) by emailing online-distribution@flixbus.com
- [Help centre](https://help.flixbus.com/)

## Security

- [Responsible disclosure policy](https://global.flixbus.com/responsible-disclosure)
- [security.txt](https://global.flixbus.com/.well-known/security.txt): contact responsible-disclosure@flixbus.com; no bug bounty offered

## Company

- [FlixBus](https://global.flixbus.com/)
- [Flix corporate](https://corporate.flix.com/)
- [Newsroom](https://corporate.flix.com/newsroom/)
- [FlixTrain](https://www.flixtrain.com/)
- [GitHub — flix-tech](https://github.com/flix-tech): Flix engineering org; infrastructure and open-source forks, no API SDK
- [Terms and conditions](https://global.flixbus.com/terms-and-conditions)
- [Privacy policy](https://global.flixbus.com/privacy-policy)

## Notes for agents

- There is no public OpenAPI, AsyncAPI, GraphQL schema, MCP server or A2A agent card for Flix. All were probed on 2026-08-04 and missed.
- Flix publishes no first-party SDK on npm, PyPI, Packagist or RubyGems. Packages matching "flixbus" on those registries are community projects.
- The only anonymous machine-readable Flix contract is GTFS. Treat the three regional archives as the integration surface unless you hold partner credentials.