---
source: https://carbone.io/documentation/design/advanced-features/signatures.html
title: "Integrate electronic signatures into your documents using your usual providers; Docusign, Yousign, SignWell, Docuseal, Documenso, ..."
description: "[BETA] Integrate electronic signatures into your documents"
generated_at: "2026-07-10"
---

# Digital signatures

\[BETA\] Integrate electronic signatures into your documents  
ENTERPRISE FEATURE Available for:  
✓ Carbone Cloud  
✓ Carbone On-premise  
✗ Embedded Carbone JS   v5.00.0+ 

> ℹ️ **Note:** Electronic signature support available in Beta on Carbone V5

## Overview

Support for Electronic Signatures enables you to generate your documents by positioning the signature fields and sending them to your usual signature provider.

The idea is to simplify API integration with your provider by giving the absolute positions of your signature fields during generation. All that's left to do is call the signature provider's API to send the document with the signature positioning information.

## :sign

The `:sign` formatter tells Carbone to set a signature field. You can set up to 999, and any type of signature can be used (signature, date, initials, etc.).

This tag is then replaced by a Carbone technical tag, and when the document is generated as a PDF, you'll get a response in the API with the position of this field and the associated data.

Here's an example. The JSON data are :

```json
{
    "signatureBuyer" : {
        "type": "signature",
        "name": "John Doe",
        "email": "john@mail.fr"
    },
    "signatureSellerDate" : {
        "type": "date",
        "name": "James Setton",
        "email": "james@mail.fr"
    },
    "signatureSeller" : {
        "type": "signature",
        "name": "James Setton",
        "email": "james@mail.fr"
    }
}
```

The simple template defines only the following tags: `{d.signatureBuyer:sign}` `{d.signatureSellerDate:sign}` `{d.signatureSeller:sign}`

![First signature template](/img/doc/signature-template.png)

When the document is generated, you will receive the following feedback:

```json
{
    "success": true,
    "data": {
        "renderId": "xxxxx.pdf",
        "signatures": [
            {
                "data": {
                    "type": "signature",
                    "name": "John Doe",
                    "email": "john@mail.fr"
                },
                "page": 1,
                "x": 108,
                "y": 95
            },
            {
                "data": {
                    "type": "date",
                    "name": "James Setton",
                    "email": "james@mail.fr"
                },
                "page": 1,
                "x": 108,
                "y": 167
            },
            {
                "data": {
                    "type": "signature",
                    "name": "James Setton",
                    "email": "james@mail.fr"
                },
                "page": 1,
                "x": 108,
                "y": 191
            }
        ]
    }
}
```

This data can then be used in the API call you make to your Signature provider.

> ℹ️ **Note:** To locate the signature, Carbone replaces the tag with a specific character string. It's visible in the final document, so we advise you to change the color of the first { of the tag to the same color as the background.

### Usage rules

To use this feature, you must:

-   use Carbone v5 and the new Carbone Studio, and add the header in the render report request: `carbone-version: 5`
-   use specific Arial or Calibri fonts
-   \[optional\] change color of the first { of the tag to the same color as the background

## Sample usage

Here's an example of implementing Carbone with Docusign using Make : [Carbone with Docusign](https://blog.carbone.io/blog/add-a-docusign-signature-to-your-documents/)

## Reference

Signature integration is based on vendor APIs. Here are the links for reference:

-   [Docusign API Reference](https://developers.docusign.com/docs/esign-rest-api/reference/)
-   [Yousign API Reference](https://developers.yousign.com/reference/oas-specification)
-   [Documenso API Reference](https://docs.documenso.com/developers/public-api/reference)
-   [SignWell API Reference](https://developers.signwell.com/reference/getting-started-with-your-api-1)

## Related topics

- [Translations i18n](/documentation/design/advanced-features/translations-i18n.md)
- [Transform](/documentation/design/advanced-features/transform.md)
- [Pictures](/documentation/design/advanced-features/pictures.md)
- [Pagination](/documentation/design/advanced-features/pagination.md)
- [Key-value mapping](/documentation/design/advanced-features/key-value-mapping.md)
- [Hyperlinks](/documentation/design/advanced-features/hyperlinks.md)