Skip to main content
PUT
Save the Datadog connection
Requires Admin or Owner. Supply the latest revision (0 for initial configuration), site, enabled state, and selected signals. Omit api_key to retain the saved key when supported; supply a complete replacement to rotate it. Enabled connections require at least one signal. Stale revisions return 409; invalid credentials/configuration 422; temporary service or credential-storage failures 503. The response does not disclose the key.

Authorizations

Authorization
string
header
required

Bandwidth Labs OAuth access token. Uses the user's selected workspace; the workspace header is not required. Do not also send an API key. Bearer-only operations may additionally require the Labs super_user role.

Headers

X-VOAI-ORGANIZATION-ID
string | null

Required with X-BW-LABS-AGENTS-API-KEY: the positive local workspace ID to access. The key owner must be a current member. Missing or invalid IDs return 400; non-member workspaces return 403. Not required for bearer authentication, which uses the user's selected workspace.

Body

application/json
revision
integer
required
Required range: x >= 0
site
enum<string>
required
Available options:
datadoghq.com,
us3.datadoghq.com,
us5.datadoghq.com,
datadoghq.eu,
ap1.datadoghq.com,
ap2.datadoghq.com,
uk1.datadoghq.com
api_key
string<password> | null
Maximum string length: 128
enabled
boolean
default:true
signals
enum<string>[]
Available options:
metrics,
logs,
traces

Response

Successful Response

can_manage
boolean
default:false
configured
boolean
default:false
delivery
Delivery · object
enabled
boolean
default:false
enabled_at
string<date-time> | null
revision
integer
default:0
signals
enum<string>[]
Available options:
metrics,
logs,
traces
site
enum<string>
default:datadoghq.com
Available options:
datadoghq.com,
us3.datadoghq.com,
us5.datadoghq.com,
datadoghq.eu,
ap1.datadoghq.com,
ap2.datadoghq.com,
uk1.datadoghq.com