The Simple Electronic Signature (SES) covers most day-to-day use cases. The Signer receives a link, reviews the Document, confirms their identity with an optional one-time password, and signs from any device.

Unlike the Advanced eSignature and the Qualified eSignature, the SES involves no identity document verification. It is also the only level compatible with every signing interface, including one you build yourself.

Set the SES level on a Signer

The signature level is set for each Signer, with the signature_level property.

Use the value electronic_signature for the Simple eSignature in the endpoint Create a new Signer (POST /signature_requests/{signatureRequestId}/signers).

Signers of the same Signature Request can have different signature levels. You can mix SES and AES Signers in a single Signature Request. QES Signers cannot be mixed with other levels.

Authenticate your Signers

The SES is the only signature level that accepts the three authentication modes. Set the mode for each Signer with the signature_authentication_mode property.

Authentication by SMS is not available for phone numbers in China and is restricted to a limited list of countries during the free trial period.

→ Read the guide: Authentication mode
→ See also: Custom One-Time Password (OTP) SMS

Choose your signing interface

The SES is the only signature level compatible with all four options:

Signature link delivered via email by Youtrust. Youtrust sends the invitation and the reminders. This is the default behaviour.
→ Read the guide: Manage signature link delivery

Signature link delivered by you. You retrieve the signature link and distribute it through your own channels.
→ Read the guide: Manage signature link delivery

Signature interface embedded in an iFrame. You embed Youtrust's signing interface inside your application.
→ Read the guide: Embedded Signing

Custom-made signature interface. You build the whole signing experience and drive the signature through the API. This option is available for SES Signers only, and the Signature Request delivery_mode must be set to none.
→ Read the guide: Custom Signing Flow

If your Signers have several Documents to sign, you can also give them access to the Signature Portal.

Test the SES in Sandbox

The SES behaves in Sandbox exactly as in production, with no activation step and no identity verification: create your Signature Request with a Sandbox API key, then run the full signing flow.

Retrieve the proof of the signature

An Audit Trail is generated for each Signer as soon as they sign and stored for 10 years. It gathers the information collected during the signing process, including the authentication mode used if any.

• Endpoint: Download Audit Trail PDF
• Endpoint: Get Signer Audit Trail for the JSON version

→ Read this guide for more info: eSignature Audit trail