FlixBus

FlixBus is the long-distance coach brand of Flix SE (formerly FlixMobility), a Munich-headquartered mobility provider that also operates FlixTrain in Europe and Greyhound in North America. Flix runs an asset-light model: it owns the brand, network planning, pricing, distribution and technology while regional bus partners operate the vehicles. Its technology surface is split in two. A partner-facing Flix API is published through the Flix Developer Portal at developer.api.flixbus.com — a Redocly-based catalogue of API references, getting-started guides, changelogs and downloadable Postman collections — but the portal is gated behind Microsoft Entra ID (Azure AD) sign-in and the underlying gateway at global.api.flixbus.com rejects anonymous requests, so no machine-readable OpenAPI is reachable without a distribution-partner agreement (requested via online-distribution@flixbus.com). Publicly and anonymously, Flix does publish schedule data as first-party GTFS Schedule feeds for Europe, the United States and Great Britain from gtfs.gis.flix.tech, refreshed regularly and licensed ODbL-1.0 through national open-data portals.

FlixBus is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Transportation, Travel, Mobility, and Bus.

FlixBus’ developer surface includes authentication, documentation, signup flow, support, engineering blog, and 14 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

23.7/100 emerging ▬ flat Agent 14/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0

AccessSelf serve

2 APIs

Company Transportation Travel Mobility Bus Rail Ticketing GTFS Open Data Distribution

Kin Score

Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0

Composite quality — 23.7/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 3.2 / 17

Access Clarity 5.8 / 17

Operational Transparency 1.5 / 11

Contract Governance 1.9 / 10

Discoverability 5.6 / 9

Regulatory Posture 4.6 / 15

Agent readiness — 14/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 4 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Government & Public Sector regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/flixbus: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Transit and Mobility (public transit, rail, micromobility)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

GTFS

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Flix API

The partner-facing Flix API, published through the Flix Developer Portal. Documentation covers API references, getting-started guides, changelogs and example Postman collections...

Flix GTFS Schedule Feeds

First-party GTFS Schedule feeds published by FlixMobility Tech GmbH covering the FlixBus and FlixTrain networks. Three anonymous, unauthenticated regional archives are served fr...

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Flixbus Authentication

oauth2 · 1 scheme

SECURITY

Flixbus Domain Security

TLSv1.3 · DMARC

SECURITY

Flixbus Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Lifecycle

Lifecycle

Build 2

SDKs, sample code, and the tooling you integrate with

Packages

Packages

GitHubOrganization

GitHubOrganization

Access & Security 5

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

SecurityTxt

SecurityTxt

Authentication

Authentication

Security

Security

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: flixbus
name: FlixBus
description: 'FlixBus is the long-distance coach brand of Flix SE (formerly FlixMobility), a Munich-headquartered mobility
  provider that also operates FlixTrain in Europe and Greyhound in North America. Flix runs an asset-light model: it owns
  the brand, network planning, pricing, distribution and technology while regional bus partners operate the vehicles. Its
  technology surface is split in two. A partner-facing Flix API is published through the Flix Developer Portal at developer.api.flixbus.com
  — a Redocly-based catalogue of API references, getting-started guides, changelogs and downloadable Postman collections —
  but the portal is gated behind Microsoft Entra ID (Azure AD) sign-in and the underlying gateway at global.api.flixbus.com
  rejects anonymous requests, so no machine-readable OpenAPI is reachable without a distribution-partner agreement (requested
  via online-distribution@flixbus.com). Publicly and anonymously, Flix does publish schedule data as first-party GTFS Schedule
  feeds for Europe, the United States and Great Britain from gtfs.gis.flix.tech, refreshed regularly and licensed ODbL-1.0
  through national open-data portals.'
url: https://raw.githubusercontent.com/api-evangelist/flixbus/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-02'
  method: derived
image: https://cdn-cf.cms.flixbus.com/drupal-assets/ogimage/flixbus.png
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-08-04'
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 10
  pass: local-v1
