Signature Requests are the primary method to initiate the signing process on the IgniSign platform.
Users can easily create a signature request using the IgniSign Console Or through API.

The process involves selecting a Signature Profile, entering a title and description, providing signer information, and uploading documents to be signed.
The Signer can also ask for a document to someone else (Document Request principle),
or associate some statements to a document or globally to a signature request( the signer need to check these statements before be able to sign the document).

Once the request is created:

• if the Integration Mode is By Side an email is sent to the signer inviting them to participate in the signature session.
• if the Integration Mode is Embedded the information to initiate the signature session with the IgniSign JS SDK are sent through a Webhook Event
  
  

Create a Signature Request

You can create a signature request using the IgniSign Console or through the API.

Signature Request Creation Api Life Cycle

You can find below a sequence diagram that describe the signature request creation process.

API calls used to create Signature Requests

Global Signature Request calls

• Initialize a Signature Request
• Update a Signature Request
• Publish a Signature Request

Signers related api calls

• Get Signer Creation Constraints
• Create a Signer

Document related calls

• Initialize a Document
• Provide Document Content - File or PDF
• Provide Document Content - Data Json
• Provide Document Content - Private file
• Create a Document Request

Signature sessions are an integral part of the IgniSign electronic signature platform. When a user initiates a signature request, the recipient receives an email inviting them to sign the provided document. Upon clicking the link in the email, the recipient is redirected to the signature page, marking the beginning of a signature session. This session ensures that the signer has a seamless experience while signing the document. The session's integration mode can either be "By Side," where IgniSign manages the entire process, or "Embedded," where the signature process is integrated directly into the user's application. The choice of integration mode can be defined in the Signature Profile.

• if the Integration Mode is By Side an email is sent to the signer inviting them to participate in the signature session.
• if the Integration Mode is Embedded the information to initiate the signature session with the IgniSign JS SDK are sent through a Webhook Event
  
  

During the signature session, a Identification Session and An Authentication Registration Session can be Initialized if the signer does not match the requierement regarding the claims of the signature profile.
This mechanism is fully managed by Ignisign, You don't have anything to do on this part.

Once this first phase is finished, the signer is invited to review documents, check statements, and sign the document.
If an Authentication is required, the signer will be invited to authenticate himself before being able to sign the document.
Once finalized, a confirmation is provided to the signer, and the signature session is closed.

If the signature mechanism failed(unexpected error - should not happens), the signature session is closed and the signer is invited to retry the signature session. the signatures session is set as FAILED and a webhook is triggered

A Signature Request is a request to sign a document.