Embedded signing infrastructure

Build signatures
into your workflow.
Not around it.

Send, track, and manage legally binding e-signatures from your own app, CRM, or automation. REST API with real-time webhooks. $0.10/request or included with Team.

REST API Real-time webhooks $0.10/request
Architecture Embedded signature flow
1

Your app sends API request

2

VisiSign delivers to signer

3

Signer signs on any device

4

Webhook fires to your system

5

Signed PDF stored with audit trail

webhook: envelope.completed

200 OK

Why embedded

Signing should happen inside your workflow

Not in a separate portal. Not behind a login wall. Not as an afterthought.

×

Context switching kills conversion

Every time you redirect a signer to an external portal, you lose momentum. Embedded signing keeps the experience inside your app or workflow.

×

Standalone signing portals break automation

If your signing tool is not in your stack, every workflow needs manual handoffs. API-first signing removes the gap between "agreement generated" and "agreement signed."

×

API gating is the wrong model

Most platforms lock API access behind enterprise tiers. VisiSign gives you API access from day one. $0.10/request with no monthly fee, or included with Team.

Signing inside your app

Your users sign without leaving your product

Signing happens inline. No redirects, no external portals, no broken flow.

yourapp.com/onboarding
VisiSign embedded signing
Signature
Complete signing

Signing is embedded directly in your application. Your users never leave your product.

Send a signature request

One API call. That is it.

No SDK required. No complex setup. Standard REST with JSON payloads.

# Send a document for signing
curl -X POST https://api.visisign.app/v1/signature_requests \
  -H "Authorization: Bearer vsk_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Service Agreement",
    "signers": [{
      "name": "Jane Smith",
      "email": "jane@example.com"
    }]
  }'

Response

201 Created
id sigreq_4x8a
status sent
signer jane@example.com
webhook: signature_request.sent

REST API

Standard HTTP. JSON in, JSON out. No SDK required.

Templates

Define a document once, send with dynamic data via API.

Signed PDF download

Retrieve the signed document and signing certificate programmatically.

Implementation time

How long does it actually take?

No procurement cycle. No onboarding calls. Just code.

~15 min

First signature request

Create an account, get an API key, send a test signature request from cURL or your app.

~half day

Production workflow

Templates, sequential signing, error handling, signed PDF storage, and end-to-end testing.

Use cases

Where embedded signing fits

Signing becomes a step in your workflow, not a separate tool your team logs into.

SaaS

SaaS onboarding

New customer signs up, your app sends a service agreement automatically. They sign without leaving your product. Webhook confirms completion and you provision their account.

CRM

CRM agreements

Deal closes in your CRM, contract fires via API. The signed PDF attaches back to the deal record. No manual upload. No context switch.

HR

HR onboarding

Offer letters, NDAs, and policy acknowledgments sent automatically when a new hire is created. Sequential signing routes documents through the right people.

Ops

Contractor approvals

Vendor agreements and contractor SOWs sent in bulk from templates. Track status via dashboard or webhooks. Download signed copies programmatically.

API

Field and mobile signing

Waivers, delivery confirmations, and field approvals signed on any device. SMS delivery gets signatures from people who never check email.

AI

AI agent workflows

AI systems that generate contracts, proposals, or agreements can send them for signature via API. The signing step becomes part of the automated pipeline.

Real-time events

Webhooks that close the loop

Your system knows what happened the moment it happens. No polling. No checking back.

signature_request.sent

Document was delivered to the signer

signer.viewed

Signer opened the document

signer.signed

Signer completed their signature

envelope.completed

All signers have signed

signer.declined

Signer declined to sign

// Incoming webhook payload
{
  "event": "envelope.completed",
  "data": {
    "id": "sigreq_4x8a",
    "title": "Service Agreement",
    "status": "completed",
    "signed_pdf_url": "https://...",
    "completed_at": "2026-05-23T14:32:00Z"
  }
}

Pricing model

API access is not a premium feature

Most e-signature platforms treat API access as an enterprise upsell. You want to automate? Pay for a higher tier. You want webhooks? Talk to sales.

VisiSign gives you API access from day one. $0.10/request with no monthly fee, or included with the $49/month Team plan. No contracts. No minimums. No sales calls.

$0.10

per API request

$0

monthly API fee

No

contracts required

500

included with Team

Integrations

Works with your stack

Standard REST and webhooks mean VisiSign fits anywhere. Here are some common patterns.

Automation

n8n

Community node with action and trigger support. Send contracts, react to signing events, download signed PDFs.

View n8n integration
CRM

Pipedrive

Send contracts when deals move stages. Signed PDFs attach to the deal automatically. Marketplace app available.

View Pipedrive integration
Database

Supabase / Postgres

Database trigger fires an edge function that calls VisiSign API. Webhook writes the result back. Full loop, no middleware.

View API docs
CRM

HubSpot

Workflow action sends a signature request when a deal closes. Webhook updates the contact record and attaches the signed PDF.

View API docs

Add signing to your product today.

Create an account, get an API key, and send your first signature request in minutes. No procurement. No sales calls.