The Mobaro API lets you pull Checklist Results out of your environment as JSON, on demand or on a schedule, without anyone clicking Export in the backend. It's the right tool when you want Results flowing automatically into a data warehouse, a BI tool like Power BI or Tableau, a Google Sheet, or a custom application.
Why this matters: Manual exports are fine for a one-off, but they don't scale and they don't stay current. An API integration turns Results into a live feed — your dashboards refresh themselves, your compliance archive fills itself, and nobody has to remember to export anything. Build it once with sensible filters and it runs quietly in the background.
What's covered:
Heads-up: An API key grants programmatic access to your organization's data. Treat it like a password — store it securely, never embed it in client-side code, and regenerate it immediately if it is ever exposed.
Before you start
This article assumes you're comfortable making HTTP requests (with curl, Postman, or a scripting language). If the API is new to you, read Getting started with the Mobaro API first — it covers the basics this article builds on. The API follows REST conventions and communicates over HTTPS using JSON. The base URL for all requests is:
https://app.mobaro.com/api/customers
Authentication
Every request authenticates with an API key sent in the X-Api-Key header.
In the Mobaro backend, go to
Configuration → API keysCreate a new key, or copy an existing one
Store it securely — treat it like a password
Include it on every request:
X-Api-Key: YOUR_SECRET_TOKEN
Best practice: For more on creating, rotating, and revoking keys, see Managing API keys.
The Results endpoint
To retrieve Checklist Results, send a GET request to the Results endpoint:
GET https://app.mobaro.com/api/customers/results
The response is a JSON list of Result records. Each Result includes its identifying data, the Checklist and Location it came from, the completing User, scoring, and the answers given — the same underlying data you'd see in an Excel export, in a structure you can parse and store.
Note: The API is for data access and automation, not authoring. You can read Results through it, but you can't edit Checklists or change system configuration via the API. For the authoritative, always-current list of fields and parameters, see the interactive Mobaro API documentation.
Filtering and pagination
Pulling every Result in one request is rarely what you want. The Results endpoint supports query parameters so you can request exactly the slice you need and page through large result sets efficiently.
Parameter | Purpose |
| Page through results — request a batch, then step forward by offset. |
| Filter by when the Checklist was completed (ISO-8601 dates). |
| Filter by record creation or last-update time. |
Location / Checklist / User IDs | Restrict to specific Locations, Checklists, or Users. |
Best practice: Dates use ISO-8601 format, for example 2026-01-31T23:59:59Z. Start with a small Limit (e.g. Limit=20) while testing, then scale up for production.
Example: a monthly export
This request pulls Results completed during January 2026, the kind of call you'd run on a schedule to keep a reporting system up to date:
curl "https://app.mobaro.com/api/customers/results?AnsweredAfter=2026-01-01T00:00:00Z&AnsweredBefore=2026-02-01T00:00:00Z&Limit=100" \
--header "X-Api-Key: YOUR_SECRET_TOKEN"
Parse the JSON response and load it into your destination system. If more records exist than your Limit, step Offset forward and repeat until the response comes back empty.
No-code alternative: Power Automate
If you'd rather not write or maintain code, Mobaro is available as a Microsoft Power Automate connector. You can build a flow that triggers when a Result is submitted and routes the data into Excel, SharePoint, or another downstream system — no API requests to manage. See Getting started with Mobaro's Power Automate connector.
Best practices
Recommendation | Why it matters |
Never expose your API key | Keys grant full data access. Keep them server-side and out of client code. |
Test with curl or Postman first | Confirm the response shape before wiring it into automation. |
Use date filters to pull in batches | Prevents timeouts and keeps each run fast as your data grows. |
Handle retries for 429 / 503 responses | The API may throttle requests under high load — back off and retry. |
Frequently asked questions
Q: Where do I find my API key?
A: In the Mobaro backend under Configuration → API keys. If you don't see it, ask a Mobaro administrator in your organization.
Q: What's the difference between the API and the Excel export?
A: They return the same underlying Result data. The Excel exports are formatted files for manual review; the API returns raw JSON built for automation and integration. See Exporting Results for the file-based options.
Q: How do I filter by date?
A: Use parameters like AnsweredAfter, AnsweredBefore, CreatedAfter, or UpdatedBefore with ISO-8601 dates (e.g. 2026-01-27T10:00:00Z).
Q: I'm getting a 401 error — what does it mean?
A: Your API key is missing, invalid, or expired. Check the X-Api-Key header and confirm the key is still active.
Q: Can I pull invalidated or disapproved Results?
A: Invalidated Results are removed from reporting and exports and are not returned. For exactly how each state behaves, see Invalidating Results and Disapproving Results.
Q: Where's the full field reference?
A: The interactive API documentation at app.mobaro.com/api/customers/documentation is always current and lists every endpoint, parameter, and field.