errors.transactions.list

List a project’s transactions by name: count (sampled and extrapolated), p50/p75/p95 duration and failure rate

GET /errors/api/projects/{id}/transactionsIAM errors:GetEventsRead

Request syntax

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

Path parameters

  • idRequired

    string

    Constraints: uuid

Query parameters

  • rangeOptional

    enum

    Window counted back from now: the last 24 hours (default) or 7 days

    One of: 24h, 7d

    Default: "24h"

  • limitOptional

    number

    Most transaction names to return, the most frequent first: 1–200, default 50

    Constraints: integer, 1-200

    Default: 50

Response

200 with a row per transaction name and operation, the most frequent first: name, op, count (stored, i.e. sampled), extrapolatedCount (from the sample rate), p50Ms, p75Ms, p95Ms, failureRate (0–1), lastSeen. 404 when the project does not exist, 403 without errors:GetEvents 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: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 transactions 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_transactions_list.