MaaS integration
This guide is written from the perspective of an external integrator. On this page, you means a non-ioki partner integrating an ioki demand-responsive transport (DRT) service into a Mobility as a Service (MaaS) or journey planner app.
A MaaS integration surfaces an ioki DRT service inside your own MaaS or journey planner app, so that your users can discover, plan, and—depending on the integration option you choose—book and pay for an ioki ride without leaving your app.
ioki offers several building blocks for this, from a lightweight deep link into the ioki Passenger App up to a full integration through the Platform API. The development effort for the integration sits on your side; ioki provides the APIs, webhooks, and configuration.
In this section
- Use cases. What you can build on top of ioki, for both passenger experience and operations.
- Integration options. The three ways to connect: Universal link, Ride inquiry, and full Platform API.
- Journey planning flow. The end-to-end registration, booking, payment, and live-position flow.
- Architecture and technical integration. How the systems connect and the technical basics of the interface.