errors.issues.list

List a project’s issues

GET /errors/api/projects/{id}/issuesIAM errors:ListIssuesRead

query takes Sentry’s search syntax: is:unresolved|resolved|ignored|all (default unresolved), level:, environment:, release:, assigned:me|none, any tag as key:value, and free text over title, culprit and location.

Request syntax

GET /errors/api/projects/{id}/issues

Path parameters

  • idRequired

    string

    Constraints: uuid

Query parameters

  • queryOptional

    string

    Search in Sentry’s syntax, up to 500 characters: is:unresolved|resolved|ignored|all, level:, environment:, release:, assigned:me|none, up to 5 tags as key:value, and free text over title, culprit and location. Without is: only unresolved issues are listed

    Constraints: max 500 chars

  • sortOptional

    enum

    last_seen (default, newest activity first), first_seen, events or users

    One of: last_seen, first_seen, events, users

    Default: "last_seen"

  • environmentOptional

    string

    Only issues seen in this environment; wins over an environment: in query

    Constraints: max 64 chars

  • periodOptional

    enum

    Only issues seen in this period, counted back from now. Default: any time

    One of: 1h, 24h, 7d, 14d, 30d, 90d

  • limitOptional

    number

    Issues per page: 1–100, default 25

    Constraints: integer, 1-100

    Default: 25

  • offsetOptional

    number

    Issues to skip, for paging: 0–100 000, default 0

    Constraints: integer, 0-100000

    Default: 0

Response

200 with { issues, total, query }: each issue with id, shortId, title, culprit, location, type, level, status (unresolved|resolved|ignored), substatus, firstSeen, lastSeen, count, userCount, firstRelease, lastRelease, environments, assigneeIamUserId, resolvedInRelease, ignoreUntil, ignoreUntilCount, lastEventId and `sparkline` (events per hour, last 24 hours); `total` the matches before paging; `query` the search as it was understood. 404 when the project does not exist, 403 without errors:ListIssues on it.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow errors:ListIssues on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud errors issues list id

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_errors_issues_list.