errors.events.list

List an issue’s events, newest first

GET /errors/api/issues/{issueId}/eventsIAM errors:GetEventsRead

Request syntax

GET /errors/api/issues/{issueId}/events

Path parameters

  • issueIdRequired

    string

    Constraints: 1-80 chars, /^(\d+|[A-Za-z0-9][A-Za-z0-9-]*-[0-9A-Za-z]+)$/

Query parameters

  • limitOptional

    number

    Events per page: 1–100, default 25

    Constraints: integer, 1-100

    Default: 25

  • beforeOptional

    string

    Only events received before this time (ISO 8601, UTC with Z): pass the last receivedAt of a page for the next

    Constraints: datetime

Response

200 with the events, newest received first, without their payload: eventId, projectId, issueId, receivedAt, timestamp, level, title, release, environment, userKey, traceId, tags, size (bytes). 404 when the issue does not exist, 403 without errors:GetEvents on its project.

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:GetEvents 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 events list issueId

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