---
title: "Multiple Authentication Methods"
description: "Combine authentication methods to require recipients to complete more than one verification step."
canonical: "https://signatureapi.com/docs/api/resources/ceremonies/authentication/multiple"
source: "https://signatureapi.com/docs/api/resources/ceremonies/authentication/multiple.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T12:10:02Z"
---

# Multiple Authentication Methods

Combine authentication methods to require recipients to complete more than one verification step.

_Last verified against API version 1.18.0._

You can combine multiple authentication methods in a single ceremony. Recipients must complete each method in sequence before accessing the ceremony.

## Rules

Not all combinations are valid. The table below shows which methods can appear at each position. A method marked `No` for later steps can still be combined with others, but it has to come first.

| Method                                                                                         | First step | Second step and beyond |
| ---------------------------------------------------------------------------------------------- | :--------: | :--------------------: |
| [Email Link](https://signatureapi.com/docs/api/resources/ceremonies/authentication/email-link) |     Yes    |           No           |
| [Email Code](https://signatureapi.com/docs/api/resources/ceremonies/authentication/email-code) |     Yes    |           Yes          |
| [Custom](https://signatureapi.com/docs/api/resources/ceremonies/authentication/custom)         |     Yes    |           No           |

Additional constraints:

- A ceremony supports a maximum of 5 authentication methods.
- `email_link` and `custom` can each only be used as the first step.
- `email_link` and `custom` cannot be combined together.
- `email_code` can appear at most once in a ceremony.

## The first method decides who delivers the URL

Whichever methods you combine, the **first** one determines how the recipient reaches the ceremony:

- `email_link` first: SignatureAPI emails the link, and the ceremony's `url` property is `null`. This does not change when other methods follow it.
- `email_code` or `custom` first: the `url` property is returned in the response, and your application delivers it.

Methods after the first are challenges the recipient completes inside the ceremony. They never change who delivers the URL.

## Common combinations

### Custom + Email Code

Your application authenticates the recipient first. SignatureAPI then independently verifies the recipient's identity by sending a code to their email.

Use this combination when you want to authenticate recipients in your own system and also require a second factor that SignatureAPI controls.

```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": "custom",
      "provider": "SuperApp",
      "data": {
        "Session ID": "a4f9e8b2-7c1d-4b2d-9a4b-e0c5d6f7a1b3",
        "Authenticated At": "2026-01-15T10:30:00Z"
      }
    },
    {
      "type": "email_code"
    }
  ]
}
```

Recipient experience:

1. **Authentication in your app**

   The recipient authenticates in your system (custom authentication).

2. **Access the ceremony**

   You direct the recipient to the ceremony URL or embed the ceremony in your app.

3. **Email verification**

   SignatureAPI prompts for additional email verification.

4. **Code entry**

   The recipient enters the 9-digit code from their email.

5. **Signing**

   The recipient proceeds to sign documents.

### Email Link + Email Code

SignatureAPI sends the invitation email automatically. When the recipient opens the ceremony, they must also enter an email verification code.

Use this combination when you want SignatureAPI to handle delivery but also need a second verification step inside the ceremony, for example to meet compliance requirements.

SignatureAPI sends both emails, the invitation link and the verification code, so your application sends none. Because `email_link` is first, the ceremony's `url` property is `null`.

```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"
    },
    {
      "type": "email_code"
    }
  ]
}
```

Recipient experience:

1. **Email link**

   The recipient clicks the ceremony link in the email sent by SignatureAPI.

2. **Email verification**

   SignatureAPI prompts for a second verification step.

3. **Code entry**

   The recipient enters the 9-digit code from their email.

4. **Signing**

   The recipient proceeds to sign documents.
