---
title: "Get the details of an error tracking issue"
method: GET
path: "/api/v2/error-tracking/issues/{issue_id}"
tags: ["Error Tracking"]
---

# Get the details of an error tracking issue

`GET /api/v2/error-tracking/issues/{issue_id}`

## Request

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

Retrieve the full details for a specific error tracking issue, including attributes and relationships.

## Path parameters

- `issue_id` string, required

## Query parameters

- `include` GetIssueIncludeQueryParameterItem[]

## 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' | '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 an assignee, case and/or teams.
      - `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
      - `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.
      - `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.
    - `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': Case priority
          - `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.
          - `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.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `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)
