OSDM is the International Union of Railways’ open standard for rail sales and distribution — the offer, booking, fulfilment and after-sales interface that lets any retailer sell any operator’s rail journey without a bilateral integration. It is published as OpenAPI, openly licensed, and is the rail sector’s structural counterpart to what NDC attempts in air.
UIC OSDM
OSDM is what NDC would look like if it had been designed as an open API from the start. Published by the International Union of Railways (UIC), it defines the full rail retail lifecycle — offer, booking, fulfilment, after-sales — as an OpenAPI specification under an open licence, so a retailer can integrate once and sell across operators rather than negotiating a connection per railway.
- OpenAPI, not XML messaging - the specification ships as a machine-readable OpenAPI contract, which is the single largest practical difference from NDC.
- Covers after-sales, not just search - exchange, refund and fulfilment are in scope, which is where rail distribution historically breaks between operators.
- Openly licensed and openly published - no accreditation gate, no certification tier, no commercial agreement required to read it.
- European in origin, structural in ambition - built to make cross-border rail sellable the way air already is, without reproducing air’s intermediation layer.
What the evidence shows
The State of Canadian Travel APIs names OSDM by its absence, and the detail is the point. VIA Rail never references OSDM anywhere — and its booking front end, built on the Sqills S3 Passenger platform, reads a UIC station code on every segment. The vocabulary is already in the system. The standard that would make it interoperable outward is not cited.
What VIA Rail does publish is GTFS Schedule with the ticketing extension under an open government licence — genuinely open, and scoped to informing a traveller rather than selling to them. That split runs through the whole travel quartet: open standards in this sector describe journeys, and proprietary interfaces sell them.
Set against the air side, OSDM is the useful counterfactual. NDC is XML, certified in tiers, gated
behind accreditation and commercial agreement, and introduces a platform-minted OrderID that moved
the primary booking key from the portable column to the vendor column. OSDM is OpenAPI, openly
licensed, and requires nothing to read. Two sectors facing the same distribution problem chose
opposite architectures, and only one of them is reachable by an agent.
Referenced in API Evangelist papers
This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.
The State of Canadian Travel APIs
The rail analogue to NDC — never referenced by VIA Rail, even though its booking front end reads UIC station codes on every segment.
