How to get your SuperOps API token
Create a dedicated SuperOps token, copy the customer subdomain, and choose the account's US or EU region. The steps below show where to find each value and how to validate access.
Generate a SuperOps API token, find the customer subdomain and data-center URL, and troubleshoot permission and connection errors.
On this page
Prerequisites
The token inherits the generating SuperOps user's access permissions and restrictions. Use a dedicated least-privilege profile where your SuperOps account model permits it, and confirm that the user can read every collection selected in RMMBackup.
Generate the API token
- Select the settings icon in SuperOps.
- Under My Profile, select your name.
- Open the API token tab and select Generate token.
- Copy the token to a secure credential store.
SuperOps allows one token per user. Regenerating it invalidates the value stored by existing integrations.
Find the subdomain and API region
Open Settings > My MSP > MSP Information and copy the customer subdomain. It is sent separately as the CustomerSubDomain header; do not paste a full URL or a credential-bearing string into that field.
Choose the endpoint for the tenant's data center: https://api.superops.ai/msp for US or https://euapi.superops.ai/msp for EU. The official API reference publishes both endpoints.
Required access
API access follows the connected user's SuperOps permissions and restrictions. The RMMBackup validation reads each selected non-ticketing, non-financial collection, including clients, sites, contacts, technicians and roles, monitored assets and inventory, alerts, scripts, activity, custom-field definitions, IT documentation, and knowledge-base items.
Use a user that can read those selected modules. Do not broaden access to tickets, billing, contracts, invoices, payments, or other excluded modules merely to make validation pass. See SuperOps export and current coverage.
Troubleshoot connection problems
- Unauthorized: regenerate only if necessary, then update the saved token; confirm no spaces were copied.
- Tenant not found or empty: recheck the customer subdomain and US/EU selection. The subdomain is not the full console URL.
- One GraphQL collection is forbidden: the profile can authenticate while lacking that module's read access.
- Partial data: confirm the profile's client or asset visibility. A successful empty list can be legitimate.
- Rate-limit response: SuperOps documents 100 API requests per minute; allow the worker to retry instead of starting overlapping validations.
Frequently asked questions
Can a SuperOps user have several API tokens?
The official guide says a user can have one API token at a time; regenerating it requires updating connected applications.
Which SuperOps API region should I choose?
Use the data center containing the MSP tenant—US or EU—not the technician's physical location.