DocumentationAPI reference

Rust · 0.1.0

UploadAttachmentSpec

Application protocol schema. Field names and inherited descriptions are kept in their original language.

Where this schema is used

These links are derived from direct references in the protocol snapshot. Follow the calling operation for authentication, accepted fields and runtime behavior; a reusable resource schema is not by itself a complete write request.

Referenced by these component schemas:

Shape and fields

object

FieldType / requirementDescription
attachmentallOf
Attachment
Required
Required. Metadata for the attachment to create. content must be empty; file bytes are sent in data.
attachmentIdstringOptional. The attachment ID to use for this attachment. If empty, a unique ID will be generated. Format: ^[a-zA-Z0-9]([a-zA-Z0-9-]{0,34}[a-zA-Z0-9])?$
totalSizestringOptional. Total size of the file in bytes before media processing. Zero represents an empty file.

Complete schema

Use this complete JSON definition for constraints and nested structure. A field's presence here does not mean it is writable by every caller.

{
  "required": [
    "attachment"
  ],
  "type": "object",
  "properties": {
    "attachment": {
      "allOf": [
        {
          "$ref": "#/components/schemas/Attachment"
        }
      ],
      "description": "Required. Metadata for the attachment to create. content must be empty;\n file bytes are sent in data."
    },
    "attachmentId": {
      "type": "string",
      "description": "Optional. The attachment ID to use for this attachment.\n If empty, a unique ID will be generated.\n Format: ^[a-zA-Z0-9]([a-zA-Z0-9-]{0,34}[a-zA-Z0-9])?$"
    },
    "totalSize": {
      "type": "string",
      "description": "Optional. Total size of the file in bytes before media processing.\n Zero represents an empty file."
    }
  }
}