tags:
- Company
- Transportation
- Travel
- Mobility
- Bus
- Rail
- Ticketing
- GTFS
- Open Data
- Distribution
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Flix API
  description: 'The partner-facing Flix API, published through the Flix Developer Portal. Documentation covers API references,
    getting-started guides, changelogs and example Postman collections for Flix distribution and affiliate partners (search,
    availability, booking and ticketing over JSON/REST). Access is gated: the developer portal requires a Microsoft Entra
    ID sign-in and the API gateway at global.api.flixbus.com returns 403/401 to anonymous callers, so credentials are issued
    only under a distribution-partner agreement.'
  humanURL: https://developer.api.flixbus.com/
  baseURL: https://global.api.flixbus.com
  tags:
  - Booking
  - Ticketing
  - Travel
  - Distribution
  properties:
  - type: DeveloperPortal
    url: https://developer.api.flixbus.com/
  - type: Documentation
    url: https://developer.api.flixbus.com/
  - type: SignUp
    url: https://global.flixbus.com/company/partners/affiliate-partners
- name: Flix GTFS Schedule Feeds
  description: First-party GTFS Schedule feeds published by FlixMobility Tech GmbH covering the FlixBus and FlixTrain networks.
    Three anonymous, unauthenticated regional archives are served from gtfs.gis.flix.tech — Europe (gtfs_generic_eu.zip),
    the United States (gtfs_generic_us.zip) and Great Britain (gtfs_generic_gb.zip) — each a standard GTFS bundle with agency,
    routes, trips, stops, stop_times, calendar, transfers and shapes. The feeds are aggregated by Transitland, the Mobility
    Database and transport.data.gouv.fr under an ODbL-1.0 license.
  humanURL: https://www.transit.land/feeds/f-u-flixbus
  baseURL: https://gtfs.gis.flix.tech
  tags:
  - GTFS
  - Open Data
  - Schedule
  - Transit
  tags_raw:
  - GTFS
  - Open Data
  - Schedules
  - Transit
  properties:
  - type: GTFS
    name: GTFS Schedule — Europe
    url: https://gtfs.gis.flix.tech/gtfs_generic_eu.zip
  - type: GTFS
    name: GTFS Schedule — United States
    url: https://gtfs.gis.flix.tech/gtfs_generic_us.zip
  - type: GTFS
    name: GTFS Schedule — Great Britain
    url: https://gtfs.gis.flix.tech/gtfs_generic_gb.zip
common:
- type: DomainSecurity
  url: security/flixbus-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/flixbus-vulnerability-disclosure.yml
- type: SecurityTxt
  url: well-known/flixbus-security.txt
- type: WellKnown
  url: well-known/flixbus-well-known.yml
- type: Authentication
  url: authentication/flixbus-authentication.yml
- type: Conformance
  url: conformance/flixbus-conformance.yml
- type: Lifecycle
  url: lifecycle/flixbus-lifecycle.yml
- type: Packages
  url: packages/flixbus-packages.yml
- type: LLMsTxt
  url: llms/flixbus-llms.txt
- type: Website
  url: https://global.flixbus.com/
- type: DeveloperPortal
  url: https://developer.api.flixbus.com/
- type: Documentation
  url: https://developer.api.flixbus.com/
- type: SignUp
  url: https://global.flixbus.com/company/partners/affiliate-partners
- type: Support
  url: https://help.flixbus.com/
- type: Blog
  url: https://corporate.flix.com/newsroom/
- type: GitHubOrganization
  url: https://github.com/flix-tech
- type: TermsOfService
  url: https://global.flixbus.com/terms-and-conditions
- type: PrivacyPolicy
  url: https://global.flixbus.com/privacy-policy
- type: Security
  url: https://global.flixbus.com/responsible-disclosure

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/flixbus"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/flixbus/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/flixbus/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.