---
title: "Email Link Authentication"
description: "Authenticate recipients with a secure link sent to their email address."
canonical: "https://signatureapi.com/docs/api/resources/ceremonies/authentication/email-link"
source: "https://signatureapi.com/docs/api/resources/ceremonies/authentication/email-link.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T12:10:02Z"
---

# Email Link Authentication

Authenticate recipients with a secure link sent to their email address.

_Last verified against API version 1.18.0._

With email link authentication, SignatureAPI sends the [recipient](https://signatureapi.com/docs/api/resources/recipients/object) an email with a direct link. Clicking the link authenticates the recipient and opens their signing session.

This is the default authentication method. If you don't specify a ceremony configuration, SignatureAPI uses email link authentication automatically.

## When to use

Email link authentication works well when:

- You want the simplest experience for recipients.
- Recipients check email to access documents.
- You don't need to control the ceremony URL or deliver it through other channels.
- Your security requirements allow email-based authentication.

## Creating an email link ceremony

You can create an email link ceremony automatically when creating an envelope, or manually using the Create Ceremony endpoint.

### On envelope creation (automatic)

By default, SignatureAPI creates an email link ceremony and sends the invitation email when you create an envelope.

```http
POST /v1/envelopes HTTP/1.1
Host: api.signatureapi.com
X-API-Key: YOUR_API_KEY
Content-Type: application/json

{
    "title": "Service Agreement",
    "recipients": [
        {
            "type": "signer",
            "key": "client",
            "name": "John Doe",
            "email": "john.doe@example.com"
        }
    ],
    "documents": [
        {
            "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/service-agreement.pdf",
            "places": [
                { "key": "client_signature", "type": "signature", "recipient_key": "client" }
            ],
            "fixed_positions": [
                { "place_key": "client_signature", "page": 1, "top": 600, "left": 72 }
            ]
        }
    ]
}
```

To add ceremony options such as a redirect URL, set the `ceremony` property explicitly.

```http
POST /v1/envelopes HTTP/1.1
Host: api.signatureapi.com
X-API-Key: YOUR_API_KEY
Content-Type: application/json

{
    "title": "Service Agreement",
    "recipients": [
        {
            "type": "signer",
            "key": "client",
            "name": "John Doe",
            "email": "john.doe@example.com",
            "ceremony": {
                "authentication": [
                    {
                        "type": "email_link"
                    }
                ],
                "redirect_url": "https://www.example.com/redirect"
            }
        }
    ],
    "documents": [
        {
            "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/service-agreement.pdf",
            "places": [
                { "key": "client_signature", "type": "signature", "recipient_key": "client" }
            ],
            "fixed_positions": [
                { "place_key": "client_signature", "page": 1, "top": 600, "left": 72 }
            ]
        }
    ]
}
```

### Create Ceremony endpoint (manual)

Use the [Create Ceremony](https://signatureapi.com/docs/api/resources/ceremonies/create) endpoint to create an email link ceremony after the envelope is created.

> **Note:** Creating a new ceremony automatically revokes any previous ceremony for that recipient. Only the most recent ceremony remains active.

```http
POST /v1/recipients/re_49r1R2jpPDz8hSpP75ZkPp/ceremonies HTTP/1.1
Host: api.signatureapi.com
X-API-Key: YOUR_API_KEY
Content-Type: application/json

{
    "authentication": [
        {
            "type": "email_link"
        }
    ]
}
```

## Email customization

By default, SignatureAPI derives the email content from the envelope:

- Subject: `envelope.title`
- Message body: `envelope.message`
- Language: `envelope.language`

For example, an envelope with:

```json
{
  "title": "Dummy Agreement",
  "message": "Please take a moment to review the attached agreement. Once you complete your electronic signature, a signed copy will be sent to your email.\n\nIf you have questions, feel free to reach out."
}
```

produces an email similar to this:

![Invitation email titled Dummy Agreement with a View and Sign button, the sender details and the envelope message](https://signatureapi.com/docs/api/resources/ceremonies/authentication/email-example.webp)

### Per-recipient overrides

Use `subject_override` and `message_override` on the `email_link` authentication object to customize the email for a specific recipient.

```http
POST /v1/envelopes HTTP/1.1
Host: api.signatureapi.com
X-API-Key: YOUR_API_KEY
Content-Type: application/json

{
    "title": "Service Agreement",
    "recipients": [
        {
            "type": "signer",
            "key": "client",
            "name": "John Doe",
            "email": "john.doe@example.com",
            "ceremony": {
                "authentication": [
                    {
                        "type": "email_link",
                        "subject_override": "Action Required: Please sign the Service Agreement",
                        "message_override": "Dear John,\n\nPlease review and sign the attached Service Agreement at your earliest convenience."
                    }
                ]
            }
        }
    ],
    "documents": [
        {
            "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/service-agreement.pdf",
            "places": [
                { "key": "client_signature", "type": "signature", "recipient_key": "client" }
            ],
            "fixed_positions": [
                { "place_key": "client_signature", "page": 1, "top": 600, "left": 72 }
            ]
        }
    ]
}
```

`message_override` supports Markdown formatting: `**bold**`, `*italic*`, and `\n\n` for paragraph breaks.

To send invitation emails through your own infrastructure with custom branding, use [Custom Authentication](https://signatureapi.com/docs/api/resources/ceremonies/authentication/custom) to obtain the ceremony URL and deliver it yourself.

## Audit log

When a recipient clicks the email link, SignatureAPI records the timestamp. The audit log entry looks like this:

12/31/2025 11:59:59 PM John Doe (#7161cf07) has authenticated using a secure link sent to john⁠@example.com.
