Datadog Archive API

The Archive API from Datadog — 5 operation(s) for archive.

Operations 10

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /api/v2/cases/{case_id}/archive Archive a case · Datadog Archive Case #
Ask an LLM
“How do I archive a case that's no longer active?”
“Can I archive a case using its key instead of its UUID?”
Tell an agent
Archive case {case_id}.
Move case {case_id} to the archive.
GET /api/v2/logs/config/archive-order Get the logs archive order · Datadog Get Archive Order #
Ask an LLM
“In what order are my logs archives processed?”
“Which logs archive gets evaluated first?”
Tell an agent
Show the current order of our logs archives.
Get the processing sequence of logs archives.
PUT /api/v2/logs/config/archive-order Reorder logs archives · Datadog Update Archive Order #
Ask an LLM
“Can I change which logs archive processes logs first?”
“Does reordering archives change what data each one receives?”
Tell an agent
Set the logs archive order to {data}.
Reorder our logs archives so the compliance archive is first.
POST /api/v2/logs/config/archives Create a logs archive · Datadog Create an Archive #
Ask an LLM
“How do I start archiving logs to cloud storage?”
“Can I set up a new logs archive with a query filter?”
Tell an agent
Create a logs archive with definition {data}.
Set up a new logs archive for long-term retention.
DELETE /api/v2/logs/config/archives/{archive_id} Delete a logs archive · Datadog Delete an Archive #
Ask an LLM
“Can I remove a logs archive I no longer need?”
“What happens to forwarding when a logs archive is deleted?”
Tell an agent destructive · confirm first
Delete logs archive {archive_id}.
Remove archive {archive_id} from our org.
GET /api/v2/logs/config/archives/{archive_id} Get a logs archive · Datadog Get an Archive #
Ask an LLM
“What's the configuration of a specific logs archive?”
“Where is a particular archive storing our logs?”
Tell an agent
Show logs archive {archive_id}.
Get the destination and query of archive {archive_id}.
PUT /api/v2/logs/config/archives/{archive_id} Replace a logs archive's configuration · Datadog Update an Archive #
Ask an LLM
“Can I change the destination bucket of an existing logs archive?”
“Does updating an archive replace its whole configuration?”
Tell an agent
Replace the configuration of archive {archive_id} with {data}.
Update logs archive {archive_id}.
DELETE /api/v2/logs/config/archives/{archive_id}/readers Revoke a role's read access to an archive · Datadog Revoke Role from an Archive #
Ask an LLM
“Can I take away a role's access to a logs archive?”
“How do I stop a team's role from reading an archive?”
Tell an agent destructive · confirm first
Revoke role {data} from archive {archive_id}.
Remove a read role from logs archive {archive_id}.
GET /api/v2/logs/config/archives/{archive_id}/readers List roles allowed to read an archive · Datadog List Read Roles for an Archive #
Ask an LLM
“Which roles can read a given logs archive?”
“Is access to an archive restricted to certain roles?”
Tell an agent
List read roles for archive {archive_id}.
Show which roles can rehydrate from archive {archive_id}.
POST /api/v2/logs/config/archives/{archive_id}/readers Grant a role read access to an archive · Datadog Grant Role to an Archive #
Ask an LLM
“How do I let a role read from a logs archive?”
“Can I restrict archive access by adding specific roles?”
Tell an agent
Grant role {data} read access to archive {archive_id}.
Add a read role to logs archive {archive_id}.

Documentation

Specifications

Schemas & Data

Other Resources

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/datadog:datadog-archive-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

datadog-archive-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  contact:
    email: support@datadoghq.com
    name: Datadog Support
    url: https://www.datadoghq.com/support/
  description: The Datadog API is an HTTP REST API. The API uses resource-oriented URLs to call the API, uses status codes to indicate the success or failure of requests, returns JSON from all requests, and uses standard HTTP response codes. Use the Datadog API to access the Datadog platform programmatically.
  title: Datadog Archive API
  version: '1.0'
servers:
- url: https://{subdomain}.{site}
  variables:
    site:
      default: datadoghq.com
      description: The regional site for Datadog customers.
      enum:
      - datadoghq.com
      - us3.datadoghq.com
      - us5.datadoghq.com
      - ap1.datadoghq.com
      - datadoghq.eu
      - ddog-gov.com
    subdomain:
      default: api
      description: The subdomain where the API is deployed.
- url: '{protocol}://{name}'
  variables:
    name:
      default: api.datadoghq.com
      description: Full site DNS name.
    protocol:
      default: https
      description: The protocol for accessing the API.
- url: https://{subdomain}.{site}
  variables:
    site:
      default: datadoghq.com
      description: Any Datadog deployment.
    subdomain:
      default: api
      description: The subdomain where the API is deployed.
security:
- apiKeyAuth: []
  appKeyAuth: []
tags:


# --- truncated at 32 KB (46 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/datadog/refs/heads/main/openapi/datadog-archive-api-openapi.yml