---
title: "Add insights to a case"
method: PUT
path: "/api/v2/cases/{case_id}/insights"
tags: ["Case Management"]
---

# Add insights to a case

`PUT /api/v2/cases/{case_id}/insights`

Adds one or more insights to a case. Insights are references to related Datadog resources (such as monitors, security signals, incidents, or error tracking issues) that provide investigative context. Up to 100 insights can be added per request. Each insight requires a type (see `CaseInsightType` for allowed values), a ref (URL path to the resource), and a resource_id.

## Path parameters

- `case_id` string, required

## Request body

- CaseInsightsRequest — Request payload for adding or removing case insights.
  - `data` CaseInsightsData, required — Data object containing the insights to add or remove.
    - `attributes` CaseInsightsAttributes, required — Attributes for adding or removing insights from a case.
      - `insights` CaseInsight[], required — Array of insights to add to or remove from a case.
        - `ref` string, required — The URL path or deep link to the insight resource within Datadog (for example, `/monitors/12345?q=total`).
        - `resource_id` string, required — The unique identifier of the referenced Datadog resource (for example, a monitor ID, incident ID, or signal ID).
        - `type` 'SECURITY_SIGNAL' | 'MONITOR' | 'EVENT_CORRELATION' | 'ERROR_TRACKING' | 'CLOUD_COST_RECOMMENDATION' | 'INCIDENT' | 'SENSITIVE_DATA_SCANNER_ISSUE' | 'EVENT' | 'WATCHDOG_STORY' | 'WIDGET' | 'SECURITY_FINDING' | 'INSIGHT_SCORECARD_CAMPAIGN' | 'RESOURCE_POLICY' | 'APM_RECOMMENDATION' | 'SCM_URL' | 'PROFILING_DOWNSIZING_EXPERIMENT', required — The type of Datadog resource linked to the case as contextual evidence. Each type corresponds to a different Datadog product signal (for example, a security finding, a monitor alert, or an incident).
    - `type` 'case', required — JSON:API resource type for cases.

## Response `200`

OK

- CaseResponse — Case response
  - `data` Case — A case
    - `attributes` CaseAttributes, required — Case resource attributes
      - `archived_at` string, date-time, nullable — Timestamp of when the case was archived
      - `attributes` CaseObjectAttributes — Key-value pairs of case attributes. Each key maps to an array of string values, used for flexible metadata such as labels or tags.
      - `closed_at` string, date-time, nullable — Timestamp of when the case was closed
      - `created_at` string, date-time — Timestamp of when the case was created
      - `custom_attributes` object — Case custom attributes
      - `description` string — Description
      - `jira_issue` JiraIssue, nullable — Jira issue attached to case
        - `result` JiraIssueResult — Jira issue information
          - `issue_id` string — Jira issue ID
          - `issue_key` string — Jira issue key
          - `issue_url` string — Jira issue URL
          - `project_key` string — Jira project key
        - `status` 'IN_PROGRESS' | 'COMPLETED' | 'FAILED' — Case status
      - `key` string — Key
      - `modified_at` string, date-time, nullable — Timestamp of when the case was last modified
      - `priority` 'NOT_DEFINED' | 'P1' | 'P2' | 'P3' | 'P4' | 'P5' — Case priority
      - `service_now_ticket` ServiceNowTicket, nullable — ServiceNow ticket attached to case
        - `result` ServiceNowTicketResult — ServiceNow ticket information
          - `sys_target_link` string — Link to the Incident created on ServiceNow
        - `status` 'IN_PROGRESS' | 'COMPLETED' | 'FAILED' — Case status
      - `status` 'OPEN' | 'IN_PROGRESS' | 'CLOSED' — Deprecated way of representing the case status, which only supports OPEN, IN_PROGRESS, and CLOSED statuses. Use `status_name` instead.
      - `status_group` 'SG_OPEN' | 'SG_IN_PROGRESS' | 'SG_CLOSED' — Status group of the case.
      - `status_name` string — Status of the case. Must be one of the existing statuses for the case's type.
      - `title` string — Title
      - `type` 'STANDARD' — Case type
      - `type_id` string — Case type UUID
    - `id` string, required — Case's identifier
    - `relationships` CaseRelationships — Resources related to a case
      - `assignee` NullableUserRelationship, nullable — Relationship to user.
        - `data` NullableUserRelationshipData, nullable, required — Relationship to user object.
          - `id` string, required — A unique identifier that represents the user.
          - `type` 'user', required — User resource type.
      - `created_by` NullableUserRelationship, nullable — Relationship to user.
        - `data` NullableUserRelationshipData, nullable, required — Relationship to user object.
          - `id` string, required — A unique identifier that represents the user.
          - `type` 'user', required — User resource type.
      - `modified_by` NullableUserRelationship, nullable — Relationship to user.
        - `data` NullableUserRelationshipData, nullable, required — Relationship to user object.
          - `id` string, required — A unique identifier that represents the user.
          - `type` 'user', required — User resource type.
      - `project` ProjectRelationship — Relationship to project.
        - `data` ProjectRelationshipData, required — Relationship to project object.
          - `id` string, required — A unique identifier that represents the project.
          - `type` 'project', required — Project resource type.
    - `type` 'case', required — JSON:API resource type for cases.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `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)