queue.messages.delete

Delete a processed message by its receipt handle

DELETE /queue/api/queues/{name}/messages/{receiptHandle}IAM queue:DeleteMessageChanges stateDestructive

Fails with ReceiptHandleIsInvalid when the message was received again since this receipt was issued.

Request syntax

DELETE /queue/api/queues/{name}/messages/{receiptHandle}

Path parameters

  • nameRequired

    string

    Constraints: max 80 chars, /^[A-Za-z0-9_-]+(\.fifo)?$/

  • receiptHandleRequired

    string

    Constraints: 1-200 chars

Response

200; data is { deleted: true }.

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 queue:DeleteMessage 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 queue messages delete name receiptHandle

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