errors.issues.delete

Delete issues and their events

DELETE /errors/api/projects/{id}/issuesIAM errors:DeleteIssueChanges stateDestructive

Request syntax

DELETE /errors/api/projects/{id}/issues
{
  "ids": "array of number"
}

Path parameters

  • idRequired

    string

    Constraints: uuid

Request body

  • idsRequired

    array of number

    Issue numbers to delete with all their events, 1–100. Numbers of another project are skipped

    Constraints: integer, min 1

Response

200 with { deleted }: how many issues went, with their events. Numbers that are not this project’s issues are skipped. 404 when the project does not exist.

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:DeleteIssue 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 delete id --ids '[1]'

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