> ## Documentation Index > Fetch the complete documentation index at: https://trigger.dev/docs/llms.txt > Use this file to discover all available pages before exploring further. # List errors > List error groups in a specific environment. Runs that fail are grouped by a fingerprint derived from the error type, message, and stack trace. Filter by task identifier, version, status, search text, and time range. ## OpenAPI ````yaml v3-openapi GET /api/v1/errors openapi: 3.1.0 info: title: Trigger.dev v3 REST API description: >- The REST API lets you trigger and manage runs on Trigger.dev. You can trigger a run, get the status of a run, and get the results of a run. version: 2024-04 license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html servers: - url: https://api.trigger.dev description: Trigger.dev API security: [] paths: /api/v1/errors: get: tags: - errors summary: List errors description: > List error groups in a specific environment. Runs that fail are grouped by a fingerprint derived from the error type, message, and stack trace. Filter by task identifier, version, status, search text, and time range. operationId: list_errors_v1 parameters: - $ref: '#/components/parameters/errorsCursorPagination' - $ref: '#/components/parameters/errorsFilter' responses: '200': description: Successful request content: application/json: schema: $ref: '#/components/schemas/ListErrorsResult' '400': description: Invalid query parameters content: application/json: schema: $ref: '#/components/schemas/ErrorWithDetailsResponse' '401': description: Unauthorized request security: - secretKey: [] x-codeSamples: - lang: curl label: List errors source: >- curl -X GET "https://api.trigger.dev/api/v1/errors?filter[status]=unresolved" \ -H "Authorization: Bearer $TRIGGER_SECRET_KEY" components: parameters: errorsCursorPagination: in: query name: page style: deepObject explode: true description: > Paginate the results. Specify the number of errors per page, and the ID of the error to start the page after or before. For object fields like `page`, use the "form" encoding style. For example, to get the next page, use `page[after]=error_1234`. schema: type: object properties: size: type: integer maximum: 100 minimum: 1 default: 25 description: Number of errors per page. Maximum is 100. after: type: string description: >- The ID of the error to start the page after. Sets the pagination direction to forward. before: type: string description: >- The ID of the error to start the page before. Sets the pagination direction to backward. errorsFilter: in: query name: filter style: deepObject explode: true description: > Filter the error groups. Filter by task identifier, version, status, search text, and time range. For array fields, provide multiple values as a comma-separated list. For example, to get unresolved and ignored errors, use `filter[status]=unresolved,ignored`. For the time range, use `filter[period]` (e.g. `filter[period]=7d`) or `filter[from]` / `filter[to]` with ISO timestamps. schema: $ref: '#/components/schemas/ErrorsFilter' schemas: ListErrorsResult: type: object properties: data: type: array items: $ref: '#/components/schemas/ErrorListItem' pagination: type: object properties: next: type: string description: >- The error ID to start the next page after. Pass it as `page[after]`. example: error_8f3b2a1c9d4e5f60 previous: type: string description: >- The error ID to start the previous page before. Pass it as `page[before]`. ErrorWithDetailsResponse: type: object properties: error: type: string example: Query Error details: type: array items: type: object required: - code - message properties: code: type: string description: The error code example: custom message: type: string description: The error message example: 'Invalid status values: FOOBAR' path: type: array items: type: string description: The relevant path in the request example: - filter[status] required: - error ErrorsFilter: type: object properties: taskIdentifier: type: array items: type: string description: The identifier of the task the error belongs to version: type: array items: type: string description: The worker version the error occurred in status: type: array items: type: string enum: - unresolved - resolved - ignored description: The lifecycle status of the error group search: type: string description: Free-text search across the error type and message from: type: string format: date-time description: The start of the time range to count occurrences within to: type: string format: date-time description: The end of the time range to count occurrences within period: type: string description: A relative time range to count occurrences within example: 7d ErrorListItem: type: object required: - id - fingerprint - taskIdentifier - errorType - errorMessage - status - count - firstSeen - lastSeen properties: id: type: string description: The unique ID of the error group, prefixed with `error_` example: error_8f3b2a1c9d4e5f60 fingerprint: type: string description: The raw fingerprint the error is grouped by taskIdentifier: type: string description: The identifier of the task the error belongs to errorType: type: string description: The error type or name (e.g. `TypeError`) errorMessage: type: string description: The normalized error message status: type: string enum: - unresolved - resolved - ignored count: type: integer description: The number of occurrences within the requested time range firstSeen: type: string format: date-time description: When the error group was first seen (global) lastSeen: type: string format: date-time description: When the error group was last seen (global) resolvedAt: type: string format: date-time nullable: true ignoredUntil: type: string format: date-time nullable: true securitySchemes: secretKey: type: http scheme: bearer description: > Use a named environment API key. It starts with `tr_dev_sk_`, `tr_prod_sk_`, `tr_stg_sk_`, etc. Create a named API key in the API Keys section of your Trigger.dev project dashboard. Choose the narrowest access preset that supports your integration. Our TypeScript SDK will default to using the value of the `TRIGGER_SECRET_KEY` environment variable if it is set. If you are using the SDK in a different environment, you can set the key using the `configure` function. ```typescript import { configure } from "@trigger.dev/sdk"; configure({ accessToken: "tr_dev_sk_1234" }); ``` ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.