Autotask PSA | Operate As Docs

Connect your client's Autotask PSA with a key they paste, and call its API through Operate As.

Website: datto.com/products/autotask-psa
Connects by: Pasting a Secret
Category: Support
Services: 1
Tools: 2,958

Service	Key	Base URL
Autotask PSA	`autotask`	`https://webservices{zone}.autotask.net/ATServicesRest`

Your client also types their zone number (The number in your Autotask web services address, such as 5 in webservices5.autotask.net).

Connecting

Your client makes a Secret in their Autotask PSA settings and pastes it on their link. Operate As tries it with Autotask PSA before saving it, and stores it encrypted. See Services connected with an API key.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "autotask"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "autotask"    ]  }]

Permissions

What the client reads	Permission it asks for
Use the Autotask PSA key you paste, with only the access you gave that key	Chosen on the provider's screen

Tools

Install Autotask PSA's typed package for your language:

pip install operate-as-autotask

pip install operate-as-autotask

Run autotask.action_types_create_entity

curl -X POST https://api.operate.as/v1/actions/autotask.action_types_create_entity \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {}
  }'

curl -X POST https://api.operate.as/v1/actions/autotask.action_types_create_entity \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {}  }'

Every input, with its JSON Schema: GET /v1/actions/autotask.action_types_create_entity

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://webservices{zone}.autotask.net/ATServicesRest, with the parts in braces filled in from your client's account. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../autotask/V1.0/Companies/entityInformation" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../autotask/V1.0/Companies/entityInformation" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

A key works until your client deletes it in Autotask PSA. They can paste a new one on the same link at any time, and your workflows carry on without changes.

See Keeping access alive and Removing access.

Calls answer, once the key is deleted

{
  "status": 401,
  "data": {
    "…": "the service's own error"
  },
  "encoding": "json"
}

{  "status": 401,  "data": {    "…": "the service's own error"  },  "encoding": "json"}