Recipient object

Here is where you will need to provide an array of JSON objects to define the intended recipient of the document. This array can hold up to 30 recipients and 30 non signer recipients.

Hint For embedded envelopes recipient signers and witnesses can be assigned tags but they are not required. To assign a witness with no tags to a signer, add "witness": {} to the recipient JSON object.

No auth
IDV auth
Copy

Type

This is type of signer.

JSON
Copy
TypeDescription
SIGNERUser to sign and receive confirmation email.
CC

User to receive the confirmation on signing automatically without signing.

  • CC recipients can only have the name and email fields.
  • CC recipients receive the same completion pack as the sender, but do not sign the envelope.
  • CC recipients can be signers and / or witnesses, but the email address must be unique in the pool of CC recipients in the envelope.
  • There can be a maximum of 30 CC recipients, and 30 SIGNER recipients.
  • The number of CC recipients does not impact the limit on SIGNER recipients and visa versa.

Name

This is the name of the signer.

JSON
Copy
  • This must be between 1 and 100 characters.
  • This must not contain special characters: /\:*?<>|

Email

The email specifies the email address of the target recipient. This must be a valid email address (RFC 5322).

JSON
Copy

Roles

This is a string value of role of the recipient, this is free text and can be used to identify the role of the recipient, the maximum length is 50 characters. This must not contain special characters: /\:*?<>|

JSON
Copy

Auth type

This is the level of authorisation you want to set per envelope.

JSON
Copy
Auth typeDescription
no-authA digital signature is required.
sign-authA Yoti scan will be required for this signature. The email_address attribute is added by default to the list of Yoti attributes even if no attributes are provided.
idvAn identity verification session will be required for this envelope. More details can be found here.

If you select sign-auth the the email_address attribute will always be used and a list of additional Yoti attributes that can be used are:

  • full_name
  • date_of_birth,
  • postal_address,
  • gender,
  • nationality,
  • phone_number,
  • photo, - This is a photo of the user
  • photo_auth. - This is to prompt the user to take a selfie of themselves live via the Yoti App as extra level of security.

Example shown below for sign-auth:

JSON
Copy

Sign group

This defines an order in which recipients receive invitations to sign a document. For example, all recipients within sign group 1 will be the first to receive a document to sign. Once all recipients from sign group 1 have signed, the document will be sent to sign group 2. There must be at least 1 sign_group, and the order must be sequential, starting from 1.

Hint Through embedded signing, any required signing order should be controlled entirely by the integrator. It is recommended to utilise webhook notifications to understand when recipients have signed.

JSON
Copy

Note A witness cannot have sign-auth and any such configuration is ignored.

Time zone name

This will effect the date signed field tag, with the relevant timezone. And Must be a TZ database name. This feature is available upon request.

JSON
Copy

Event notifications

This defines the events that trigger email or sms notifications for the recipients. If the event names are included in the array, An email or sms will be sent for that event. If omitted for the standard envelope creation, the signer invitation and envelope completion email notifications will be sent by default. If you include an sms notification, you must also include an email notification. An sms notification requires valid mobile_number and iso_country_code fields.

JSON
Copy
Event typeDescriptionEmbeddedNon-embedded
signer_invitationemail notification is sent to the recipient, informing them to sign.
signer_invitation_smstext message is sent to the recipient, informing them to sign.
envelope_completionemail notification is sent to the recipient, informing that everyone has signed the document.

Excluded files

The documents specified in this array will not appear for the user when they are directed to the signing page. The documents need to be valid documents that have been added to the envelope, and there can't be any tags on the excluded documents.

JSON
Copy

Country code

If the has_envelope_otps is toggled true, Yoti will return a country code in a valid two letter ISO country code format.

JSON
Copy

Phone number

If the has_envelope_otps is toggled true, Yoti will return a valid mobile number.

JSON
Copy

Hint Please ensure the correct country code is used and remove the first digit of the mobile number.

Add a non signing recipient

You can add an email address to the recipient object that the sender creates so that a non signing recipient receives a copy of the completion pack. The non signing recipient (CC recipient) does not receive an invitation to the envelope while it is in an incomplete state.

Once the envelope is complete and all signers have signed then the completion pack email is triggered and are sent to all recipients including non signing recipients.

JSON
Copy
ParameterDescription
TypeType of signer, in this case CC.
NameName of the receipt you want to CC.
EmailEmail of the recipient to be CC'd
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard