![]() |
VOOZH | about |
Service Access Tokens (SATs) are credentials that authenticate Datadog API calls on behalf of a service account. Unlike Personal Access Tokens (PATs), SATs belong to a service account rather than an individual user — they remain valid when team members join or leave the organization.
With SATs, you can:
| Service Access Tokens | Personal Access Tokens | Application keys | |
|---|---|---|---|
| Owned by | Service account | Individual user | Individual user or service account |
| Time-to-live (TTL) | Optional; 1 day, 1 month, 1 year, Never, or Custom | Required; 1 day to 1 year | No expiration |
| Scoped by default | Yes; scopes are mandatory | Yes; scopes are mandatory | Optional; unscoped by default |
| Standalone authentication | Yes; no API key pairing needed | Yes; no API key pairing needed | No; requires an API key |
| Identifiable prefix | ddsat_ | ddpat_ | ddapp_ (new) |
| Visible in | Service account details, Organization Settings > Access Tokens | Personal Settings > Access Tokens, Organization Settings > Access Tokens | Personal Settings > Application Keys, Organization Settings > Application Keys |
For Personal Access Tokens, see Personal Access Tokens.
service_account_write permission to create SATs for a service account you manage.org_app_keys_write permission to manage SATs for any service account in the organization.After you save, a details panel displays the token secret, name, Token ID, owner, owner roles, expiration date, and scopes.
SATs support two authentication methods.
Pass the SAT as a Bearer token in the Authorization header. This method does not require an
API key:
curl -X GET "https://api.datadoghq.com/api/v2/users" \
-H "Authorization: Bearer <YOUR_SAT>"
Pass the SAT in the dd-application-key header:
curl -X GET "https://api.datadoghq.com/api/v2/users" \
-H "dd-application-key: <YOUR_SAT>"
Note: When a valid SAT is provided in the dd-application-key header, Datadog authenticates
with the SAT only. The dd-api-key header is optional and its value is not evaluated.
A service account’s tokens appear in the details panel under Organization Settings > Service Accounts.
Organization administrators with the org_app_keys_read permission can also view all SATs
alongside Personal Access Tokens from Organization Settings > Access Tokens.
Alternatively, revoke a SAT from Organization Settings > Access Tokens.
Revoked tokens can no longer authenticate API calls. Revocation takes effect within seconds.
You can update the name and scopes of an existing SAT. You cannot modify the expiration date after creation. To change the expiration, revoke the token and create a new one.
| Permission | Description |
|---|---|
service_account_write | Create SATs for service accounts you manage |
org_app_keys_read | View SATs for all service accounts in the organization |
org_app_keys_write | Create, edit, and revoke SATs for any service account |
For more information, see Role Based Access Control.
If Audit Trail is enabled, it records all SAT creation, usage, and revocation events. Each API call authenticated with a SAT is attributed to the owning service account. This gives administrators visibility into automated credential usage across the organization.
To review SAT activity, navigate to Security > Compliance > Audit Trail and filter by the Service Access Token authentication method.
Manage SATs programmatically through the Datadog API:
| Operation | Endpoint |
|---|---|
| List SATs | GET /api/v2/service_accounts/<SERVICE_ACCOUNT_ID>/access_tokens |
| Create a SAT | POST /api/v2/service_accounts/<SERVICE_ACCOUNT_ID>/access_tokens |
| Get a specific SAT | GET /api/v2/service_accounts/<SERVICE_ACCOUNT_ID>/access_tokens/<TOKEN_ID> |
| Update a SAT | PATCH /api/v2/service_accounts/<SERVICE_ACCOUNT_ID>/access_tokens/<TOKEN_ID> |
| Revoke a SAT | DELETE /api/v2/service_accounts/<SERVICE_ACCOUNT_ID>/access_tokens/<TOKEN_ID> |
To retrieve all PATs and SATs across users and service accounts in a single call, use the unified endpoint:
GET /api/v2/personal_access_tokens
Additional helpful documentation, links, and articles:
| |