> ## Documentation Index
> Fetch the complete documentation index at: https://kb.mspprocess.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Axcient x360Recover

> Connect Axcient x360Recover to Triggr with an x360Portal API key.

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](https://kb.mspprocess.com/integrations/x360cloud.md) 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](https://partner.axcient.com/), 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](https://help.axcient.com/360001190313-Axcient-x360Portal-/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.](https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/integrations-common/base-configuration.png?fit=max\&auto=format\&n=nyuVXZ1rouDTTEvu\&q=85\&s=bb81acb082055015f91beda7b4876f35)

**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.](https://mintcdn.com/triggr/0aCLuL0-lL3gEqxH/images/x360recover/configure.png?fit=max\&auto=format\&n=0aCLuL0-lL3gEqxH\&q=85\&s=8c9f5f95ca0102133ffbfda41508fcca)

## 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:

| Input | Where to get it |
| - | - |
| `deviceId` | `id` from List Devices or List Client Devices |
| `applianceId` | `id` from List Appliances or List Client Appliances |
| `vaultId` | `id` from List Vaults |
| `jobId` | `id` from List Device Jobs |
| `userId` | `id` from List Users |
| `asioEndpointId` | A protected system's `asio_endpoint_id` |

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](https://developer.axcient.com/x360recover).

## Troubleshooting

> [accordion] Every action fails with an authentication error
>
> 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.

> [accordion] An action returns 400 or 404
>
> Pass the numeric `id` from the matching list action, not a name. For job actions, use the device's `client_id` as `clientId`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.