---
title: "Snooze an issue"
method: POST
path: "/api/v2/error-tracking/issues/{issue_id}/snooze"
tags: ["Error Tracking"]
---

# Snooze an issue

`POST /api/v2/error-tracking/issues/{issue_id}/snooze`

## Request

- Base URL: `https://api.datadoghq.com`
- URL: `https://api.datadoghq.com/api/v2/error-tracking/issues/{issue_id}/snooze`
- 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` scopes: `error_tracking_read`, `error_tracking_write`

Snooze an issue by `issue_id`: move it to `IGNORED` until a condition is met, then back to `OPEN`.
The condition can be a number of occurrences, a number of distinct values of an attribute such as `@usr.id`,
an elapsed time, or any or all of several conditions.
Snoozing an issue that is already snoozed replaces its snooze. Updating the state of the issue with
`UpdateIssueState` cancels the snooze.
The response includes the watch that reopens the issue.

## Path parameters

- `issue_id` string, required

## Request body

- IssueSnoozeRequest: Snooze issue request payload.
  - `data` IssueSnoozeRequestData, required: Snooze issue request.
    - `attributes` IssueSnoozeRequestDataAttributes, required: Object describing an issue snooze request.
      - `condition` IssueWatchCondition, required: Condition that triggers the watch action. The fields that are set depend on `kind`: `OCCURRENCES` uses `threshold`, `CARDINALITY` uses `threshold` and `projection`, `ELAPSED_TIME` uses `duration`, and `ANY` and `ALL` use `operands`.
        - `duration` string: Time that must elapse from when the watch started, as a Go duration string, such as `24h`, or `168h` for a week.
        - `kind` 'OCCURRENCES' | 'CARDINALITY' | 'ELAPSED_TIME' | 'ANY' | 'ALL', required: Kind of watch condition.
        - `operands` IssueWatchCondition[]: Nested conditions combined by `ANY` or `ALL`.
        - `projection` string[]: Attributes whose distinct values `CARDINALITY` counts, in search syntax: `@` for attributes, such as `@usr.id` or `@account.id`, and no prefix for tags and reserved fields, such as `org_id` or `service`. Only use attributes that the issue's errors carry: a condition on an attribute they don't carry is never met.
        - `threshold` integer: Number of new occurrences, or of distinct values for `CARDINALITY`, that meets the condition, counted from when the watch started.
    - `id` string, required: Issue identifier.
    - `type` 'error_tracking_issue', required: Type of the object.

## Response `200`

OK

- IssueResponse: Response containing error tracking issue data.
  - `data` Issue: The issue matching the request.
    - `attributes` IssueAttributes, required: Object containing the information of an issue.
      - `error_message` string: Error message associated with the issue.
      - `error_type` string: Type of the error that matches the issue.
      - `file_path` string: Path of the file where the issue occurred.
      - `first_seen` integer: Timestamp of the first seen error in milliseconds since the Unix epoch.
      - `first_seen_version` string: The application version (for example, git commit hash) where the issue was first observed.
      - `function_name` string: Name of the function where the issue occurred.
      - `is_crash` boolean: Error is a crash.
      - `languages` IssueLanguage[]: Array of programming languages associated with the issue.
      - `last_seen` integer: Timestamp of the last seen error in milliseconds since the Unix epoch.
      - `last_seen_version` string: The application version (for example, git commit hash) where the issue was last observed.
      - `platform` 'ANDROID' | 'BACKEND' | 'BROWSER' | 'ELECTRON' | 'FLUTTER' | 'IOS' | 'REACT_NATIVE' | 'ROKU' | 'UNKNOWN': Platform associated with the issue.
      - `regression` IssueRegression: Regression information for an issue that was previously resolved and then reopened.
        - `regressed_at` string, date-time, required: Timestamp when the issue was reopened (regressed).
        - `regressed_at_version` string: Application version where the regression was observed.
        - `resolved_at` string, date-time, required: Timestamp when the issue was resolved before the regression.
      - `service` string: Service name.
      - `state` 'OPEN' | 'ACKNOWLEDGED' | 'RESOLVED' | 'IGNORED' | 'EXCLUDED': State of the issue
    - `id` string, required: Issue identifier.
    - `relationships` IssueRelationships: Relationship between the issue and other resources, such as an assignee, case, teams, pull requests, watches, samples, or a Bits AI investigation.
      - `assignee` IssueAssigneeRelationship: Relationship between the issue and assignee.
        - `data` IssueUserReference, required: The user the issue is assigned to.
          - `id` string, required: User identifier.
          - `type` 'user', required: Type of the object
      - `bits_investigation` IssueBitsInvestigationRelationship: Bits AI investigation linked to the issue, returned when `bits_investigation` is requested in the `include` query parameter.
        - `data` IssueBitsInvestigationReference, required: The Bits AI investigation linked to the issue.
          - `id` string, required: Bits AI investigation identifier.
          - `type` 'bits_investigation', required: Type of the object.
      - `case` IssueCaseRelationship: Relationship between the issue and case.
        - `data` IssueCaseReference, required: The case the issue is attached to.
          - `id` string, required: Case identifier.
          - `type` 'case', required: Type of the object.
      - `pull_requests` IssuePullRequestsRelationship: Relationship between the issue and its linked pull requests. Returned when `pull_requests` is included and the issue has linked pull requests.
        - `data` IssuePullRequestReference[], required: Array of pull requests linked to the issue.
          - `id` string, required: Pull request link identifier.
          - `type` 'error_tracking_pull_request', required: Type of the object.
      - `samples` IssueSamplesRelationship: Relationship between the issue and its curated error samples.
        - `data` IssueSampleReference[], required: Array of curated error samples of the issue.
          - `id` string, required: Sample identifier.
          - `type` 'error_tracking_issue_sample', required: Type of the object.
      - `team_owners` IssueTeamOwnersRelationship: Relationship between the issue and teams.
        - `data` IssueTeamReference[], required: Array of teams that are owners of the issue.
          - `id` string, required: Team identifier.
          - `type` 'team', required: Type of the object.
      - `watches` IssueWatchesRelationship: Relationship between the issue and its active watches. Returned when `watches` is included and the issue has an active watch.
        - `data` IssueWatchReference[], required: Array of active watches on the issue.
          - `id` string, required: Watch identifier.
          - `type` 'error_tracking_issue_watch', required: Type of the object.
    - `type` 'issue', required: Type of the object.
  - `included` IssueIncluded[]: Array of resources related to the issue.
    - union: An array of related resources, returned when the `include` query parameter is used.
      - IssueCase: The case attached to the issue.
        - `attributes` IssueCaseAttributes, required: Object containing the information of a case.
          - `archived_at` string, date-time: Timestamp of when the case was archived.
          - `closed_at` string, date-time: Timestamp of when the case was closed.
          - `created_at` string, date-time: Timestamp of when the case was created.
          - `creation_source` string: Source of the case creation.
          - `description` string: Description of the case.
          - `due_date` string: Due date of the case.
          - `insights` IssueCaseInsight[]: Insights of the case.
            - `ref` string: Reference of the insight.
            - `resource_id` string: Insight identifier.
            - `type` string: Type of the insight.
          - `jira_issue` IssueCaseJiraIssue: Jira issue of the case.
            - `error_message` string: Error message set when the Jira issue creation fails.
            - `result` IssueCaseJiraIssueResult: Contains the identifiers and URL for a successfully created Jira issue.
              - …
            - `status` string: Creation status of the Jira issue.
          - `key` string: Key of the case.
          - `linear_issue` IssueCaseLinearIssue: Linear issue of the case.
            - `error_message` string: Error message set when the Linear issue creation fails.
            - `result` IssueCaseLinearIssueResult: Contains the identifiers and URL for a successfully created Linear issue.
              - …
            - `status` string: Creation status of the Linear issue.
          - `modified_at` string, date-time: Timestamp of when the case was last modified.
          - `priority` 'NOT_DEFINED' | 'P1' | 'P2' | 'P3' | 'P4' | 'P5': Work item priority
          - `status` 'OPEN' | 'IN_PROGRESS' | 'CLOSED': Deprecated way of representing the work item 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 work item.
          - `status_name` string: Status of the work item. Must be one of the existing statuses for the work item's type.
          - `title` string: Title of the case.
          - `type` string: Type of the case.
        - `id` string, required: Case identifier.
        - `relationships` IssueCaseRelationships: Resources related to a case.
          - `assignee` NullableUserRelationship, nullable: Relationship to user.
            - `data` NullableUserRelationshipData, nullable, required: Relationship to user object.
              - …
          - `created_by` NullableUserRelationship, nullable: Relationship to user.
            - `data` NullableUserRelationshipData, nullable, required: Relationship to user object.
              - …
          - `modified_by` NullableUserRelationship, nullable: Relationship to user.
            - `data` NullableUserRelationshipData, nullable, required: Relationship to user object.
              - …
          - `project` ProjectRelationship: Relationship to project.
            - `data` ProjectRelationshipData, required: Relationship to project object.
              - …
        - `type` 'case', required: Type of the object.
      - IssueUser: The user to whom the issue is assigned.
        - `attributes` IssueUserAttributes, required: Object containing the information of a user.
          - `email` string: Email of the user.
          - `handle` string: Handle of the user.
          - `name` string: Name of the user.
        - `id` string, required: User identifier.
        - `type` 'user', required: Type of the object
      - IssueTeam: A team that owns an issue.
        - `attributes` IssueTeamAttributes, required: Object containing the information of a team.
          - `handle` string: The team's identifier.
          - `name` string: The name of the team.
          - `summary` string: A brief summary of the team, derived from its description.
        - `id` string, required: Team identifier.
        - `type` 'team', required: Type of the object.
      - IssuePullRequest: A pull request linked to an issue.
        - `attributes` IssuePullRequestAttributes, required: Object containing the information of a pull request linked to an issue.
          - `closed_at` string, date-time: Timestamp of when the pull request was closed. Omitted if the pull request is not closed.
          - `linked_at` string, date-time: Timestamp of when the pull request was linked to the issue.
          - `merged_at` string, date-time: Timestamp of when the pull request was merged. Omitted if the pull request is not merged.
          - `reason` 'unknown' | 'fix' | 'trigger': Why the pull request is linked to the issue. `fix` means the pull request fixes the issue, and `trigger` means the pull request introduced the issue.
          - `url` string: URL of the pull request.
        - `id` string, required: Pull request link identifier.
        - `type` 'error_tracking_pull_request', required: Type of the object.
      - IssueWatch: An active watch on an issue. A watch moves an ignored issue back to open when its condition is met.
        - `attributes` IssueWatchAttributes, required: Object containing the information of a watch.
          - `action` IssueWatchAction: Action applied to the issue when the watch condition is met.
            - `from` 'OPEN' | 'ACKNOWLEDGED' | 'RESOLVED' | 'IGNORED' | 'EXCLUDED': State of the issue
            - `kind` 'CHANGE_ISSUE_STATE', required: Kind of watch action.
            - `to` 'OPEN' | 'ACKNOWLEDGED' | 'RESOLVED' | 'IGNORED' | 'EXCLUDED': State of the issue
          - `condition` IssueWatchCondition: Condition that triggers the watch action. The fields that are set depend on `kind`: `OCCURRENCES` uses `threshold`, `CARDINALITY` uses `threshold` and `projection`, `ELAPSED_TIME` uses `duration`, and `ANY` and `ALL` use `operands`.
            - `duration` string: Time that must elapse from when the watch started, as a Go duration string, such as `24h`, or `168h` for a week.
            - `kind` 'OCCURRENCES' | 'CARDINALITY' | 'ELAPSED_TIME' | 'ANY' | 'ALL', required: Kind of watch condition.
            - `operands` IssueWatchCondition[]: Nested conditions combined by `ANY` or `ALL`.
            - `projection` string[]: Attributes whose distinct values `CARDINALITY` counts, in search syntax: `@` for attributes, such as `@usr.id` or `@account.id`, and no prefix for tags and reserved fields, such as `org_id` or `service`. Only use attributes that the issue's errors carry: a condition on an attribute they don't carry is never met.
            - `threshold` integer: Number of new occurrences, or of distinct values for `CARDINALITY`, that meets the condition, counted from when the watch started.
          - `started_at` string, date-time: Timestamp of when the watch started.
          - `status` 'ACTIVE': Status of the watch.
        - `id` string, required: Watch identifier.
        - `type` 'error_tracking_issue_watch', required: Type of the object.
      - IssueSample: An error event of the issue, picked because it satisfies one or more sample biases.
        - `attributes` IssueSampleAttributes, required: Object containing the information of a sample.
          - `application_id` string: RUM application identifier of the error.
          - `biases` IssueSampleBias[]: Biases the sample satisfies. A single error can satisfy several biases.
          - `build_id` string: Build identifier of the mobile application.
          - `bundle_version` string: Bundle version of the mobile application.
          - `data_source` 'APM' | 'LOGS' | 'RUM' | 'LLMOBS' | 'SYNTHETICS' | 'NONE': Product that reported the error. The value is `NONE` when the error has no known origin.
          - `debug_id` string: Debug identifier used to resolve the stack trace of the error to source code.
          - `debug_info_captured` boolean: Whether an Exception Replay snapshot was captured for the error.
          - `error_source_type` string: Source type set by the SDK or tracer that reported the error, such as `browser` for RUM browser errors or `Crashtracking` for backend crash reports. Usually not set for APM and logs errors.
          - `error_stack` IssueSampleErrorStack, required: Parsed stack trace of the error. Only the sample picked by the `git_metadata` bias has frames.
            - `frames` IssueSampleStackFrame[]: Stack frames, from the top of the stack.
              - …
            - `language` string: Programming language used to parse the stack trace.
          - `event` IssueSampleEvent: Raw error event, as stored by its data source. Its fields differ between APM, logs, and RUM.
          - `git_commit_sha` string: Git commit SHA of the service version.
          - `git_repository_id` string: Git repository identifier of the service.
          - `git_repository_url` string: Git repository URL of the service.
          - `has_session_replay` boolean: Whether a RUM session replay is available for the error.
          - `language` string: Programming language of the service.
          - `links` IssueSampleFrameLink[]: Source code locations of the stack frames that resolve to a repository file.
            - `code_location` IssueSampleGitFileLocation, required: Location of a stack frame in a repository file. Empty when the source code is unavailable.
              - …
            - `frame_id` integer, required: Index of the frame in the stack trace, starting at 0.
          - `os_name` string: Operating system of the device that reported the error.
          - `service` string: Service name.
          - `session_id` string: RUM session identifier of the error.
          - `session_replay_url` string: URL of the RUM session replay of the error.
          - `snapshot_id` string: Identifier of the Exception Replay snapshot of the error.
          - `span_id` string: APM span identifier of the error.
          - `timestamp` string, date-time, required: Timestamp of the error.
          - `trace_id` string: APM trace identifier of the error.
          - `variant` string: Build variant of the mobile application.
          - `version` string: Version of the service.
          - `view_id` string: RUM view identifier of the error.
        - `id` string, required: Sample identifier.
        - `type` 'error_tracking_issue_sample', required: Type of the object.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `429`: Too many requests

## Changes

- **2026-11-16** `68fde5438681`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/changes/api/v2/error-tracking/issues/:issue_id/snooze/post.md)

---

[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/d0ad57792f3c?raw)
