Open Schedules Data.
One source for the industry.
One canonical schedule corpus — airlines file SSIM directly, the rest of the industry gets a free, normalized API.
Free API · airline-filed data. The hub is hosted by the community so the data stays singular — no fragmented forks, no contradictory feeds.
Community-hostedWhy one source
Schedule data only works if the whole industry trusts the same version of it. That's why Open Schedules Data isn't a fork-it-yourself project — it's a community-hosted hub. Airlines file once, at the source. Everyone reads the same normalized output. No drift. No reconciliation calls.
The code is open for inspection and contribution; the canonical instance is run for the community by the community.
Airlines file directly
Sign in with your airline domain. Upload SSIM. We validate, diff against last published, and store with full audit history.
Free for everyone
The output API is free to consume. Effective-from semantics, diff history, normalized JSON. No vendor login, no per-call fees.
Transparent ingest
Every transformation is auditable, diffable, and version-controlled. See exactly what was applied to your schedule, by whom, and when.
Community catalog
A shared library of transformations — code-share rollups, equipment fallbacks, slot translations — contributed by airlines.
Built on the Order Database
Sub-millisecond schedule lookups, append-only revision history, and a familiar query surface — out of the box.
NDC / Order shaped
Aligned with the offer and order shapes used in modern airline retailing. Ready for offer-time consumption, not just network planning.
File your SSIM directly.
Skip the middleware.
The SSIM upload portal is being built so airlines own the source of truth for their own schedule. We provide the rails — you stay in control. Filing takes minutes; the file shape is exactly what you already produce.
Network planners, schedule analysts, OAG wranglers — if any part of this looks like the spreadsheet you're maintaining, we'd love your feedback before we ship.
Updates when the SSIM portal opens, and when transformations land.
One email per shipping milestone. Nothing else.