---
title: "Assign or unassign security findings"
method: PATCH
path: "/api/v2/security/findings/assignee"
tags: ["Security Monitoring"]
---

# Assign or unassign security findings

`PATCH /api/v2/security/findings/assignee`

## Request

- Base URL: `https://api.datadoghq.com`
- URL: `https://api.datadoghq.com/api/v2/security/findings/assignee`
- Auth: one of:
  - API key in header `DD-API-KEY` and API key in header `DD-APPLICATION-KEY`
  - OAuth 2
    - Authorization code: `/oauth2/v1/authorize`
    - Token URL: `/oauth2/v1/token`

Assign or unassign security findings.
You can assign up to 100 security findings per request. Set `assignee_id` to the unique identifier of the Datadog user you want to assign the findings to. Omit `assignee_id` (or set it to `null`) to unassign the findings. Per-finding warnings and failures are returned in the response `meta` object.

## Request body

- AssigneeRequest: Request to assign or unassign security findings.
  - `data` AssigneeRequestData, required: Data of the assignee request.
    - `attributes` AssigneeRequestDataAttributes: Attributes of the assignee request.
      - `assignee_id` string: Unique identifier of the Datadog user to assign the security findings to. If this field is not provided, the security findings are unassigned.
    - `id` string: Unique identifier of the assignee request.
    - `relationships` AssigneeRequestDataRelationships, required: Relationships of the assignee request.
      - `findings` Findings, required: A list of security findings.
        - `data` FindingData[]: Array of security finding data objects.
          - `id` string, required: Unique identifier of the security finding.
          - `type` 'findings', required: Security findings resource type.
    - `type` 'assignee', required: Assignee resource type.

## Response `202`

Accepted

- AssigneeResponse: Response for the assign or unassign request.
  - `data` AssigneeResponseData, required: Data of the assignee response.
    - `attributes` AssigneeResponseDataAttributes, required: Attributes of the assignee response.
      - `assignee_id` string: Unique identifier of the Datadog user assigned to the security findings. Omitted when the findings were unassigned.
    - `id` string, required: Unique identifier of the assignee request.
    - `type` 'assignee', required: Assignee resource type.
  - `meta` AssigneeResponseMeta: Per-finding warnings and failures produced while processing the bulk assignee request.
    - `failures` AssignmentResult[]: Findings that could not be assigned or unassigned.
      - `detail` string, required: Human-readable explanation of the outcome.
      - `finding_id` string, required: Unique identifier of the security finding.
      - `status` integer, required: HTTP-like status code describing the outcome for this finding.
      - `title` string, required: Short label describing the outcome for this finding.
    - `warnings` AssignmentResult[]: Findings for which the assignment succeeded but a non-critical error occurred during processing.
      - `detail` string, required: Human-readable explanation of the outcome.
      - `finding_id` string, required: Unique identifier of the security finding.
      - `status` integer, required: HTTP-like status code describing the outcome for this finding.
      - `title` string, required: Short label describing the outcome for this finding.

## Other responses

- `400`: Bad Request
- `404`: Not Found
- `429`: Too many requests

---

[API](https://skmtc.dev/datadog/apis/datadog-api-v2-collection.md) - [All operations](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/llms.txt) - [OpenAPI document](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/revisions/da68bf029e4c?raw)