gitlabEdit

โœ๏ธeSign Dispatch

Learn how to send documents for electronic signature through Docs-Dispatcher with Universign, Signaturit, and Yousign.

Overview

This recipe covers:

  1. Sending documents for signature

  2. Multiple signature providers (Universign, Signaturit)

  3. Signature workflows (simple, advanced, qualified)

  4. Multiple signers and signature order

  5. Webhooks for signature events

  6. Complete examples in 4 languages

What You'll Learn

  • Structure eSign dispatch requests

  • Configure signature workflows

  • Add multiple signers

  • Handle signature events

  • Provider-specific features

  • Complete working examples

Prerequisites

  • Docs-Dispatcher account with JWT

  • eSign provider configured (Universign, Signaturit, or Yousign)

  • Template created

  • Basic REST API knowledge

eSign Service Overview

Supported providers:

Provider
Signature Types
Multi-signer
Qualified Signature

Universign

Simple, Advanced, Qualified

โœ…

โœ…

Signaturit

Simple, Advanced

โœ…

โŒ

Yousign

Simple, Advanced

โœ…

โŒ

Step 1: Authentication

Dispatcher API uses HTTP Basic Authentication. You'll need your Dispatcher account email and password for all API calls.

Setup Credentials

circle-info

No token management needed! Unlike JWT-based APIs, Basic Auth doesn't require separate authentication endpoints or token refresh. Your credentials are sent with each request.

Quick links:

Step 2: Prepare eSign Request

Basic eSign Structure

Required Fields

Field
Type
Description

providerName

string

universign, signaturit, or yousign

template.id

number

Template ID for document

esign.documentName

string

Document display name

esign.signers

array

List of signers (min 1)

esign.signers[].email

string

Signer email address

Signature Types

Type
Description
Legal Value
Provider Support

SIMPLE

Basic e-signature

Low

All

ADVANCED

EU eIDAS compliant

Medium

All

QUALIFIED

Highest legal value

High

Universign only

Step 3: Send for Signature

Single Signer Request

Success Response:

Multiple Signers with Order

Step 4: Handle Signature Events

Webhook Events

Signature providers send webhook notifications for:

  • signature_pending - Document sent for signature

  • signer_viewed - Signer opened the document

  • signer_signed - Individual signer completed

  • signature_completed - All signers completed

  • signature_declined - Signer declined to sign

  • signature_expired - Signature period expired

Webhook Payload Example

Webhook Handler (Node.js)

Complete Examples

curl (Complete Flow)

Node.js (Complete Flow)

PHP (Complete Flow)

Java (Complete Flow)

Provider-Specific Features

Universign

Unique features:

  • Qualified signatures (highest legal value)

  • Advanced certificate options

  • French market leader

Signaturit

Unique features:

  • Multi-language support (30+ languages)

  • Certified email integration

  • SMS authentication

Yousign

Unique features:

  • Affordable pricing

  • Simple API

  • EU-based

Best Practices

1. Set Reasonable Expiration

2. Use Sequential Signing When Order Matters

3. Implement Reminders

Error Handling

Common Errors

Invalid Signer Email

Signature Type Not Supported

Next Steps

Summary

You've learned:

  • โœ… Send documents for electronic signature

  • โœ… Configure multiple signers and order

  • โœ… Handle signature events via webhooks

  • โœ… Provider-specific features

  • โœ… Complete implementations in 4 languages

Electronic signatures streamline contract workflows!

Last updated