> For the complete documentation index, see [llms.txt](https://docs.sign.enadocapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sign.enadocapp.com/evia-sign-api/v1/request-types/template.md).

# Template

## Implementation Overview

Evia Sign's "**Initiate Signature Request from Template**" API simplifies the process of generating signature requests based on predefined templates.&#x20;

This API endpoint enables the initiation of a signature request from a template:

<mark style="color:green;">`POST`</mark> `https://evia.enadocapp.com/_apis/sign/api/Requests?type=1`

#### Headers

| Name          | Type   | Description                                   |
| ------------- | ------ | --------------------------------------------- |
| Authorization | Bearer | Access token should be sent as request header |

{% tabs %}
{% tab title="200: OK " %}
Upon successful creation, a status code of 200 is returned, confirming the successful initiation of the sign request.
{% endtab %}
{% endtabs %}

The provided JSON body serves as an example, showcasing the essential parameters required to initiate such a request.

**Request Body for Template**

```json
{
        "templateId": "05117898-90db-45e5-b6b8-0230fd326e4f",
        "signatories": 
        [
            {
                "roleId": "9e7bb576-a2da-9fdc-d99c-958063dcfa19",
                "signatoryUserName": "Alison",
                "signatoryUserEmail": "alison@email.com"
            },
            {
                "roleId": "dd0caa50-58e1-bf28-441b-556bf70d5fc0",
                "signatoryUserName": "Stev Smith",
                "signatoryUserEmail": "stev@email.com"
            },
            {
                "roleId": "0612c8de-52b0-dc18-9a95-447041ebbe56",
                "signatoryUserName": "Jhone doe",
                "signatoryUserEmail": "jhone@email.com"
            }
        ]
}

```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sign.enadocapp.com/evia-sign-api/v1/request-types/template.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
