Datadog

Overview

Use Datadog credentials to make authenticated API calls through Alter Vault without exposing API keys in code.

Property	Value
Provider ID	datadog
Category	Monitoring & Observability
Credential Type	API Key

Step 1: Get Credentials

Log in to Datadog

Log in to Datadog at app.datadoghq.com/account/login.

Go to Organization Settings → API Keys

Go to Organization Settings → API Keys.

Create an API key

Click ‘New Key’ to create an API key and copy it.

Get the Application Key

If the API operation requires an Application Key, go to Organization Settings → Application Keys and create a key tied to a user account.

Enter your Datadog site

If the organization is on a non-US1 site (EU, US3, US5, AP1, AP2, gov), enter the matching site in the Datadog Site field (e.g. datadoghq.eu).

Warning

Never share credentials publicly. Store them securely and only enter them in the Alter Vault Developer Portal.

Step 2: Add to Alter Vault

Open the Developer Portal

Go to portal.alterauth.com and navigate to the application.

Add Datadog

Go to Managed Secrets > Add Provider > Datadog.

Enter credentials

Paste the API Key into its field. Add the optional Application Key for operations that require one, and set the optional Datadog Site field when the organization is not on US1.

Save

Click Save. You’ll receive a grant_id to use with the SDK.

Using in Code

response = await alter_app.request(
    HttpMethod.GET,
    "https://api.YOUR_DATADOG_SITE/api/v1/events",  # YOUR_DATADOG_SITE e.g. datadoghq.com (US1), datadoghq.eu (EU), us3.datadoghq.com, etc.
    grant_id="YOUR_GRANT_ID",
    query_params={"start": START_UNIX_SECONDS, "end": END_UNIX_SECONDS},
)

Notes

• The login URL redirects to your correct Datadog site. If your organization is on a non-US1 site (EU, US3, US5, AP1, AP2, gov), you can also log in directly at your site’s URL.

Policy-cataloged operations

Alter policy rules can target these attested operations and families for operation-level and parameter-aware controls.

Operation ID	Families	Method	Provider path
v1/dashboards/list	read	GET	/api/v1/dashboard
v1/dashboards/create	write	POST	/api/v1/dashboard
v1/dashboards/get	read	GET	/api/v1/dashboard/{dashboard_id}
v1/dashboards/update	write	PUT	/api/v1/dashboard/{dashboard_id}
v1/dashboards/delete	delete	DELETE	/api/v1/dashboard/{dashboard_id}
v1/monitors/list	read	GET	/api/v1/monitor
v1/monitors/create	write	POST	/api/v1/monitor
v1/monitors/get	read	GET	/api/v1/monitor/{monitor_id}
v1/monitors/update	write	PUT	/api/v1/monitor/{monitor_id}
v1/monitors/delete	delete	DELETE	/api/v1/monitor/{monitor_id}
v1/events/create	write	POST	/api/v1/events
v1/events/list	read	GET	/api/v1/events
v2/events/search	read	POST	/api/v2/events/search
v1/metrics/query	read	GET	/api/v1/query
v1/metrics/submit	write	POST	/api/v1/series
v2/metrics/submit	write	POST	/api/v2/series
v2/metrics/list	read	GET	/api/v2/metrics
v2/query/timeseries	read	POST	/api/v2/query/timeseries
v1/hosts/list	read	GET	/api/v1/hosts
v1/validate	read	GET	/api/v1/validate
v2/downtime/create	write	POST	/api/v2/downtime
v2/downtime/list	read	GET	/api/v2/downtime
v2/incidents/create	write	POST	/api/v2/incidents
v2/incidents/list	read	GET	/api/v2/incidents
v2/incidents/get	read	GET	/api/v2/incidents/{incident_id}
v2/incidents/update	write	PATCH	/api/v2/incidents/{incident_id}
v2/logs/list	read	GET	/api/v2/logs/events
v2/logs/search	read	POST	/api/v2/logs/events/search
v2/users/create	admin	POST	/api/v2/users
v2/users/list	read	GET	/api/v2/users