# Create Sign Request

> Windows | Cross-platform

## Project compatibility

Windows | Cross-platform

## Overview

| Description | API Method | API Path |
| --- | --- | --- |
| Create a sign request for a document using a Box Sign template. | POST | /sign_requests/send |

:::note
To create a sign request with the Create Sign Request activity, the documents used in the process must have template tags.

Template tags are a way in which you add data to a base document that Box Sign automatically recognizes. To learn how to create templates using tags, see the official [Box documentation](https://support.box.com/hc/en-us/articles/4404085855251-Creating-templates-using-tags).
:::

## Input

| Parameter | Description | Data Type |
| --- | --- | --- |
| Signer emails | The email addresses of all required signers. Signer order can be specified, with the first signer designated as index 0. | string |
| File to sign | The file for which the signing request is being created. | data list |
| Destination folder | The folder where the signed document will be saved once completed. | data list |
| Template | The Box Sign template to use for the signing process. Templates can be created directly within Box. | data list |
| Email subject | The subject line of the sign request email sent to recipients. | string |
| Email message | The message body included in the email sent to signers. | string |
| Reminders | If enabled, Box will automatically send reminders to outstanding signers on days 3, 8, 13, and 18. | boolean |
| Days valid | The number of days after which the sign request will automatically expire if not completed. | int32 |
| Are text signatures enabled | Determines whether signers are allowed to sign by typing their names (text signatures). If disabled, only drawn or uploaded signatures are allowed. | boolean |
| External ID | An identifier used to reference the sign request in an external system. | string |
| Prefill tags text value | The text value to prefill a corresponding text tag defined in the template. | string |
| Prefill tags date value | A date value used to prefill a date tag defined in the template. | date time |
| Is document preparation needed | Indicates whether document preparation (e.g., setting up fields) is required before sending. | boolean |
| Prefill tags checkbox value | A boolean value used to prefill a checkbox field in the template. | boolean |
| Prefill tags document tag ID | The tag ID of the field being prefilled, as defined in the Box Sign template. | string |

:::note
Template tags are assigned in the order in which the email addresses are added to the **Signer Emails** field. This is not the same as the order of signing. If there are more tags on the document than actual signers, those tags aren't populated. If you add more signers than tags, the extra signers can sign the document, but are not directed to the locations in the document. They can add text, dates, and signatures wherever they want in the document.
:::

## Output

| Parameter | Description | Data Type |
| --- | --- | --- |
| Sign request ID | The unique identifier of the newly created sign request. | string |
| Create sign request | The full response object detailing the created sign request. | object |

:::note
* In API workflows, a single response object is returned as the output. Any required fields can be extracted directly from this object.
* In RPA workflows, some output parameters may differ, but the necessary values can still be retrieved from the response object even if they are not explicitly exposed.
:::