Overview
CEN/TR 18362:2026 - Guidelines for Building Multimodal Travel Purchase APIs Based on Transmodel provides valuable guidance for creating interoperable APIs that support purchasing multimodal travel options. Developed by CEN/TC 278 as part of the CoRoM (Coordination & standardisation for Rail & Mobility) initiative, this technical report addresses the practical need for integrated digital solutions in Mobility-as-a-Service (MaaS) and supports the seamless purchase and reservation of journeys across various public transport modes, including long-distance rail.
Designed for developers, transport operators, platform providers, and standardisation bodies, this report builds directly on Transmodel (EN 12896), the reference data model for public transport information, ensuring compatibility and extensibility for future developments in European digital mobility services.
Key Topics
-
API Specification for Multimodal Travel Purchase
The guidelines detail the necessary data flows and interactions required for purchasing multimodal travel options, including after-sale support, from a traveller's perspective.
-
Transmodel-Based Data Structures
All conceptual and structural API elements are based exclusively on Transmodel concepts, ensuring that only standardised data models are applied.
-
Analysis of Existing APIs
The document provides a comparative study of leading European APIs such as OSDM, TOMP-API, BoB, Entur, FerryGateway, and TAP TSI. This analysis identifies commonalities, differences, and best practices relevant for cross-modal integration.
-
Functional Scope
The covered processes include:
- Fares catalog and consultation
- Request and retrieval of fare offers
- Pre-purchase offer selection
- Purchase initiation, commitment, and reservation
- Issuance of purchase evidence
- Basic after-sale management
- Interactions associated with persistent traveller identity
-
Exclusions
The guidelines specifically exclude journey or trip planning, payment processing interfaces, travel document issuance, access right validation/control, and user registration/functionality unrelated to purchase processes.
-
Terminology and Interoperability
Emphasizes the use of consistent, unambiguous terms, explicitly preferring "purchase" over "booking," due to varied interpretations among stakeholders. This is to harmonize the language and functional intent across the industry.
Applications
CEN/TR 18362:2026 delivers practical value by enabling:
-
Development of Standardized Purchase APIs
Transport operators and MaaS providers can design and expose purchase APIs that are interoperable across European markets, accelerating deployment and reducing integration costs.
-
Increased Traveller Convenience
Travellers benefit from easier access to unified, cross-modal travel options, including the ability to view, select, and commit to journeys involving multiple transport operators through a single interface.
-
Advance Multimodal Retailing
Aggregators and retailers can create seamless sales journeys, combining offers from multiple suppliers, managing reservations, and integrating diverse fare structures using standardized Transmodel-aligned APIs.
-
Future Regulations and Compliance
Positions stakeholders to comply with upcoming EU regulations on Multimodal Digital Mobility Services (MDMS) and supports the goals of the EU Green Deal by encouraging more sustainable travel options.
-
Foundation for Automated Handling
The structured approach paves the way for future automation of redress and trip-repair processes in cases of disruptions, by standardizing the recording and transfer of necessary travel purchase data.
Related Standards
For comprehensive integration and alignment in public transport information systems, consider these related standards:
-
Transmodel - EN 12896 Series
The foundational reference model for public transport data structures leveraged throughout this technical report.
-
NeTEx - CEN/TS 16614 Series
Covers network, timetable, and fare data exchange formats for public transport systems.
-
SIRI - EN/TS 15531 Series
Specifies interfaces for real-time information exchange.
-
Open API for Distributed Journey Planning (OJP) - CEN/TS 17118 Series
Standardized formats for distributed journey planning, complementary to purchase-focused APIs.
-
CEN/TR 00278582:2022
Overview of public transport distribution APIs for MaaS.
By following CEN/TR 18362:2026, organizations can future-proof their digital sales channels, foster API interoperability, and directly support a seamless, multimodal travel experience across Europe.