Embedded envelope
To see the flow of a standard envelope request please try out our demo here, switch our toggle on for embedded signing. We break down each section throughout the documentation so do continue reading.
Having an embedded flow means you can have your own branding and white label our solution.
The steps are:
Generate envelope.
Launch the envelope.
Complete signing request.
Redirect the user once the envelope is signed.
Important Authentication is important. Please ensure that any user signing through the embedded version are authenticated. You can do this by validating the email address or doing an IDV check on the user.
These endpoints allows you to create an envelope request by sending one or more documents:
Sandbox
Production
Below is an example of the full request for creating an envelope.
Event Notifications
Event notifications must be present for embedded envelopes. An empty array means an event notification will not be sent. Accepted notifications are "signer_invitation" or "envelope_completion". These are for the recipient, who will receive an email notification from these events.
Example code
Expected response
On success Yoti returns a 200 and a JSON object in the following format:
This envelope ID will be used to view the envelope status and retrieve the completed signed document.
Launch envelope
To launch an embedded envelope, render it using one of the following URLs.
The example below demonstrates the use of an iframe:
Error codes
Error code | Description |
|---|---|
400 | Bad Request, example: id provided not a UUID |
401 | Unauthorised request, example: requesting the status on an envelope you are not authorised to view |
403 | Forbidden, requesting user did not create the envelope |
413 | The combined file sizes have exceeded the 20MB limit |
422 | The request body did not pass validation |
Got a question? Contact us here.