How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Datadog Permissions API

The Permissions API from Datadog — 5 operation(s) for permissions.

Datadog Permissions API is one of 290 APIs that Datadog publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 4 JSON Schema definitions.

Tagged areas include Permissions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, an API reference, and 4 JSON Schemas.

This API exposes 7 operations across 5 paths, and defines 18 schemas. It is described by OpenAPI 3.0.0, at version 1.0.

Requests are made against 3 base URLs: https://{subdomain}.{site}, {protocol}://{name}, https://{subdomain}.{site}.

7 operations 5 paths 18 schemas 1 DELETE4 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0
Base URL
https://api.datadoghq.com
Authentication
OAuth 2.0, API Key, API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 4

Datadog Permissions API declares 4 security schemes for authenticating requests. It supports OAuth 2.0 (AuthZ) using the authorizationCode flow, exposing 68 scopes. An API key is passed in the header as DD-API-KEY (apiKeyAuth). An API key is passed in the header as DD-APPLICATION-KEY (appKeyAuth). It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • AuthZ — This API uses OAuth 2 with the implicit grant flow.
  • apiKeyAuth — Your Datadog API Key.
  • appKeyAuth — Your Datadog APP Key.

Paths & Operations 7

Across 5 paths, the API surfaces 7 operations — 1 DELETE, 4 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Permissions 7
GET
/api/v2/permissions
Datadog List Permissions
ListPermissions → 200400403429
DELETE
/api/v2/roles/{role_id}/permissions
Datadog Revoke Permission
RemovePermissionFromRole 1 param body → 200400403404429
GET
/api/v2/roles/{role_id}/permissions
Datadog List Permissions for a Role
ListRolePermissions 1 param → 200403404429
POST
/api/v2/roles/{role_id}/permissions
Datadog Grant Permission to a Role
AddPermissionToRole 1 param body → 200400403404429
GET
/api/v2/team/{team_id}/permission-settings
Datadog Get Permission Settings for a Team
GetTeamPermissionSettings 1 param → 200403404429
PUT
/api/v2/team/{team_id}/permission-settings/{action}
Datadog Update Permission Setting for Team
UpdateTeamPermissionSetting 2 params body → 200403404429
GET
/api/v2/users/{user_id}/permissions
Datadog Get a User Permissions
ListUserPermissions 1 param → 200403404429

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are PermissionAttributes (7 properties), TeamPermissionSettingAttributes (5 properties), TeamPermissionSetting (3 properties), Permission (3 properties). Each schema is shown below with its type and property counts.

RelationshipToPermission
object
Relationship to a permissions object.
1 property
PermissionsType
string
Permissions resource type.
TeamPermissionSettingType
string
Team permission setting type
TeamPermissionSettingValues
array
Possible values for action
TeamPermissionSettingUpdateAttributes
object
Team permission setting update attributes
1 property
APIErrorResponse
object
API error response.
1 property 1 required
TeamPermissionSettingAttributes
object
Team permission setting attributes
5 properties
TeamPermissionSettingsResponse
object
Team permission settings response
1 property
TeamPermissionSetting
object
Team permission setting
3 properties 2 required
PermissionAttributes
object
Attributes of a permission.
7 properties
TeamPermissionSettingUpdateRequest
object
Team permission setting update request
1 property 1 required
PermissionsResponse
object
Payload with API-returned permissions.
1 property
TeamPermissionSettingResponse
object
Team permission setting response
1 property
TeamPermissionSettingSerializerAction
string
The identifier for the action
TeamPermissionSettingUpdate
object
Team permission setting update
2 properties 1 required
Permission
object
Permission object.
3 properties 1 required
TeamPermissionSettingValue
string
What type of user is allowed to perform the specified action
RelationshipToPermissionData
object
Relationship to permission object.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

datadog-permissions-api-openapi.yml Raw ↑

Other APIs Datadog publishes across the network.

Datadog Dashboards API
Datadog Synthetics API
Datadog Service Level Objectives API
Datadog Security Monitoring API
Datadog Service Definition API
Datadog Software Catalog API
Datadog Users API
Datadog Roles API
Datadog Key Management API
Datadog Organizations API
Datadog Downtimes API
Datadog RUM API
Where this information came from

This is an independent, third-party profile of Datadog Permissions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.