DocSignerHub
eIDAS Compliant · Legally Binding · Audit Logged

Sign Documents Electronically, Securely

DocSignerHub is an API-first, multi-tenant eSign SaaS. Send documents for signature, track signing status in real time, and integrate with your own systems via our developer API.

Documents Sent
Documents Signed
eIDAS Compliant
< 2 min
Avg Sign Time

How It Works

Four simple steps from registration to a fully signed document.

01

Register & Verify

Create your account and verify your email address to activate your signing portal.

02

Create Merchant

Set up your merchant account to get an API key. Each merchant has a usage limit (default 100 envelopes).

03

Send Envelope

Upload your document, add signers with order and roles, and dispatch the signing envelope.

04

Signer Signs

Signers receive a secure email link, draw their signature, and submit — confirmation email follows.

Everything You Need

Built for developers and businesses who need reliable, legal eSign workflows.

eIDAS Compliant

Meets EU electronic signature regulations for legal validity.

Secure Token Signing

HMAC-secured, expiring, single-use signing tokens per signer.

Multi-Signer Support

Define signer order and roles — each receives their own link.

PDF Stamping

Signature and date automatically embedded into the document.

Audit Trail

Every action logged: portal opened, signed, IP, user agent.

Email Notifications

Signers and senders get confirmation emails on completion.

API-First Design

Full REST API — integrate signing into your own product.

Multi-Tenant

Each merchant has isolated keys, usage limits, and audit logs.

Analytics Dashboard

Real-time charts for user growth, envelopes sent, and document completion trends.

Admin Management

Manage users, roles, and merchant accounts from a secure admin panel.

Document Signature Placeholders (Required)

Your PDF documents must contain these exact placeholder strings so DocSignerHub can locate where to embed the signature and date.

Signature Field

{signature:signer:Please+Sign+Here}

Replace signer with the signer's role value defined in your envelope request.

Date Field

{date:signer:Date+Here}

The signing date is automatically populated when the signer submits.

💡 Tip: The label after the last colon ("Please+Sign+Here") is the placeholder text visible in the document before signing. Use + for spaces.

Integrate in Minutes

DocSignerHub provides a clean REST API. All you need is an API key from your merchant account and you can start sending envelopes from any language or platform.

  1. 1

    Register

    Create a free account at docsignerhub.com/register

  2. 2

    Create Merchant

    Go to Dashboard → Merchant → Create Merchant Account

  3. 3

    Copy API Key

    Your API key appears on the Merchant page. Keep it secret.

  4. 4

    Call the API

    Add the X-Api-Key header to every envelope request.

View Full API Docs
POST /api/envelopes
curl -X POST https://api.docsignerhub.com/api/envelopes \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Employment Contract",
    "merchantId": "YOUR_MERCHANT_ID",
    "documents": [{
      "documentTitle": "Contract",
      "documentFileName": "contract.pdf",
      "documentBase64": "BASE64_CONTENT"
    }],
    "signers": [{
      "name": "John Doe",
      "email": "john@example.com",
      "role": "signer",
      "order": 1,
      "message": "Please sign the contract."
    }]
  }'

Background Architecture

High-level overview of how DocSignerHub processes a document signing request.

User
REST API
Database
Queue
Email
Sign Portal
Storage

Token-Based Signing

Each signer receives a unique HMAC-signed, time-limited URL. Tokens are single-use and expire after a configured window.

Outbox Queue Processing

Emails (signing links, confirmations) and PDF stamping jobs are queued in the OutboxQueue table and processed by a background worker.

Audit Logging

Every action — portal opened, signature submitted, token expired — is appended to the AuditLog with IP address, user agent, and timestamp.

PDF Stamping

When a signer submits, the background stamp worker embeds the signature image and signing date into the PDF at the placeholder coordinates.

Multi-Tenant Isolation

Each merchant has its own API key and envelope quota. Usage is tracked via RequestUsed. At limit, new envelopes are blocked.

eIDAS Alignment

Electronic signatures meet Simple Electronic Signature (SES) requirements under eIDAS. Audit trail supports non-repudiation.

eIDAS Compliance

Built for Legal Validity

DocSignerHub aligns with EU eIDAS guidelines to ensure your signed documents carry legal weight.

Legally Valid Signatures

DocSignerHub produces Simple Electronic Signatures (SES) recognised under EU Regulation No 910/2014 (eIDAS). Signed documents are admissible as evidence in EU member state courts.

Secure Signing Process

Documents are transmitted over TLS. Signing tokens are HMAC-signed and expire. Signed PDF bytes are preserved unchanged after stamping.

Immutable Audit Trail

Every event — invitation sent, portal opened, signature submitted — is logged with timestamp, IP, and user agent to create an irrefutable audit record.

Identity & Consent

Signers authenticate via their email (possession factor) plus optional password. The explicit submit action constitutes informed consent to the document.

* SES (Simple Electronic Signature) under eIDAS Article 3(10). For AES/QES requirements, consult your legal counsel.

Ready to Start Signing?

Create a free account, set up your merchant, and send your first envelope in under 5 minutes.

No credit card required · 100 free envelopes per merchant · Cancel anytime