Batch Delete Attachments

Access

Requires the attachment owner or an instance administrator. A linked attachment also requires permission to manage its memo and valid placement.

Delete metadata and stored content

Deletion removes the stored resource rather than only its memo association. Motion-media groups must be selected together; a partial group is rejected. Batch deletion accepts 1–100 attachment resource names. Storage cleanup follows the database commit, so a cleanup failure does not prove that the attachment metadata remains.

Successful response

This operation has no resource to return. The Rust REST transport serializes protobuf Empty as HTTP 200 with JSON {}. The empty success-schema area in the generated contract is intentional, not missing request instructions.

Request

BatchDeleteAttachments deletes multiple attachments in one request.

Parameters

No path or query parameters are declared.

Request body

Required

application/json · BatchDeleteAttachmentsRequest

Responses

Complete operation definition

All declared constraints, media types and response details are retained below. Schema references link to their complete definitions.

{
  "tags": [
    "AttachmentService"
  ],
  "description": "BatchDeleteAttachments deletes multiple attachments in one request.",
  "operationId": "AttachmentService_BatchDeleteAttachments",
  "requestBody": {
    "content": {
      "application/json": {
        "schema": {
          "$ref": "#/components/schemas/BatchDeleteAttachmentsRequest"
        }
      }
    },
    "required": true
  },
  "responses": {
    "200": {
      "description": "OK",
      "content": {}
    },
    "default": {
      "description": "Default error response",
      "content": {
        "application/json": {
          "schema": {
            "$ref": "#/components/schemas/Status"
          }
        }
      }
    }
  }
}