A ceremony is the session where a recipient acts on an envelope to complete actions like signing documents. Before accessing a ceremony, recipients must authenticate their identity. SignatureAPI offers multiple authentication methods that can be used individually or combined to meet your security and user experience requirements.

​
Authentication Methods

SignatureAPI supports several authentication methods to verify recipient identity before they can access their ceremony: SignatureAPI sends recipients an email containing a direct link to the ceremony. When recipients click the link, they’re automatically authenticated and can proceed with signing.
  • Default method: Automatically used when you create envelopes
  • Zero setup: Works out of the box with no configuration needed
  • Simple experience: One-click access for recipients
  • Automatic ceremony creation: Ceremonies are created and emails sent automatically
Learn more about Email Link Authentication →

​
Email Code Authentication

SignatureAPI sends recipients an email containing a 9-digit verification code. Recipients must enter this code in the ceremony interface to authenticate.
  • URL control: You receive the ceremony URL to share via your own channels
  • Email verification: Ensures recipients have access to their email account
  • Flexible sharing: Send the ceremony URL via SMS, app notifications, or direct links
  • Manual ceremony creation: Requires manual ceremony setup
Learn more about Email Code Authentication →

​
Custom Authentication

Your application authenticates recipients using your own methods. SignatureAPI provides a ceremony URL that you can share directly or embed in your application.
  • Full control: Authenticate recipients using your existing systems
  • Embedding support: Perfect for in-app signing experiences
  • Custom audit trail: Your authentication details are included in the audit log
  • Maximum flexibility: Use any authentication method your application supports
Learn more about Custom Authentication →

​
Use Multiple Authentication Methods

You can combine authentication methods for enhanced security or compliance requirements. Each method must be completed in sequence before recipients can access the ceremony. Learn more about Multiple Authentication Methods →

​
Ceremony Creation

You can create ceremonies in two ways: automatically when creating an envelope, or manually at a later time.

​
On Envelope Creation (Automatic)

When creating an envelope, define the Ceremony that will be automatically created for that recipient, using the recipient.ceremony parameter. If no ceremony is provided, a Ceremony with email_link authentication is created by default. 
// POST https://api.signatureapi.com/v1/envelopes
// X-API-Key: key_test_...
// Content-Type: application/json

{
    "title": "Service Agreement",
    "recipients": [
        {
            "type": "signer",
            "key": "client",
            "name": "John Doe",
            "email": "john.doe@example.com"
            // ceremony defaults to "email_link"
        }
    ],
    "documents": [ /* ... */ ],
    // ...
}

​
Create Ceremony Endpoint (Manual)

You can create additional ceremonies for recipients using the Create Ceremony endpoint. This gives you flexibility to change authentication methods or create new access points as needed.
When you create a new ceremony for a recipient, any previous ceremonies are automatically revoked. This ensures that only the most recent ceremony remains active and accessible.
Common use cases for creating additional ceremonies:
  • Switching authentication methods: Start with custom authentication for an embedded ceremony, then switch to email link authentication if the recipient doesn’t complete it within a set time
  • Extending access: Provide a new ceremony URL if the original one has expired or been compromised
  • Changing ceremony settings: Update redirect URLs or other ceremony configurations for the same recipient
  • Workflow escalation: Begin with one authentication method and escalate to a more direct method (like email) if needed
// POST https://api.signatureapi.com/v1/recipients/rec_123/ceremonies
// X-API-Key: key_test_...
// Content-Type: application/json

{
    "authentication": [
        {
            "type": "email_link"
        }
    ],
    // optional properties: redirect_to, etc ...
}