Scope: 1.1 MaaS distribution API survey This document describes the execution and results of a survey into distribution APIs for MaaS. API owners have been encouraged to participate if they offer APIs that support the functions or if they were expecting to do so within a reasonable timeframe. Although there seems to be good coverage of European examples, survey responses cannot be treated as representative of the complete worldwide set of APIs, but provide strong indications of the totality of what exists, and the issues raised in terms of standardization and regulation. The survey has been carried out without any pre-determined agenda in terms of API policy or strategy. It has not been assumed a priori that a single API set could or should meet all multi-modal business needs. Comments are provided in respect of the impacts in standardization, but it was not considered appropriate to make any comments on regulatory implications, as this is not the area of competence for the CEN working group. 1.2 Transport distribution functions Distribution APIs may be related to one or to a combination of the functionality/ies1 (processes) described in Table 1. Table 1 — Functionalities Functionalities based on the MaaS Alliance White paper and Transmodel/NeTEx Functionalities described in the survey User registration: registration of detailed information related to the travelling entity (user, group of passengers, etc) such as payment cards, specific needs and preferences, data consent, etc. Management of customer accounts including for example customer preferences, data and entitlements, the products used, and journeys made Trip planning: provision of particular trip options taking into account parameters provided by the user (eg, location, time, budget and other preferences) Passenger trip itinerary for a single transport operator or multiple transport operators Personalisation of itineraries based on individual travel needs and preferences, data and entitlements Personalisation of it