At a glance
Attendance can be sent to Mobaro via the attendance API.
This data can power the latest attendance dashboard widget (entries, re-entries, exits, in park).
Attendance also populates the operations report attendance field and enables rides per capita metrics.
If no attendance is provided for a period, attendance-based fields show “-”.
Who this is for
Admins / super users setting up integrations
Developers / IT responsible for API connections
Operations leaders who want attendance and per-capita context in reporting
Overview
Mobaro supports attendance reporting through an API endpoint that lets you post attendance values such as total entries, re-entries, exits, and current guests in park. Once sent, Mobaro can display the latest attendance on dashboards and use attendance in reporting.
Attendance is commonly sourced from ticketing, turnstiles, or access control systems, but it can also be entered from any trusted system that can make an API call.
How attendance is used in Mobaro
Latest attendance dashboard widget
When attendance data is available, the Latest attendance widget can display:
Total entries
Re-entries
Total exits
In park (current attendance)
Last updated timestamp
If no attendance data is available for the selected organization or location group, the widget shows a “no data available” message.
Operations report
If attendance is provided for the reporting period, the operations report can populate:
Attendance in the park overview
Rides per capita metrics (when applicable)
If no attendance is provided, these values display as “-” (Mobaro does not estimate attendance automatically).
Before you start
Confirm you have API access
You’ll need:
An active Mobaro API key
A system capable of making HTTPS requests (for example: a middleware service, scheduled job, or integration platform)
Tip: If you’re unsure whether your account is enabled for the attendance integration, contact [email protected].
Post attendance data with the API
This section shows the fields Mobaro expects and a safe, anonymized example you can model your integration on.
Attendance fields you can send
Typical fields include:
timestamp: When the attendance snapshot applies (ISO 8601 / RFC 3339 format recommended)
entries: Total entries
reEntries: Total re-entries
exits: Total exits
currentAttendance: Guests currently in park
target: Which location group (or target scope) the attendance applies to
Note: Your integration should use the same “target” scope consistently (for example: your park’s primary location group).
Example request body
Use this as a template and replace values with your own.
{
"timestamp": "2026-02-11T10:24:01.000Z",
"entries": 3500,
"reEntries": 30,
"exits": 453,
"currentAttendance": 3077,
"target": "locationgroups/XXXXX-A"
}Tip: Keep the payload simple and consistent—Mobaro can only display what you provide.
Example cURL request
curl https://app.mobaro.com/api/customers/attendance \
--request POST \
--header 'Content-Type: application/json' \
--header 'x-api-key: YOUR_API_KEY' \
--data '{
"timestamp":"2026-02-11T10:24:01.000Z",
"entries":3500,
"reEntries":30,
"exits":453,
"currentAttendance":3077,
"target":"locationgroups/XXXXX-A"
}'
Expected result: Mobaro stores the latest attendance snapshot for the target, and the Latest attendance widget updates to reflect the newest values.
Recommended posting frequency
Near real-time: Post every few minutes (best for live dashboards)
Operational cadence: Post hourly or at set checkpoints
Minimum: Post at least once per day if you only care about daily reporting
Recommendation: If you use the operations report, ensure attendance is posted before the report is generated early the next morning so the prior day’s report can populate attendance and per-capita fields.
Troubleshooting
The widget says “No data available”
Confirm your request is successfully posting (HTTP success response from your integration).
Confirm the target is correct (for example: the location group you’re viewing in the widget).
Confirm you’ve posted at least one attendance record recently.
The operations report shows “-” for attendance or rides per capita
Attendance wasn’t provided for the report’s period, or it was posted after the report was generated.
Post attendance earlier (or on a schedule) so it exists before report generation.
Values look wrong (entries/exits don’t match expectations)
Verify you’re sending the correct source values (entries, re-entries, exits, in park).
Confirm your system’s definitions match Mobaro’s intended meaning (for example: re-entries vs. entries).
Frequently asked questions
Q: Do we have to send all fields every time?
A: You should send the fields you want Mobaro to display and use. If a value isn’t provided, Mobaro can’t show it.
Q: What does the target field represent?
A: It tells Mobaro which scope the attendance applies to (commonly a park-level location group). Use a consistent target so dashboards and reporting stay aligned.
Q: What happens if we don’t send attendance at all?
A: Attendance-based fields will display “-” in the operations report, and the attendance widget will show no data available.
Q: Can this power both reporting and dashboards?
A: Yes. The same attendance feed can populate the operations report and the Latest attendance dashboard widget.