SignatureAPI now supports Email Code Authentication, a new way to verify recipients before they access a signing ceremony. It complements the existing Email Link and Custom Authentication methods and is particularly useful when you want to control how the ceremony URL itself is delivered.
What It Does
With Email Code Authentication, SignatureAPI sends the recipient a 9-digit verification code by email. The recipient enters that code on the ceremony page to prove they control the email address, and then proceeds to sign. Unlike Email Link Authentication, the ceremony URL is returned to you in the API response so you can deliver it through your own channels.
This is a good fit when:
- You want to send the signing link by SMS, push notification, or in your own application.
- Recipients are in environments where email links may be filtered or stripped.
- You want to embed the ceremony in your product while still tying access to a verified email.
Email code is the third supported authentication type and can be combined with Custom Authentication for multi-step verification.
How to Use It
Specify email_code in the ceremony’s authentication array when creating an envelope or calling the Create Ceremony endpoint:
{
"authentication": [
{
"type": "email_code"
}
]
}The response includes the ceremony URL in the url property. Deliver that URL however you like. When the recipient opens it, they will be prompted for the 9-digit code that was emailed to them. The authentication event is recorded in the envelope’s audit log alongside the timestamp, so the verified access is preserved in the signed record.
For more details, see the Email Code Authentication documentation.
