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 Destination API

The Destination API from Datadog — 2 operation(s) for destination.

Datadog Destination 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 Destination. 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 4 operations across 2 paths, and defines 38 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}.

4 operations 2 paths 38 schemas 1 DELETE1 GET1 PATCH1 POST

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 Destination 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 4

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

Destination 4
POST
/api/v2/logs/config/custom-destinations
Datadog Create a Custom Destination
CreateLogsCustomDestination body → 200400403409429
DELETE
/api/v2/logs/config/custom-destinations/{custom_destination_id}
Datadog Delete a Custom Destination
DeleteLogsCustomDestination 1 param → 204400403404429
GET
/api/v2/logs/config/custom-destinations/{custom_destination_id}
Datadog Get a Custom Destination
GetLogsCustomDestination 1 param → 200400403404429
PATCH
/api/v2/logs/config/custom-destinations/{custom_destination_id}
Datadog Update a Custom Destination
UpdateLogsCustomDestination 1 param body → 200400403404409429

Schemas 38

The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are CustomDestinationCreateRequestAttributes (7 properties), CustomDestinationUpdateRequestAttributes (7 properties), CustomDestinationResponseAttributes (7 properties), CustomDestinationForwardDestinationElasticsearch (5 properties). Each schema is shown below with its type and property counts.

CustomDestinationHttpDestinationAuthCustomHeaderType
string
Type of the custom header access authentication.
CustomDestinationResponseForwardDestinationHttpType
string
Type of the HTTP destination.
CustomDestinationForwardDestinationHttp
object
The HTTP destination.
3 properties 3 required
CustomDestinationResponseAttributes
object
The attributes associated with the custom destination.
7 properties
CustomDestinationResponseForwardDestinationSplunkType
string
Type of the Splunk HTTP Event Collector (HEC) destination.
CustomDestinationForwardDestinationSplunk
object
The Splunk HTTP Event Collector (HEC) destination.
3 properties 3 required
CustomDestinationResponseHttpDestinationAuthCustomHeader
object
Custom header access authentication.
2 properties 2 required
CustomDestinationResponseHttpDestinationAuthBasic
object
Basic access authentication.
1 property 1 required
APIErrorResponse
object
API error response.
1 property 1 required
CustomDestinationResponseForwardDestinationSplunk
object
The Splunk HTTP Event Collector (HEC) destination.
2 properties 2 required
CustomDestinationHttpDestinationAuth
Authentication method of the HTTP requests.
CustomDestinationCreateRequestAttributes
object
The attributes associated with the custom destination.
7 properties 2 required
CustomDestinationElasticsearchDestinationAuth
object
Basic access authentication.
2 properties 2 required
CustomDestinationCreateRequestDefinition
object
The definition of a custom destination.
2 properties 2 required
CustomDestinationForwardDestinationElasticsearchType
string
Type of the Elasticsearch destination.
CustomDestinationResponseDefinition
object
The definition of a custom destination.
3 properties
CustomDestinationAttributeTagsRestrictionListType
string
How forwardtagsrestrictionlist parameter should be interpreted. If ALLOWLIST, then only tags whose keys on the forwarded logs match the ones on the restriction…
CustomDestinationResponseForwardDestinationHttp
object
The HTTP destination.
3 properties 3 required
CustomDestinationHttpDestinationAuthBasicType
string
Type of the basic access authentication.
CustomDestinationType
string
The type of the resource. The value should always be customdestination.
CustomDestinationForwardDestinationHttpType
string
Type of the HTTP destination.
CustomDestinationResponseForwardDestination
A custom destination's location to forward logs.
CustomDestinationForwardDestinationSplunkType
string
Type of the Splunk HTTP Event Collector (HEC) destination.
CustomDestinationCreateRequest
object
The custom destination.
1 property
CustomDestinationUpdateRequestAttributes
object
The attributes associated with the custom destination.
7 properties
CustomDestinationHttpDestinationAuthCustomHeader
object
Custom header access authentication.
3 properties 3 required
CustomDestinationForwardDestination
A custom destination's location to forward logs.
CustomDestinationUpdateRequestDefinition
object
The definition of a custom destination.
3 properties 2 required
CustomDestinationResponse
object
The custom destination.
1 property
CustomDestinationResponseHttpDestinationAuthBasicType
string
Type of the basic access authentication.
CustomDestinationHttpDestinationAuthBasic
object
Basic access authentication.
3 properties 3 required
CustomDestinationResponseForwardDestinationElasticsearch
object
The Elasticsearch destination.
5 properties 4 required
CustomDestinationForwardDestinationElasticsearch
object
The Elasticsearch destination.
5 properties 4 required
CustomDestinationResponseHttpDestinationAuthCustomHeaderType
string
Type of the custom header access authentication.
CustomDestinationResponseForwardDestinationElasticsearchType
string
Type of the Elasticsearch destination.
CustomDestinationResponseElasticsearchDestinationAuth
object
Basic access authentication.
CustomDestinationUpdateRequest
object
The custom destination.
1 property
CustomDestinationResponseHttpDestinationAuth
Authentication method of the HTTP requests.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

datadog-destination-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 Destination 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.