> For the complete documentation index, see [llms.txt](https://developers.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.docstudio.com/guides/envelope-structure.md). # Envelope Structure This document contains the envelope XML structure, including the fields you can include in the request body. Use this XML inside the `data` field of envelope API requests. Send only the fields your request needs. {% hint style="info" %} The platform generates some envelope properties automatically. {% endhint %} ### Example ```xml Sales agreement Please review the attached data. text 10 10.20 2024-01-11 Record name data:image/png;base64,iVBORw...K5CYII= agreement.pdf 1 2 1 2 Choice

``` ### Envelope root

Attribute	Type	Required	Description
`templateUuid`	UUID	yes	Template ID used to create the envelope
`templateVersion`	UUID	yes	Template version ID used for validation

### Info block Use `` to define envelope-level communication settings, including the subject, message, expiration, and forwarding options.

Element or attribute	Type	Required	Description
`subject`	string	depends	Envelope subject
`message`	string	no	Short message for recipients
`expire`	integer	no	Number of days before the envelope expires
`forwarding/@delegation`	boolean	no	Allow delegation
`forwarding/@sharing`	boolean	no	Allow sharing

### Flow block Use `` to define recipients and map template roles to mailbox IDs.

Element or attribute	Type	Required	Description
`role/@id`	UUID	yes	Role ID from the template
`role/@mailboxUuid`	UUID	yes	Mailbox ID assigned to that role

### Documents block Use `` to send field values for each template document, including standard fields, dictionary references, file attachments, and table rows.

Element or attribute	Type	Required	Description
`document/@id`	UUID	yes	Document ID from the template
`field/@name`	string	yes	Template field name
`field` value	string	depends	Field value, validated by the template
`field/@recordUuid`	UUID	depends	Dictionary record ID
`field/@attachmentUuid`	UUID	depends	Uploaded attachment ID
`fieldgroup/@name`	string	yes	Dynamic table name
`fieldset/@index`	integer	yes	Zero-based row index

### Dynamic field formats #### Text, Number, Currency, Date, and single-select Dropdown ```xml value ``` * `name` — field name from the template * value — field value The platform validates the value against the template rules. #### Multi-select Dropdown ```xml 1 2 ``` Use one `` element for each selected option. #### Dictionary ```xml value ``` * `name` — dictionary field name * `recordUuid` — dictionary record ID * value — record label, if needed If you send both `recordUuid` and text, they must match. #### Signature ```xml data:image/png;base64,... ``` Send the signature as a Base64 data URL. #### File ```xml filename.ext ``` Upload the file first, then send the returned attachment ID. Use [Upload Attachments](/api-reference/upload-attachments.md) to get `attachmentUuid`. #### Checkbox ```xml 1 ``` Send `1` to mark the checkbox as selected. Skip the field when it is optional and unchecked. #### Choice ```xml option-name ``` * `name` — radio group name * value — selected option name inside that group #### Duplicate, Lookup, and Autonumber Do not send these fields manually. The platform fills them automatically. #### Dynamic table ```xml

``` Add one `

` for each row you need. Use a zero-based `index` for each row. ### Platform-generated fields You may also encounter envelope properties generated by the platform. * `created` * `status` * `date` * `roleId` * `active` * `completed` Treat these fields as system data unless an endpoint requires them. ### Related topics * [Fill Envelope](/api-reference/fill-envelope.md) * [Envelope fields](/guides/envelope-fields.md)