With email code authentication, SignatureAPI sends recipients an email containing a 9-digit verification code. Recipients must enter this code to authenticate and access the signing ceremony.
Email code authentication provides an alternative to email link authentication when you need more control over the ceremony URL. Like email link authentication, it authenticates recipients via email, but instead of clicking a link, recipients enter a verification code.It’s particularly useful when:
You want to obtain the ceremony URL to share via your own channels (SMS, app notifications, etc.)
Recipients are in environments where email links might be blocked by security policies
You need to embed the ceremony in your application while still using email-based authentication
You prefer a code-entry workflow over link-clicking for user experience reasons
This method combines email-based authentication with the flexibility of having direct access to the ceremony URL.
The recipient can access the ceremony through various methods:
Clicking a link in an email sent by SignatureAPI (when combined with email link authentication)
Visiting a URL shared through your application (email, SMS, or direct link)
Being redirected from your application
Using an embedded ceremony within your application
Email Verification Process
When recipients access the ceremony, they’ll be prompted to verify their email address:
After clicking the verification button, SignatureAPI sends an email containing the 9-digit verification code:
Test Mode: While in test mode, no emails are sent to recipients. You can view the verification codes that would have been sent in the SignatureAPI dashboard under the ceremony details.
Code Entry and Verification
Recipients must enter the verification code in the ceremony interface:
Once the correct code is entered, recipients can proceed with the signing ceremony: