Use cases

ioki supports a range of MaaS integration use cases. They fall into two groups: improving the passenger user experience and optimizing operations. You can combine several use cases in one integration.

Passenger user experience

Use case	What it does
Journey planning (information)	Shows in your journey planner that an ioki DRT service exists for a requested trip, using a small amount of data such as stations and timestamps. Realized through a Universal link, the Ride inquiry endpoint, or the Platform API.
Journey planning and booking	Lets passengers plan and book an ioki ride from within your MaaS app, integrated via the Platform API.
Booking with live-position updates	After booking, shows the assigned vehicle’s live position and ride information in your app.
Vehicle monitor / timetable information	Presents departure and timetable-style information for a stop, comparable to a passenger information display.

Operations optimization

Use case	What it does
Planning exchange	Plan vehicles, drivers, and shifts in your own planning tools and exchange them automatically through the Platform API.
Vehicle information	Read vehicle details and current location (geodata) through the Platform API and Webhooks.
Raw data delivery	Receive raw operational data through the Platform API for your own reporting or BI tooling. Storing historical data and archiving on your side remain your responsibility.
Customer / call center system	Pre-fill your customer management or call center system with ride and user data.
On-board computer / ITCS integration	Integrate with on-board computers or an ITCS/RBL system through the Driver or Platform API.

The right combination depends on how much of the passenger flow you want to own in your app versus keep in the ioki Passenger App. See Integration options for how each is realized.