errors.projects.usage

What the ingest received for the project in the last 30 days, by category and outcome

GET /errors/api/projects/{id}/usageIAM errors:ListProjectsRead

Request syntax

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

Path parameters

  • idRequired

    string

    Constraints: uuid

Response

200 with { since, usage, artifacts }: `usage` a row per category (error, transaction, session, profile, …) and outcome with count and bytes. An outcome is `accepted` or a kind and its reason: rate_limited:<reason> and invalid:<reason> (refused, the SDK was told), filtered:<reason> and unsupported (not kept by design), lost:<reason> (acknowledged, then not stored), delayed:<reason> (stored late, also counted under accepted) and client_discard:<reason> (the SDK’s own report); rows from before 2026-11-19 carry the kind alone; `artifacts` the uploaded source-map files of the whole organization by kind, with files and bytes. 404 for a project that does not exist or that you may not read.

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:ListProjects 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 projects usage id

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