Delete Attachment

Access

This single-delete endpoint requires the attachment owner, including when the caller is an administrator. Linked memo management and placement checks also apply.

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

DeleteAttachment deletes an attachment by name.

Parameters

Request body

No request body is declared.

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": "DeleteAttachment deletes an attachment by name.",
  "operationId": "AttachmentService_DeleteAttachment",
  "parameters": [
    {
      "name": "attachment",
      "in": "path",
      "description": "The attachment id.",
      "required": true,
      "schema": {
        "type": "string"
      }
    }
  ],
  "responses": {
    "200": {
      "description": "OK",
      "content": {}
    },
    "default": {
      "description": "Default error response",
      "content": {
        "application/json": {
          "schema": {
            "$ref": "#/components/schemas/Status"
          }
        }
      }
    }
  }
}