Integration options

There are three ways to integrate an ioki DRT service into your MaaS or journey planner app. They differ in how much of the passenger flow runs in your app and how much stays in the ioki Passenger App.

The journey planner informs the passenger that an ioki DRT service exists and deep-links into the ioki Passenger App to continue.

  • You maintain the core data needed to plan in your app: the geodata of the service area, the stops and virtual stops in the service area, and the service times.
  • When a matching trip is found, your journey planner shows that a DRT service exists and offers a redirection into the ioki Passenger App. If the user has not installed the app yet, they are redirected to the app store.
  • Trip data—origin, destination, and requested date and time—is pre-filled in the ioki Passenger App. The link also works the other way around.

Booking and payment happen in the ioki Passenger App. For the deep-link URL scheme and the parameters you can prefill, see Deep links.

Option 2: Ride inquiry endpoint

A lightweight, fast query to check availability and get an estimate, without a registered user.

  • Only a small amount of data (latitude and longitude) is needed for the query.
  • The query can be made without a registered user or a login.
  • ioki returns the geodata of the service area, the stops and virtual stops, the journey length, the service times, and a pricing estimation.
  • Planning of the whole trip (the travel chain) takes place in your journey planner.

Booking and payment happen in the ioki Passenger App.

See Ride inquiry for the endpoint details.

Option 3: Platform API (full integration)

Journey planning, booking, and payment all happen in your MaaS app, integrated through the Platform API.

  • Your app creates the user, requests and books the ride, and handles payment through your own payment service provider.
  • ioki reports offers, prices, and ride updates back to your app, and can push updates through Webhooks.

See the Journey planning flow for the end-to-end sequence and Ride creation flow for the concrete Platform API calls.

Choose Universal link when you only want to surface that a service exists and hand off to the ioki app. Choose Ride inquiry when you want availability and estimates in your own planner but keep booking in the ioki app. Choose the Platform API when you want the full booking and payment experience inside your own app.