--- title: "Search error tracking issues" method: POST path: "/api/v2/error-tracking/issues/search" tags: ["Error Tracking"] --- # Search error tracking issues `POST /api/v2/error-tracking/issues/search` ## Request - Base URL: `https://api.datadoghq.com` - URL: `https://api.datadoghq.com/api/v2/error-tracking/issues/search` - 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` Search issues endpoint allows you to programmatically search for issues within your organization. This endpoint returns a list of issues that match a given search query, following the event search syntax. The search results are limited to a maximum of 100 issues per request. ## Query parameters - `include` SearchIssuesIncludeQueryParameterItem[] ## Request body - IssuesSearchRequest: Search issues request payload. - `data` IssuesSearchRequestData, required: Search issues request. - `attributes` IssuesSearchRequestDataAttributes, required: Object describing a search issue request. - `assignee_ids` string[]: Filter issues by assignee IDs. Multiple values are combined with OR logic. - `from` integer, required: Start date (inclusive) of the query in milliseconds since the Unix epoch. - `order_by` 'TOTAL_COUNT' | 'FIRST_SEEN' | 'IMPACTED_SESSIONS' | 'PRIORITY': The attribute to sort the search results by. - `persona` 'ALL' | 'BROWSER' | 'MOBILE' | 'BACKEND': Persona for the search. Either track(s) or persona(s) must be specified. - `query` string, required: Search query following the event search syntax. - `states` IssueState[]: Filter issues by state. Multiple values are combined with OR logic. - `team_ids` string[]: Filter issues by team IDs. Multiple values are combined with OR logic. - `to` integer, required: End date (exclusive) of the query in milliseconds since the Unix epoch. - `track` 'trace' | 'logs' | 'rum': Track of the events to query. Either track(s) or persona(s) must be specified. - `type` 'search_request', required: Type of the object. ## Response `200` OK - IssuesSearchResponse: Search issues response payload. - `data` IssuesSearchResult[]: Array of results matching the search query. - `attributes` IssuesSearchResultAttributes, required: Object containing the information of a search result. - `impacted_sessions` integer: Count of sessions impacted by the issue over the queried time window. - `impacted_users` integer: Count of users impacted by the issue over the queried time window. - `total_count` integer: Total count of errors that match the issue over the queried time window. - `id` string, required: Search result identifier (matches the nested issue's identifier). - `relationships` IssuesSearchResultRelationships: Relationships between the search result and other resources. - `issue` IssuesSearchResultIssueRelationship: Relationship between the search result and the corresponding issue. - `data` IssueReference, required: The issue the search result corresponds to. - `id` string, required: Issue identifier. - `type` 'issue', required: Type of the object. - `type` 'error_tracking_search_result', required: Type of the object. - `included` IssuesSearchResultIncluded[]: Array of resources related to the search results. - union: An array of related resources, returned when the `include` query parameter is used. - 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. - … - `case` IssueCaseRelationship: Relationship between the issue and case. - `data` IssueCaseReference, required: The case the issue is attached to. - … - `team_owners` IssueTeamOwnersRelationship: Relationship between the issue and teams. - `data` IssueTeamReference[], required: Array of teams that are owners of the issue. - … - `type` 'issue', required: Type of the object. - 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 - … - `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 - … - `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. - … - `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: JSON:API resource type for cases. - 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 - `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)