Datto RMM Integration
The Datto RMM integration is a read-only connection for RMM reporting and dashboards. It syncs account-wide monitoring data over the Datto RMM API v2.
The integration never creates, updates, or deletes records in Datto RMM.
Before you begin
Section titled “Before you begin”You need:
- A Datto RMM account with API Access enabled under Setup → Global Settings → Access Control
- An API Key and API Secret Key generated for a user under Setup → Users → Generate API Keys
- The regional API URL shown on that user page (for example
https://zinfandel-api.centrastage.net)
Use a dedicated service user when possible. Regenerating API keys invalidates previous keys.
What you can sync
Section titled “What you can sync”| Dataset | Sync behavior | Notes |
|---|---|---|
| Sites | Atomic snapshot every 60 minutes by default | Customer/site inventory up to the configured snapshot row limit |
| Devices | Rolling snapshot; checks every minute by default | Configure the row limit and duration of each repeating scan |
| Users | Atomic snapshot every 60 minutes by default | Portal users up to the configured snapshot row limit |
| Open Alerts | Atomic snapshot every 5 minutes by default | Current alerts up to the configured snapshot row limit |
| Resolved Alerts | Rolling historical scan every 10 minutes by default | Captures late resolutions without relying on timestamp ordering |
| Activity Logs | Incremental time window every 5 minutes by default | Recent changes plus a resumable historical cursor |
Sites, Users, and Open Alerts expose a Snapshot Row Limit in Dataset Options. The default is 10,000 rows, and the maximum is 100,000 rows. The integration reads as many 250-row Datto API pages as needed to reach that limit. An atomic replacement is written only after every required page succeeds. Hard deletions catch up on the next successful snapshot. Devices drop off after a complete successful rolling scan no longer includes them. Resolved Alerts keep previously observed history while their scan repeats, because Datto can insert older resolutions into earlier pages. Resolved Alerts also expose Full Scan Duration (default 60 minutes). Activity Logs use a day window in Dataset Options (default 30 days, maximum 3,650).
Setup instructions
Section titled “Setup instructions”Step 1: Enable API access
Section titled “Step 1: Enable API access”- In Datto RMM, go to Setup → Global Settings → Access Control
- Turn on Enable API Access
Step 2: Generate API keys
Section titled “Step 2: Generate API keys”- Go to Setup → Users
- Open the user that will own the integration credentials
- Click Generate API Keys
- Copy the API URL, API Key, and API Secret Key
The API Secret Key is shown only once. Store it securely.
Step 3: Connect in Resplendent Data
Section titled “Step 3: Connect in Resplendent Data ”- Go to Settings → Integrations
- Find Datto RMM and click Connect
- Paste the API URL, API Key, and API Secret Key
- Click Save & Test
- After a successful test, click Sync Dataset and choose the Datasets to sync
Device downtime reporting
Section titled “Device downtime reporting”Datto RMM device list endpoints do not support server-side “changed since” filters. The integration scans consecutive device pages, updates each device as it finds it, and starts over after reaching the configured row limit. In Dataset Options, use Full Scan Row Limit (100 to 100,000 rows), Sync Frequency, and Full Scan Duration to control how a full scan is spread across scheduled runs. New Devices Datasets default to 10,000 rows and a 5-minute full scan duration. Use:
- Devices.
onlineand Devices.last_seen(Datto’s lastSeen value) for current device availability - Open Alerts for monitor-driven offline events
- Activity Logs for historical activity around device and user actions
Limits and behavior
Section titled “Limits and behavior”- The integration budgets at most 480 API requests per 60 seconds per account so other Datto consumers still have headroom
- Paginated endpoints return at most 250 records per page; this is an internal API page size, not a Dataset row limit
- Sites, Users, and Open Alerts support a configurable snapshot row limit up to 100,000 rows
- Devices support a configurable rolling row limit from 100 to 100,000 rows; the integration spreads that limit across the full scan duration
- Access tokens are refreshed automatically before they expire
- Only HTTPS
*.centrastage.netAPI hosts are accepted - Private or custom hosts outside Datto’s regional API domains are not supported
Troubleshooting
Section titled “Troubleshooting”| Symptom | Likely cause | What to try |
|---|---|---|
| Invalid credentials | Wrong API Key/Secret or revoked keys | Regenerate keys and reconnect |
| Unsafe URL | API URL is not HTTPS centrastage.net | Paste the API URL from the Datto user page |
| Missing Datasets / empty sync | User lacks view permissions for sites/devices/alerts | Confirm the API user can view Sites, Devices, Monitor, and Audit |
| Throttling / temporary failures | Account-wide rate limit | Wait and retry; reduce concurrent Datto API consumers |
| Unsupported response shape | Unexpected Datto payload | Contact support with the Dataset name and sync time |