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

The Historical API from Datadog — 3 operation(s) for historical.

Datadog Historical API is one of 186 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 Historical. 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 2 operations across 1 path, and defines 40 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

2 operations 1 paths 40 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.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 Historical 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 2

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

Historical 2
GET
/api/v2/siem-historical-detections/jobs
Datadog List Historical Jobs
ListHistoricalJobs 4 params → 200400403429
POST
/api/v2/siem-historical-detections/jobs
Datadog Run a Historical Job
RunHistoricalJob body → 201400401403404429

Schemas 40

The contract defines 40 schemas that model the data the API accepts and returns. The most detailed are JobDefinition (14 properties), HistoricalJobQuery (8 properties), HistoricalJobResponseAttributes (8 properties), HistoricalJobOptions (7 properties). Each schema is shown below with its type and property counts.

SecurityMonitoringRuleCaseActionType
string
The action type.
SecurityMonitoringRuleImpossibleTravelOptions
object
Options on impossible travel detection method.
1 property
APIErrorResponse
object
API error response.
1 property 1 required
SecurityMonitoringThirdPartyRootQuery
object
A query to be combined with the third party case query.
2 properties
RunHistoricalJobRequestData
object
Data for running a historical job request.
2 properties
SecurityMonitoringRuleQueryAggregation
string
The aggregation type.
SecurityMonitoringRuleCaseAction
object
Action to perform when a signal is triggered. Only available for Application Security rule type.
2 properties
HistoricalJobOptions
object
Job options.
7 properties
SecurityMonitoringRuleNewValueOptions
object
Options on new value detection method.
4 properties
JobDefinitionFromRule
object
Definition of a historical job based on a security monitoring rule.
6 properties 5 required
RunHistoricalJobRequestAttributes
object
Run a historical job request.
3 properties
SecurityMonitoringReferenceTable
object
Reference tables used in the queries.
5 properties
JobDefinition
object
Definition of a historical job.
14 properties 7 required
SecurityMonitoringRuleImpossibleTravelOptionsBaselineUserLocations
boolean
If true, signals are suppressed for the first 24 hours. In that time, Datadog learns the user's regular access locations. This can be helpful to reduce noise a…
SecurityMonitoringRuleCaseCreate
object
Case when signal is generated.
5 properties 1 required
HistoricalJobDataType
string
Type of payload.
HistoricalJobListMeta
object
Metadata about the list of jobs.
1 property
SecurityMonitoringThirdPartyRuleCaseCreate
object
Case when a signal is generated by a third party rule.
4 properties 1 required
SecurityMonitoringRuleNewValueOptionsLearningDuration
integer
The duration in days during which values are learned, and after which signals will be generated for values that weren't learned. If set to 0, a signal will be…
SecurityMonitoringRuleEvaluationWindow
integer
A time window is specified to match when at least one of the cases matches true. This is a sliding window and evaluates in real time. For third party detection…
HistoricalJobResponseData
object
Historical job response data.
3 properties
SecurityMonitoringRuleCaseActionOptionsUserBehaviorName
string
Used with the case action of type 'userbehavior'. The value specified in this field is applied as a risk tag to all users affected by the rule.
SecurityMonitoringRuleKeepAlive
integer
Once a signal is generated, the signal will remain "open" if a case is matched at least once within this keep alive window. For third party detection method, t…
RunHistoricalJobRequest
object
Run a historical job request.
1 property
SecurityMonitoringRuleNewValueOptionsForgetAfter
integer
The duration in days after which a learned value is forgotten.
SecurityMonitoringRuleNewValueOptionsLearningThreshold
integer
A number of occurrences after which signals will be generated for values that weren't learned.
JobCreateResponseData
object
The definition of JobCreateResponseData object.
2 properties
RunHistoricalJobRequestDataType
string
Type of data.
SecurityMonitoringRuleThirdPartyOptions
object
Options on third party detection method.
4 properties
SecurityMonitoringStandardDataSource
string
Source of events, either logs, audit trail, or Datadog events.
SecurityMonitoringRuleNewValueOptionsLearningMethod
string
The learning method used to determine when signals should be generated for values that weren't learned.
CalculatedField
object
Calculated field.
2 properties 2 required
HistoricalJobResponseAttributes
object
Historical job attributes.
8 properties
SecurityMonitoringRuleSeverity
string
Severity of the Security Signal.
SecurityMonitoringRuleCaseActionOptions
object
Options for the rule action
2 properties
HistoricalJobQuery
object
Query for selecting logs analyzed by the historical job.
8 properties
SecurityMonitoringRuleMaxSignalDuration
integer
A signal will "close" regardless of the query being matched once the time exceeds the maximum duration. This time is calculated from the first seen timestamp.
JobCreateResponse
object
Run a historical job response.
1 property
ListHistoricalJobsResponse
object
List of historical jobs.
2 properties
SecurityMonitoringRuleDetectionMethod
string
The detection method.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

datadog-historical-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 Historical 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.