Policyholders sign where the policy lives: in your portal.
Embedded signing for policy issuance, claims intake, endorsements, and producer onboarding. Built for insurtech and core-system platforms; HIPAA compliant where claims and health authorizations demand it.
Building an agency management system? See the AMS-specific workflows.
Domain or work email: either way you get a branded account. No credit card, no sales call.
Just need an API key? Create a plain account
The four signing workflows every insurance platform carries
Claims intake and authorization
Capture FNOL forms, medical authorizations, and releases inside your claims workflow, with KBA or ID scan where the file demands it.
Policy issuance and binding
Send, sign, and finalize new business and renewal documents without the policyholder ever leaving your portal.
Endorsements and amendments
Route mid-term policy changes and approvals to the right parties, in order, with live status back to your system.
Agent and broker onboarding
Manage E&O acknowledgments and producer agreements across your distribution network, every agency under its own brand.
The entire journey, under your control
The policyholder starts an action in your portal: a claim, an endorsement, an enrollment.
Fields arrive populated from your policy data. No rekeying, no transcription errors.
They sign inside your portal, on your domain, in your brand. No redirect, no foreign UI.
Your webhook fires the moment they open, sign, or decline. Status lives in your system.
The tamper-evident PDF, certificate, and audit trail store in your document center.
Identity assurance that scales with the stakes
A renewal acknowledgment is not a total-loss settlement. Layer recipient authentication per document, from a simple emailed link up to knowledge-based authentication and live ID scans.
KBA and ID scan are per-transaction add-ons; see pricing.
Endorsements, FNOL packets, producer agreements: one API shape.
Web components, not iframes: override any control, style with standard CSS. MIT-licensed SDKs on GitHub and npm. Live in 1-2 business days.
// 1. Create an envelope from your template
const envelope = await verdocs.envelopes.create({
template_id: 'engagement-letter',
recipients: [{ role: 'signer', email: client.email }],
fields: { client_name: client.name }, // pre-filled, still editable
})
// 2. Render signing inside your app
<VerdocsSign envelopeId={envelope.id} theme={yourBrand} />
// 3. Know the moment it completes
app.post('/webhooks/verdocs', ({ body }) => {
if (body.event === 'envelope.completed') fulfill(body.envelope_id)
})Every agency and MGA under its own brand
White-label works at the multi-tenant level: each agency, broker, and program in your distribution network gets its own logo, colors, domain, and emails on every document it sends.
Every tenant, their own brand
White-label works at the multi-tenant level. Each of your customers gets a branded experience: their logo, their colors, their domain, their emails. Not yours, and never ours.
Own the SKU
Package, price, and sell signing as part of your product. Usage-based platform pricing leaves the margin, and the customer relationship, with you.
Aligned by design
We sell through you, not around you. Your success selling downstream is the business model, so partner support is the product, not a program.
Common questions from insurance platforms
Do policyholders need Verdocs accounts to sign?
No. Recipients sign without creating accounts, with authentication layered to the risk of the document: from emailed links up to MFA, knowledge-based authentication, and live ID scans for high-stakes files like total-loss settlements.
Is embedded signing appropriate for claims and health authorizations?
Yes. Verdocs is HIPAA compliant and SOC 2 Type I attested, and every document carries a tamper-evident seal, a digitally signed certificate, and a full audit trail suitable for claims files.
Can each agency in our network have its own branding?
Yes. White-label operates at the multi-tenant level: each agency, broker, or program gets its own logo, colors, domain, and email sender on every document it sends.
More questions? The full FAQ lives in the developer docs, from API auth and webhooks to eIDAS signature levels.
Compliance the file room can live with.
SOC 2 Type I · HIPAA compliant · ESIGN & UETA · eIDAS SES / AES · GDPR. Legally valid in 50+ countries and 60+ jurisdictions. KBA and ID scan available per transaction where carriers require identity assurance.