Resources

Guides & resources

Everything you need to add legally binding e-signatures to your product — from API basics to language-specific tutorials and honest comparisons.

Guides

What is an e-signature API?

A plain-English explanation of e-signature APIs and how the signing lifecycle works.

Read →

Are electronic signatures legally binding?

PIPEDA, ESIGN, and UETA — and the four elements of an enforceable e-signature.

Read →

E-signature audit trail explained

What a tamper-evident audit trail contains, how PKCS#7 sealing works, and what to look for.

Read →

Multi-signer e-signatures

Sequential routing, parallel signing, and mixed workflows — controlled by routing_order.

Read →

Embedded signing

Render the signing UI inside your product with an iframe — no email redirect, same audit trail.

Read →

E-signature template API

Define a document once with signer roles and pre-placed fields, then send it on demand.

Read →

Bulk send documents

Send the same document to hundreds of recipients — each gets an independent envelope.

Read →

E-signatures for SaaS

Integration patterns, multi-tenant isolation, webhooks, and white-labeling for SaaS products.

Read →

E-signatures for startups

Ship signing features in hours with the free tier — no credit card, no sales call required.

Read →

E-signature API vs SDK

When to call the REST API directly vs. using an SDK — and why the API usually wins.

Read →

Electronic signature vs digital signature

The difference between the two terms — PKI, PKCS#7, and what the law actually requires.

Read →

E-signatures for real estate

Which property documents can be e-signed under ESIGN/UETA, and which cannot.

Read →

E-signatures for HR

Offer letters, NDAs, and onboarding documents — legally valid and automatable via API.

Read →

E-signatures for law firms

NDAs, engagement letters, settlement agreements, and retainer contracts — legally defensible.

Read →

E-signatures for finance

Loan agreements, investment docs, and account opening forms — audit trail meets ESIGN/UETA.

Read →

E-signatures for insurance

Policy applications, claims forms, and coverage agreements — automated from application to issuance.

Read →

E-signature compliance guide

PIPEDA, ESIGN Act, and UETA explained — what the law requires and what GetSigned captures.

Read →

E-signature retention policy

How long to keep signed documents by industry, and what GetSigned retains after a purge.

Read →

Online document signing

No printing, no scanning — signers get a link, sign on any device, you get a sealed PDF.

Read →

E-signatures for nonprofits

Grant agreements, board resolutions, and volunteer waivers — free tier for low-volume orgs.

Read →

E-signatures for government

Permits, interagency agreements, and procurement contracts under ESIGN/PIPEDA.

Read →

Digital signature API

PKCS#7 sealing on every document — how it works, how to verify, and how it differs from e-signatures.

Read →

eSign API

OAuth2, endpoints, and key features — the quick-start product overview for developers.

Read →

API for collecting signatures

Upload any PDF, declare signers, send — receive a sealed document via webhook.

Read →

Secure document signing

TLS, AES-256, OTP, PKCS#7, hash-chained audit log, HMAC webhooks — eight security layers.

Read →

E-signatures for education

Enrollment agreements, parental consent, financial aid docs, and IRB forms for schools and EdTech.

Read →

Document signing API

Sign any PDF via REST — upload, place fields, send, receive a PKCS#7-sealed document.

Read →

PDF signature API

How the PDF signature API works, what field types are supported, and how to verify the seal.

Read →

Contract signing API

Send any contract for legally binding signature in 3 API calls — multi-party routing included.

Read →

Signable PDF API

Upload any PDF, place fields, send — get back a PKCS#7-sealed tamper-evident document.

Read →

Best e-signature APIs for developers

How to choose an e-signature API, plus a balanced look at the main options.

Read →

Developer how-tos

Add e-signatures to your app

The four-step REST integration, language-agnostic, with curl examples.

Read →

Add e-signatures in Node.js

Integrate signing in a Node 18+ app with fetch and Express — no SDK.

Read →

Add e-signatures in Python

Integrate signing with the requests library and a Flask webhook.

Read →

Add e-signatures in PHP

Integrate signing using PHP's built-in cURL extension — no Composer package needed.

Read →

Add e-signatures in Go

Integrate signing using only Go's standard library — net/http and mime/multipart, zero deps.

Read →

E-signature webhook guide

Which events are fired, how to verify HMAC signatures, and how to build an idempotent handler.

Read →

Add e-signatures in Ruby

Net::HTTP and multipart-post — full Rails and Sinatra webhook handler included.

Read →

Add e-signatures in Java

Java 11 HttpClient — zero extra deps, Spring Boot webhook controller included.

Read →

Add e-signatures in C# (.NET)

HttpClient + MultipartFormDataContent — ASP.NET Core minimal API webhook handler.

Read →

Add e-signatures in Rust

reqwest + tokio multipart upload — Axum webhook handler with HMAC-SHA256 verification.

Read →

Add e-signatures in Kotlin

OkHttp + Gson + coroutines — works on Spring Boot, Ktor, Micronaut, and Android.

Read →

Add e-signatures in Swift

URLSession + CryptoKit only — zero dependencies. Works on iOS, macOS, and server-side Swift.

Read →

Add e-signatures in Dart / Flutter

http + crypto packages — works on Flutter mobile, web, desktop, and server-side Dart.

Read →

Add e-signatures in Elixir

Req + Jason + Erlang :crypto — works with Phoenix, Plug, or any OTP application.

Read →

Comparisons

Start building with the free tier

Get free API keys →