Signing

Create, send, and sign documents

Build signing flows around reusable templates, generated documents, embedded signing, and audit-ready completion. Use Korala for straightforward e-signature workflows or as the signing layer inside a broader document process.

NDA — Acme Corp
doc_a1b2c3d4
Awaiting signatures
Client
Signature pending...
Sender
Signature pending...
J
Jane Smith
jane@acme.com
J
John Doe
john@company.com
RFC 3161 Certified
DigiCert TSA · X.509
Audit trail
3 events logged
Templates
Create reusable documents with signer roles
Generate
Fill documents from product or CRM data
Embed
Bring signing into your own experience
Audit
Finish with certificates and timestamps
Document Flows

Start from reusable templates and send documents with context

Korala signing is more than drawing a signature on a PDF. Create a reusable document model, prefill it with live data, define who signs where, and keep the flow consistent every time.

Reusable templates
Define signer roles, fields, and document structure once, then reuse the same template across every transaction.
Signer roles and placeholders
Repeatable field layouts
Brand-ready document setup
Document generation
Create ready-to-sign documents by merging your own customer, deal, or case data into templates.
Prefill from your systems
One-off or repeatable generation
Clean PDF output
Signer orchestration
Route the document through the right people, track who is pending, and keep everyone on the same version.
Multi-signer support
Role-based routing
Status tracking and reminders
Signing Experience

Let the signing flow play out in motion

The strongest proof for signing is seeing the document move from draft to completed state. Korala keeps the document, signer progress, and compliance artifacts connected in one flow.

Signer progress and completion states
Embedded or link-based signing flows
Completion with audit trail and certificate data
NDA — Acme Corp
doc_a1b2c3d4
Awaiting signatures
Client
Signature pending...
Sender
Signature pending...
J
Jane Smith
jane@acme.com
J
John Doe
john@company.com
RFC 3161 Certified
DigiCert TSA · X.509
Audit trail
3 events logged
Use Cases

Support standalone e-signature or deeper document workflows

Some teams only need fast document signing. Others generate documents from templates, feed them from product data, and use signing as the final step. This page supports both shapes.

Sales and contracts
Generate agreements from deal data and keep signers, completion state, and final artifacts in sync.
Internal approvals
Route internal documents through approvers without leaving the same signing and audit model.
Embedded product flows
Add signing directly into your own onboarding, contracting, or operations experience.
For Developers

Create documents and track signing from one integration

Templates, generated documents, signing state, and downstream events all stay inside the same API model.

Create documents from reusable templates
Send for signature or embed the signing UI
Handle completed, declined, and downloaded events
01
Create a document from your template
korala.documents.create({ templateId, data, signers })
02
Share the signing flow
document.signingUrl / embedded signing component
03
Sync your system on completion
document.completed -> webhook handler
sign-document.ts
typescript
import Korala from "@korala/sdk";

const korala = new Korala({ apiKey: process.env.KORALA_KEY });

const document = await korala.documents.create({
  templateId: "tmpl_master_services_agreement",
  data: {
    companyName: "Acme Corp",
    effectiveDate: "2026-03-27",
  },
  signers: [
    { name: "Jane Smith", email: "jane@acme.com", role: "client" },
    { name: "John Doe", email: "john@korala.ai", role: "sender" },
  ],
});
Trust & Compliance

Every completed signature should come with proof

Signing is only useful when the result is defendable. Korala keeps signer state, timestamps, certificates, and audit history attached to the final document.

RFC 3161 timestamps
Attach long-term timing proof to the final signed artifact.
Certificates and audit trail
Keep document completion evidence visible and exportable.
Embedded delivery options
Use the same signing core in product-led or ops-led flows.
API-first control
Create, send, and monitor signing flows through the same developer surface.
Pricing

Pricing for document signing and API-based document flows

Use standalone signing plans for straightforward signature workflows, or move into API Platform pricing when documents, fills, and signing events are part of a larger product flow.

Signing is the simple path for template-driven document execution. API Platform pricing covers higher-volume document generation, fills, signing events, and orchestration.

Signing
Popular signing plan: Starter
For simple signing workflows
$29/month
50 signed docs/month
Unlimited senders
Reusable templates + reminders
Branding + webhooks
API Platform
Usage starts at $0.20
Usage-based production access
$0.20/document
100 free docs/month
$0.05/template fill
$0.60/signing event
Sessions + workflows as usage grows

Ship document signing that feels complete

Start with reusable templates, generate documents from live data, and finish with signatures, timestamps, and audit-ready output.