Shotl API
Plays well with your mobility ecosystem
Connect Shotl services to MaaS apps, journey planners and BI — on secure, documented APIs.
{
"pickup": [41.49, 2.14],
"dropoff": "rail-hub-04",
"passengers": 2,
"wheelchair": false,
"requested_time": "now"
}
→ 201 Created
{
"booking_id": "bk_8f31",
"vehicle": "SHTL-07",
"eta_minutes": 6
}Illustrative request — full API documentation is shared during onboarding.
Already connected
Your service, bookable inside other apps
LINETainan riders book inside the messaging app they already use: no download, no accountRead the caseThrough the Shotl API, riders can book the same trips from a MaaS app or a messaging app they already use — with the same vehicles, rules and data behind them. In Tainan, that app is LINE.
- myBuxiSwitzerlandShotl services connected to myBuxi and its KIM mobility project.Read more →
- HiTransScottish HighlandsOn-demand trips booked alongside buses, trains and ferries across the region.Read the case →
Autonomous mobility
Autonomous vehicles, dispatched like the rest of your fleet
Autonomous shuttles connect to the platform through the same APIs as any other vehicle. Riders book them in the same app, and the control room sees them on the same dashboard.
- Custom APIs to the vehicle. Built to exchange information between Shotl’s platform and the autonomous bus.
- Fixed or on demand. A scheduled loop at peak times, with pickups on request when the loop empties.
- Under the pilot’s own brand. The rider app published as a white-label service.
Built into the API
Connect the service to everything around it
Journey planners, MaaS apps and your own systems connect through the same documented APIs.
- In every journey plannerGTFS integration puts the service next to the trains and trams in the planners riders already use.
- Inside the apps your region runsRiders can book from regional MaaS or messaging apps — in Tainan they book inside LINE.
- Read from your own systemsDrivers, vehicles, stops, zones and service plans can come from your APIs instead of being kept twice.
- Your data, outA query API exposes bookings, KPIs and real-time vehicle positions, and activity data is delivered to you.Operations Dashboard
- Fares and payments, built inCard payments into your own Stripe account, payment on board, and a price per fare type.Fares and payments
- Onboard units, if you have themCAN-bus or other onboard units can feed richer tracking. A driver phone or tablet is all that is required.
FAQ
The questions we hear most
Can riders book from an app that isn't ours?
Yes. In Tainan, Taiwan, riders book Shotl trips inside LINE — the messaging app they already use daily — with no separate download. The same approach works for regional MaaS apps and journey planners.
Is the API publicly documented?
Yes — versioned documentation with examples, so your team or vendor can scope an integration before talking to us.
Does Shotl publish GTFS?
Yes — GTFS in and out, including on-demand zones, plus live vehicle positions and service alerts.
How long does a MaaS integration take?
Around two weeks is typical for booking and tracking through a regional MaaS app.
How is access secured?
Role-based API keys, EU-hosted infrastructure and audit logs — answers your procurement team can copy-paste.
Can third-party fleets connect?
Yes — external and autonomous fleets dispatch through the same APIs as your own vehicles.
