Datadog · Arazzo Workflow

Datadog Resolve an Incident

Version 1.0.0

Retrieve an incident then update its state to resolved.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub AnalyticsDashboardsMonitoringPlatformT1VisualizationsArazzoWorkflows

Provider

datadog

Workflows

resolve-incident
Get an incident then update its state to resolved.
Fetches the incident by id to confirm it exists, then patches its state to resolved to mark the incident closed.
2 steps inputs: incidentId outputs: incidentId, state
1
getIncident
Retrieve the incident details by id to confirm it exists and capture its current state before resolving.
2
resolveIncident
Update the incident state to resolved, which records the resolution time and marks the incident closed.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Datadog Resolve an Incident
  summary: Retrieve an incident then update its state to resolved.
  description: >-
    Closes out a Datadog incident by first retrieving its current details to
    confirm it exists and capture its present state, and then updating the
    incident to transition its state to resolved, which records the resolution
    time. Every step spells out its request inline so the flow can be read and
    executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: existingApi
  url: ../openapi/datadog-existing-api-openapi.yml
  type: openapi
- name: getApi
  url: ../openapi/datadog-get-api-openapi.yml
  type: openapi
workflows:
- workflowId: resolve-incident
  summary: Get an incident then update its state to resolved.
  description: >-
    Fetches the incident by id to confirm it exists, then patches its state to
    resolved to mark the incident closed.
  inputs:
    type: object
    required:
    - incidentId
    properties:
      incidentId:
        type: string
        description: The unique identifier of the incident to resolve.
  steps:
  - stepId: getIncident
    description: >-
      Retrieve the incident details by id to confirm it exists and capture its
      current state before resolving.
    operationId: GetIncident
    parameters:
    - name: incident_id
      in: path
      value: $inputs.incidentId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      incidentId: $response.body#/data/id
      currentState: $response.body#/data/attributes/state
  - stepId: resolveIncident
    description: >-
      Update the incident state to resolved, which records the resolution time
      and marks the incident closed.
    operationId: UpdateIncident
    parameters:
    - name: incident_id
      in: path
      value: $steps.getIncident.outputs.incidentId
    requestBody:
      contentType: application/json
      payload:
        data:
          id: $steps.getIncident.outputs.incidentId
          type: incidents
          attributes:
            state: resolved
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      incidentId: $response.body#/data/id
      state: $response.body#/data/attributes/state
  outputs:
    incidentId: $steps.resolveIncident.outputs.incidentId
    state: $steps.resolveIncident.outputs.state

Work with this as data

Every workflow 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 arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow 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 workflow
curl "https://apis.io/api/v1/arazzo/datadog-resolve-incident-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?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.