Datadog | Operate As Docs

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

Website: datadoghq.com
Connects by: Pasting a API key
Category: Developer tools
Services: 1
Tools: 1,813

Service	Key	Base URL
Datadog	`datadog`	`https://api.{site}`

Your client also types their datadog site (The end of the address you sign in at, such as datadoghq.com or datadoghq.eu).

Connecting

Your client makes a API key in their Datadog settings and pastes it on their link. Operate As tries it with Datadog 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": [
      "datadog"
    ]
  }
]

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

Permissions

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

Tools

Install Datadog's typed package for your language:

pip install operate-as-datadog

pip install operate-as-datadog

Run datadog.abort_test_file_multipart_upload

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

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

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/datadog.abort_test_file_multipart_upload

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://api.{site}, 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-.../datadog/api/v2/permissions" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../datadog/api/v2/permissions" \  -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 Datadog. 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"}