Integrations and API
On-demand software has to sit beside fare systems, identity, GTFS publishers and, sometimes, broker platforms. Integrations are project work, described honestly.
How the platform is used
A feed is not an integration. GTFS describes services that can be published. Live assignment still happens inside the operations system. National RTAP notes that static GTFS is what NTD currently requires for fixed route, including deviated fixed route. Microtransit reported as demand response follows a different reporting path.
maas.maker exposes operational APIs and can publish information feeds where they make sense. Payment, identity and AFC connections are scoped per project. This page does not claim a finished connector for every national fare card.
If a procurement asks for a named third-party system, we confirm the interface in the proposal rather than listing logos.
Integrations and API
On-demand software has to sit beside fare systems, identity, GTFS publishers and, sometimes, broker platforms. Integrations are project work, described honestly.
REST for partners
Create and update trips, vehicles and stops from a trusted partner system when the project defines it.
GTFS where it fits
Published stop and calendar information can be exported. Dynamic routing is not magically a perfect GTFS-RT feed.
Identity and payments
Single sign-on and payment providers are connected when the operator already has them. They are not bundled as surprise fees.
Scoped credentials
Partner keys are limited to the tenant and the objects they need.
How the platform is used
A feed is not an integration. GTFS describes services that can be published. Live assignment still happens inside the operations system. National RTAP notes that static GTFS is what NTD currently requires for fixed route, including deviated fixed route. Microtransit reported as demand response follows a different reporting path.
maas.maker exposes operational APIs and can publish information feeds where they make sense. Payment, identity and AFC connections are scoped per project. This page does not claim a finished connector for every national fare card.
Request a demoHow a tenant goes live
Scope
We walk through service type, fleet, booking channels and the reports you already have to file.
Configure
Branding, stops, hours, vehicle classes and assignment rules land in one tenant.
Train
Dispatchers, drivers and coordinators practise on the live board before opening hours.
Go live
The first operating weeks are coached. Exceptions, not the happy path, are the real product.
Modules you can combine. One tenant.
Start with booking, dispatch and the driver app. Add passenger apps, pooling rules, feeds and exports when the service needs them.
Explore the modulesA configured walkthrough, not a marketing video only. We look at your service type and fleet.
Questions teams ask
White-label software for booking, dispatching and reporting demand-responsive transport. It is not a consumer ride-hail brand.
No. Customers run the service with their own fleet or contracted carriers.
USD is the list-price base. You can switch the calculator to Australian dollars, New Zealand dollars or euro. Final contract currency is confirmed in a proposal.
Yes. Book a conversation and we walk through a configured tenant for your service type.
Plan a working demo
Share fleet size, service type and the outcome you need. We reply with a working demo path, not a generic brochure.