We’re thrilled to announce the launch of the ATOM Mobility OpenAPI V1 – a major step toward enabling mobility operators to seamlessly integrate their services with third-party platforms, partner systems, and custom applications.
With the OpenAPI, ATOM Mobility opens up new possibilities for businesses running vehicle-sharing, rental, and ride-hailing services to extend their digital reach, enhance customer experience, and unlock new revenue streams.

What is an OpenAPI and Why Does it Matter?
An OpenAPI (or application programming interface) is a set of standardized protocols that allows external software systems to interact with your platform. In simple terms, it acts like a bridge between your mobility service and the outside world — enabling secure data sharing and functional integration.
For mobility businesses, OpenAPIs have become a key tool for:
- Displaying fleet availability in Mobility-as-a-Service (MaaS) platforms
- Enabling ride or rental bookings directly from external platforms (websites, apps, kiosks)
- Automating back-office workflows and data pipelines
- Enhancing customer service tools with real-time ride information
What Makes ATOM Mobility’s OpenAPI Different?
While many mobility providers offer GBFS (General Bikeshare Feed Specification) to share read-only data (ATOM Mobility will continue supporting GBFS) – such as vehicle locations and availability – these feeds are typically limited to visibility. Users still need to switch to a provider’s app to complete the ride.
ATOM Mobility’s OpenAPI is different. It offers full read-write access to the core functions of your platform – similar to what operators can already do in the back-office dashboard. This means that third-party apps can not only display your vehicles but also handle booking, payments, and ride management entirely within their own interface.
This is a game-changer for expanding your service footprint beyond your app.
What’s Included in OpenAPI V1?
The first version of the OpenAPI supports all core modules — Vehicle sharing, Digital rental, and Ride-Hailing — with both public and private endpoints for:
- User registration and authentication
- Vehicle discovery and availability
- Zone rules, pricing, and ride logic
- Starting and ending rides or bookings
- Accessing ride history and user activity
- Enhanced actions: skip wallet checks, trigger some commands, bypass OTP, and more
Typical Use Cases
Here are some examples of how mobility operators are already planning to use the ATOM OpenAPI:
1. Deep MaaS Platform Integrations
Connect your fleet to fast-growing MaaS platforms, for example:
- umob – a Dutch mobility booking app that recently raised €3.5M to expand its “all-in-one” MaaS experience across Europe. With OpenAPI, your vehicles could be fully bookable and payable directly from their interface.
- Moovit – a mobility super-app used by over 1.7 billion riders in 3,500+ cities. Traditionally, Moovit displays vehicles using GBFS and redirects users to provider apps – with OpenAPI, the entire booking could happen inside Moovit.
- Jelbi (Berlin) – Germany’s flagship MaaS platform, integrating 12+ operators, including car-sharing, scooters, and public transport. A direct API integration offers visibility and usage on one of Europe’s most advanced multimodal networks.
2. Bookings Via Your Website
Allow users to book rentals or ride directly from your website without needing to download an app upfront. This is especially useful for tourists, first-time users or hotels. The app would only be needed to unlock the vehicle or track the driver (in case of ride-hailing).
3. B2B Partner Integrations
Want to offer mobility through hotels, offices, or real estate platforms? Now they can show your vehicles and complete bookings within their apps – driving high-value B2B usage without manual overhead.
4. Customer Support Automation
Support agents can pull up a rider’s active trip data in external helpdesk tools using ride ID endpoints – improving efficiency and resolution speed.
5. Custom Dashboards and Analytics
Build your own reporting layer by pulling real-time and historical ride, user, and revenue data into tools like Power BI, Tableau, or custom CRMs.
How to Enable the OpenAPI?
The OpenAPI is available to all ATOM clients on the Premium Plan, which includes:
- Access to full OpenAPI documentation and developer tools
- 100,000 API requests per month included in your support fee
- Technical assistance from the ATOM team for setup and testing
Ready to Expand Your Mobility Ecosystem?
Whether you’re exploring new channels, seeking B2B integrations, or joining a MaaS platform, the ATOM OpenAPI gives you the tools to scale faster and smarter.
This article was originally published by ATOM Mobility.