How to get your Datto RMM API key and secret key

At a glance

Enable access in Datto RMM, create dedicated credentials on an active user, and copy the platform address shown for that account. The steps below explain the required permissions and how to validate the RMMBackup Beta connection.

Prepare dedicated Datto RMM credentials, record the account address, set read permissions, and troubleshoot connection errors.

Published Updated

On this page

Prerequisites

Use a Datto RMM administrator to enable API access and configure an active API user. Prefer a dedicated user with a reviewed security level and device visibility rather than attaching automation to a person's broad administrator account.

Enable API access and generate keys

  1. Open Setup > Global Settings > Access Control and enable API Access.
  2. Go to Setup > Users and open the intended user.
  3. Select Generate API Keys.
  4. Record the displayed API URL.
  5. Select the appropriate API Security Level and API Component Level.
  6. Copy the API Key and API Secret Key, then save the user.

The secret is hidden after navigating away. Deleting or regenerating keys, or deactivating the user, invalidates the existing credentials.

API URL and authentication

Use the exact platform API URL shown for the user, such as one of Datto RMM's named centrastage.net API hosts. Do not substitute a Partner Portal or Datto Networking API credential.

Datto RMM obtains an OAuth bearer token from [API URL]/auth/oauth/token; normal version 2 requests use [API URL]/api/v2/.... RMMBackup stores the selected platform, API key, and API secret key in the encrypted provider credential store. It reuses the bearer token until near expiry, renews it once after a 401, and never stores the token in snapshots or response archives.

Minimum read permissions

The available collections require the documented View permissions for the selected resources. The broad set includes Setup > Global Settings: View, Sites > Sites: View, Sites > Devices: View plus suitable Device Visibility, Sites > Policies: View, Global or Sites Monitor: View, applicable Filters: View, Global > Audit: View, and Components: View with an appropriate API Component Level. Jobs are not an enumerable backup collection.

Grant only permissions needed by selected account, site, device, inventory, patch, alert, activity, filter, and component collections. Datto's security levels guide explains that device visibility and permissions both constrain results.

Troubleshoot connection problems

  • Token request fails: recheck the API key/secret pair, active user, and account-wide API toggle.
  • 401 after working previously: the bearer token may have expired, or the user/key pair may have been changed.
  • 403 or missing devices: inspect the user's current API Security Level, ordinary View permissions, API Component Level, and Device Visibility.
  • Wrong host: copy the API URL from the user page instead of inferring it.
  • 429 or temporary 403: Datto documents account-wide rate limiting; stop repeated requests and allow the documented window to clear.

Validate and start the first backup

Choose the platform matching your account address, enter the key pair, select what to back up, and save. RMMBackup checks the connection and selected access before enabling backups. After validation, start a manual Datto RMM backup. See the Datto RMM Beta integration and Datto RMM data export guide.

Frequently asked questions

Where is the Datto RMM API URL?

It appears on the individual user's page after API keys are generated. Use that value rather than guessing from another Datto or Kaseya product.

What happens when Datto RMM keys are regenerated?

The prior key pair is invalidated and every integration using it must be updated.

Official source

Datto RMM API

Related Datto RMM integration

Review current Datto RMM backup coverage and availability.