How to get your Action1 API client ID and client secret

At a glance

Create dedicated Action1 credentials, give them read access to the organizations you want to protect, and select the matching account region. The steps below show where to find each value and how to validate the connection.

Create dedicated Action1 credentials, choose the correct account region, assign read access, and troubleshoot connection errors.

Published Updated

On this page

Prerequisites

Use an Action1 account allowed to manage users, API credentials, and roles. Plan the organization scope before creating the credential: a credential without access to an organization cannot discover or back up it.

Create the client ID and secret

  1. Open Configuration > Users & API Credentials.
  2. Select + New API Credentials.
  3. Enter a descriptive name and assign the least-privilege role prepared for the backup.
  4. Copy both the Client ID and Client Secret. Action1 does not show the secret again after the dialog closes.
  5. Add additional role assignments only where required for the selected organizations and collections.

Deleting the credential immediately breaks integrations using that pair. Store both values as secrets; never include them in a test URL.

Select the regional API URL

RMMBackup offers the official API hosts for North America (app.action1.com), North America 2 (app.na-2.action1.com), Europe (app.eu.action1.com), United Kingdom (app.uk.action1.com), and Australia (app.au.action1.com), each under /api/3.0. Choose the region where the Action1 account is registered.

The official authentication guide exchanges the client ID and secret at /oauth2/token, then uses the returned bearer token. RMMBackup performs that exchange internally.

Assign minimum permissions

Action1 permissions are role-based. Grant only the view or manage permission named by the official API operation for every selected collection. Core backup domains include View Endpoints, View Installed Software, View Updates, View Vulnerabilities, and View Automations and History. Configuration collections can additionally require permissions for advanced settings, scripts, software repository, roles, reports, audit events, and agent deployment.

Because the current Action1 implementation spans many optional domains, RMMBackup validates every selected permission domain before backup. Do not grant remote-control or execution rights merely to satisfy a read-only backup. Use Action1's Users and Roles guide to limit organization scope.

Troubleshoot connection problems

  • OAuth authentication fails: confirm the client ID and secret are from the selected region and were not deleted or replaced.
  • 403 on one collection: the credential is valid but its assigned role lacks that domain's documented permission.
  • Organizations are missing: check role assignments and organization scope before changing credentials.
  • No visible organizations: this can be a valid restricted scope; it is not the same as a bad client secret.
  • Wrong host: credentials created in one Action1 region do not authenticate against another region's API URL.

RMMBackup availability

Action1 is available in RMMBackup with supported collection backups, snapshot browsing, and ZIP exports. Review current backup coverage and the data export overview; restore and write-back remain unsupported.

Frequently asked questions

Can Action1 API credentials be limited to selected organizations?

Yes. Assigned roles control permissions and organization visibility. RMMBackup attempts every organization visible to the configured credential.

Does RMMBackup need Action1 write access?

No. OAuth token creation is the only POST used by the connection; provider-data collection uses documented GET operations.

Official source

Action1 API credentials

Related Action1 integration

Review current Action1 backup coverage and availability.