---
title: "Send an incident event (legacy)"
method: POST
path: "/api/v2/dora/incident"
tags: ["DORA Metrics"]
deprecated: true
---

# Send an incident event (legacy)

`POST /api/v2/dora/incident`

> **Deprecated.**

**Note**: This endpoint is deprecated. Please use `/api/v2/dora/failure` instead.

Use this API endpoint to provide incident data.
Tracking incidents gives a side-by-side view of how failed deployments translate into real-world incidents.

## Request body

- DORAFailureRequest — Request to create a DORA incident event.
  - `data` DORAFailureRequestData, required — The JSON:API data.
    - `attributes` DORAFailureRequestAttributes, required — Attributes to create a DORA incident event.
      - `custom_tags` string[], nullable — A list of user-defined tags. The tags must follow the `key:value` pattern. Up to 100 may be added per event.
      - `env` string — Environment name that was impacted by the incident.
      - `finished_at` integer — Unix timestamp when the incident finished. It must be in nanoseconds, milliseconds, or seconds.
      - `git` DORAGitInfo — Git info for DORA Metrics events.
        - `commit_sha` string, required — Git Commit SHA.
        - `repository_url` string, required — Git Repository URL
      - `id` string — Incident ID. Must be 16-128 characters and contain only alphanumeric characters, hyphens, underscores, periods, and colons (a-z, A-Z, 0-9, -, _, ., :).
      - `name` string — Incident name.
      - `services` string[] — Service names impacted by the incident. If possible, use names registered in the Service Catalog. Required when the team field is not provided.
      - `severity` string — Incident severity.
      - `started_at` integer, required — Unix timestamp when the incident started. It must be in nanoseconds, milliseconds, or seconds.
      - `team` string — Name of the team owning the services impacted. If possible, use team handles registered in Datadog. Required when the services field is not provided.
      - `version` string — Version to correlate with [APM Deployment Tracking](https://docs.datadoghq.com/tracing/services/deployment_tracking/).

## Response `200`

OK

- DORAFailureResponse — Response after receiving a DORA incident event.
  - `data` DORAFailureResponseData, required — Response after receiving a DORA incident event.
    - `id` string, required — The ID of the received DORA incident event.
    - `type` 'dora_failure' — JSON:API type for DORA incident events.

## Other responses

- `202` — OK - but delayed due to incident
- `400` — Bad Request
- `403` — Not Authorized
- `429` — Too many requests

---

[API](https://skmtc.net/datadog/apis/api-v2.md) · [All operations](https://skmtc.net/datadog/apis/api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/datadog/api-v2/versions/da68bf029e4c/schema)