Overview
Purematic provides crowd and wait-time systems for parks. The Purematic integration connects your Purematic account to your Mobaro organization, so Purematic’s system can exchange ride data with Mobaro, such as wait times and dispatches, without anyone typing it into two systems.
You connect the two in a few minutes: generate an AIS auth token in Purematic, paste it into Mobaro, then choose in Purematic which of its areas belong to which Mobaro Location. Mobaro doesn’t need anything else from you.
At a glance |
|
Who can do this | Super Users, or a Role with Organization › Administrate |
Where | Configuration › Integrations › Purematic; area mapping in Purematic |
Works on | Backend (web) to set up. Purematic then connects through the Mobaro API |
Availability | All organizations with a Purematic account |
How the Purematic integration works
When | What happens |
You save an AIS auth token | Mobaro creates an API key named Purematic Integration Key (Do Not Delete) with full (not read-only) access and sends it to Purematic. The token itself is used once and isn’t stored in Mobaro. |
You map areas in Purematic | Purematic knows which Mobaro Location each of its areas belongs to. |
Purematic sends or reads data | Purematic calls the Mobaro API with that key. Which data it exchanges is set up on the Purematic side. |
You turn it off, then connect again with a new token | Turning it off deletes the old key. Connecting again creates a new key and sends it to Purematic. |
You turn the integration off | Mobaro deletes the key, so Purematic can no longer connect. |
When Purematic sends dispatches or queue times, Mobaro stores them as external RideOps data from Purematic, alongside what Operators enter in RideOps rather than replacing it. See RideOps dashboard widgets for reporting on external data.
🛑 Critical: Don’t delete the Purematic Integration Key (Do Not Delete) API key or tick Read-only on it. Purematic uses it for every request; without it, nothing reaches Mobaro from Purematic, and Mobaro doesn’t warn you. If it happens, connect again with a new token (see Change or renew the connection).
Before you start
A Purematic account that can open Integration in Purematic’s menu. Mobaro doesn’t create Purematic accounts.
A Mobaro Location for each ride or area you want to connect.
The Mobaro API add-on isn’t needed: Mobaro creates the key for Purematic itself.
Connect Purematic to Mobaro
1. Open the Purematic card
In the Backend, go to Configuration and open the Integrations tab. Click the Purematic card; it shows Not enabled until you connect.
2. Turn the integration on
Tick Enable Purematic integration. The AIS auth token field appears, with the guide Show me how to get an AIS auth token.
3. Generate the token in Purematic
In a new tab, open Purematic at pureais.purematic.de (the guide links to it as Open Purematic), then:
Log in.
Open the menu top left.
Open Integration.
Select Mobaro.
Click the refresh icon to generate the AIS auth token.
Click the copy icon to copy the token.
4. Paste the token and save
Back in Mobaro, paste the token into AIS auth token and click Save (the disk icon at the top of the Purematic panel). Mobaro sends the new API key to Purematic straight away. When it works, you’ll see Purematic settings saved successfully, the field is locked and masked, and the card shows Enabled.
5. Map Purematic areas to Mobaro Locations
Open the guide Show me how to map locations in Purematic. In Purematic, log in, open the menu top left, open Integration, select Mobaro and Assign Purematic areas to Mobaro locations. Mapping is done in Purematic only; there’s nothing to map in Mobaro.
If saving fails
If Purematic doesn’t accept the request, Mobaro shows the reason and keeps nothing: no key is created and the card stays Not enabled.
Message | What to do |
The AIS auth token was rejected by Purematic. | Generate a new token in Purematic and paste it again. |
Could not reach Purematic., Purematic timed out., Purematic is unavailable. or Purematic rate-limited the request. | Wait a few minutes and save again. |
Purematic could not find the partner API., Purematic rejected the request (with a status code) or Could not save Purematic settings | Contact Mobaro Support with the message. |
Change or renew the connection
Once connected, the AIS auth token field is locked. To connect with a new token, for example after the key was deleted by mistake:
Untick Enable Purematic integration and click Save. This disconnects Purematic and deletes its key.
Tick Enable Purematic integration again.
Generate a new token in Purematic, paste it and click Save.
Your area mapping lives in Purematic, so check it there afterwards.
Turn the integration off
Untick Enable Purematic integration and click Save. Mobaro deletes the Purematic Integration Key (Do Not Delete) key, so Purematic’s requests stop working immediately. Data Purematic already sent stays in Mobaro. To stop only one ride or area, remove its mapping in Purematic instead.
Best practices
Generate the token right before you paste it, and don’t store or share it.
Map one ride first, check that its data appears in Mobaro, then map the rest.
Tell everyone who manages API keys that the Purematic Integration Key (Do Not Delete) key belongs to Purematic.
Let Purematic know before you turn the integration off, so they don’t chase connection errors.
Frequently asked questions
Is the AIS auth token stored in Mobaro?
No. Mobaro uses it once to hand Purematic a Mobaro API key, then discards it. That’s why the field is masked and locked after saving.
Why is there an API key called “Purematic Integration Key (Do Not Delete)”?
Mobaro created it when you connected Purematic, and Purematic uses it to reach your organization. Leave it in place and don’t make it Read-only while the integration is in use.
We deleted the Purematic key by mistake. How do we fix it?
Connect again: untick Enable Purematic integration, save, tick it, paste a new AIS auth token and save. Mobaro creates a new key and sends it to Purematic.
Do we need the Mobaro API add-on for Purematic?
No. Mobaro creates Purematic’s key for you. You only see it under Configuration › API › API Keys if your organization has API access. See Creating and managing API keys.
Which data does Purematic send to Mobaro?
That’s set up in Purematic, and depends on your Purematic system. Ask Purematic which data is included, and check it in Mobaro after mapping your first ride.