Skip to main content
Triggr works with your x360Recover clients, appliances, vaults, protected systems, backup jobs and restore points, and can create Direct-to-Cloud (D2C) agent tokens. One configuration covers all your clients. Axcient x360Cloud is a separate integration with a key created the same way.

​
Create an API key in Axcient

You need an administrator account in the Axcient x360Portal.
1

Add a key

Sign in to the x360Portal, go to Settings > API Keys and click Add API Key.
2

Generate and copy it

Name it Triggr, select x360Recover if the form lists products, accept the license agreement and click Generate API Key. Axcient shows the key only once. See Axcient’s Generating and Managing API Keys.

​
Connect it in Triggr

1

Open the configuration

Go to Integrations > x360Recover and click Configure on the Base Configuration card.
The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.
2

Enter the key

Paste the key into API Key and click Save Configuration.
The x360Recover configuration window with an API Key field, an Allow insecure TLS switch under Advanced, and a Save Configuration button.

​
Work with x360Recover in workflows

There’s no client mapping. Run List Clients and pass the client’s id as clientId. Other IDs come from list actions: Job actions need both deviceId and the device’s client_id as clientId. Timestamps such as maxTimestamp and starttimeBegin are Unix seconds. Set Vault Connectivity Threshold takes {"threshold": 240} (minutes) in jsonBody, and Create D2C Agent Token takes {}. List Devices and Get Job History return up to 500 results; use offset for more. See the x360Recover API reference.

​
Troubleshooting

Check the key is complete and still exists under Settings > API Keys; any administrator can delete it. If it’s gone, create a new one and paste it in with Edit on the Base Configuration card.
Pass the numeric id from the matching list action, not a name. For job actions, use the device’s client_id as clientId.