Datadog · Schema

IncidentUpdateAttributes

Attributes to update on an existing incident

AnalyticsDashboardsMonitoringPlatformT1Visualizations

Properties

Name Type Description
title string The updated title of the incident
state string The updated state of the incident (transitioning to resolved records resolution time)
severity string The updated severity level of the incident
customer_impacted boolean Updated flag indicating whether the incident has customer impact
customer_impact_scope string Updated description of the customer impact scope
customer_impact_end string ISO 8601 timestamp when customer impact ended (set when marking impact as resolved)
fields object Updated custom field values for the incident
notification_handles array Updated list of notification handles for the incident
View JSON Schema on GitHub

JSON Schema

datadog-incidents-incident-update-attributes-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/datadog/refs/heads/main/json-schema/datadog-incidents-incident-update-attributes-schema.json",
  "title": "IncidentUpdateAttributes",
  "description": "Attributes to update on an existing incident",
  "type": "object",
  "properties": {
    "title": {
      "type": "string",
      "description": "The updated title of the incident",
      "example": "Example Monitor"
    },
    "state": {
      "type": "string",
      "description": "The updated state of the incident (transitioning to resolved records resolution time)",
      "enum": [
        "active",
        "stable",
        "resolved"
      ],
      "example": "active"
    },
    "severity": {
      "type": "string",
      "description": "The updated severity level of the incident",
      "enum": [
        "SEV-1",
        "SEV-2",
        "SEV-3",
        "SEV-4",
        "SEV-5",
        "UNKNOWN"
      ],
      "example": "SEV-1"
    },
    "customer_impacted": {
      "type": "boolean",
      "description": "Updated flag indicating whether the incident has customer impact",
      "example": true
    },
    "customer_impact_scope": {
      "type": "string",
      "description": "Updated description of the customer impact scope",
      "example": "example_value"
    },
    "customer_impact_end": {
      "type": "string",
      "format": "date-time",
      "description": "ISO 8601 timestamp when customer impact ended (set when marking impact as resolved)",
      "example": "example_value"
    },
    "fields": {
      "type": "object",
      "description": "Updated custom field values for the incident",
      "additionalProperties": {
        "type": "object"
      }
    },
    "notification_handles": {
      "type": "array",
      "description": "Updated list of notification handles for the incident",
      "items": {
        "type": "object"
      }
    }
  }
}

Work with this as data

Every JSON Schema 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 schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • 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 JSON Schema
curl "https://apis.io/api/v1/json-schemas/datadog-incidents-incident-update-attributes"
All schemas
curl "https://apis.io/api/v1/json-schemas?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.