Overview
Mobaro connects to other systems in two ways. Built-in partner integrations link Mobaro to a specific partner product, such as a guest app or a ride-monitoring system, and you switch them on in Configuration › Integrations. For any other system, such as a CMMS, HR system or BI tool, you or your IT team build the connection on the Mobaro API, webhooks or the Power Automate connector.
This article shows what’s available and where each one is set up. Each integration has its own setup article.
At a glance |
|
Who can do this | Super Users, or a Role with Organization › Administrate |
Where | Configuration › Integrations; API and webhooks in Configuration › API |
Works on | Backend (web) to set up. Data then flows to RideOps, the Mobile app, Dashboards or the Public API, depending on the integration |
Availability | Integrations tab: all organizations. API and webhooks: enabled per organization — ask your CSM |
Built-in partner integrations
Partner | What it does | Set up |
Attractions.io | Sends queue times posted in RideOps, and when rides open or close, to your Attractions.io guest app. One-way, Mobaro to Attractions.io. | |
Safari AI | Mobaro fetches camera-counted dispatches and queue estimates from Safari AI every 5 minutes and shows them in RideOps widgets and Dashboards. | |
DMT RideGuard | RideGuard turns sensor anomalies into Mobaro Assignments on the mapped Location, for the User Group you choose. | |
Purematic | Connects your Purematic crowd and wait-time system to Mobaro, so Purematic can exchange ride data with Mobaro through the API. |
Each partner needs its own account or subscription with that partner, and the credentials come from them, not from Mobaro.
Open the Integrations tab
1. Open Configuration
In the Backend, go to Configuration and open the Integrations tab. Each partner has a card with a short description and a badge.
2. Check the badge
Enabled means the partner’s credentials are saved in Mobaro; Not enabled means they aren’t. The badge doesn’t check that data is actually flowing, so test each integration as its setup article describes.
3. Open a partner
Click a card to open that partner’s settings. Click Integrations at the top to return to the cards; the badges refresh.
Connect other systems
There’s no built-in connector for other products, such as Maximo or another CMMS, SAP, Power BI or a ticketing system. Connect them with one of these:
Option | Use it to | Learn more |
Mobaro API | Read, create and update Mobaro data from your own system or script, with an API key. | |
Webhooks | Have Mobaro push changes to Users, Locations, Results, Assignments, Notes, Downtimes, Dispatches and Queue times to your system as they happen. | |
Power Automate | Build flows without code, for example daily exports to Excel or SharePoint. Needs a Premium Power Automate license. | |
Park attendance | Send guest counts from your ticketing or gate system for Dashboards and the Operations Report. | |
Single sign-on | Let Users sign in with their company account. Mobaro connects your identity provider. |
API access and webhooks are switched on per organization by Mobaro. When they are, you see the API tab in Configuration. Every API key can read all of your organization’s data; the only restriction is Read-only. See Understanding API access scopes and limitations.
API keys created by integrations
DMT RideGuard and Purematic call the Mobaro API, so Mobaro creates a full-access API key for them when you connect: DMT Rideguard Integration Key (Do Not Delete) and Purematic Integration Key (Do Not Delete). If your organization has API access, you’ll see them under Configuration › API › API Keys, whether or not you use the API yourself.
🛑 Critical: Don’t delete these keys or make them Read-only. Deleting a key cuts the partner off straight away, and a Read-only key blocks everything the partner writes. Mobaro doesn’t warn you, so sensor findings or ride data can go missing unnoticed. To replace a key, reconnect the integration as its setup article describes.
Best practices
Connect one ride or Location first and check the result in Mobaro before rolling out.
Give every custom integration its own API key, named after it, and keep it Read-only unless it must write.
Keep a list of which integrations your organization uses, who owns each one, and which API key it uses.
Before deleting an API key, check its name and Created date against that list. See Creating and managing API keys.
Frequently asked questions
Our Maximo integration has stopped working. What should we check?
Maximo isn’t a built-in Mobaro integration; it connects through the Mobaro API. Ask the team that built it to check that its API key still exists and isn’t Read-only (401 or 403 errors), then contact Mobaro Support with examples.
Can we send wait times to a guest app that isn’t Attractions.io?
Yes, through the API or webhooks. Your app provider can read RideOps queue times with an API key, or you can push them with a Queue times webhook. Only Attractions.io has a built-in connector. See Using webhooks in Mobaro.
Can we connect Power BI to Mobaro?
Yes, through the Mobaro API, for example by pulling Results on a schedule. There’s no built-in Power BI connector. See Pulling Results via the API.
Where’s the documentation for the Mobaro connector in Power Automate?
It’s in Getting started with Mobaro’s Power Automate connector. Each connector action matches a Mobaro API operation, so the API documentation covers its fields.
A card says Not enabled, but we set it up. Why?
The badge shows Enabled only while the partner’s credentials are saved. If someone turned the integration off, or saving failed, enter the credentials again. Open the card to check.