The eSignature API built for agency management systems.
If you build the platform that agencies run on, signing should live inside it: your brand, your domain, your data. Verdocs is the embedded signing layer behind insurance platforms, with every agency in your book getting its own branded experience.
The paperwork your AMS already carries
Policy applications and binding
Applications, endorsements, and renewal packets signed inside the AMS record they belong to, with fields pre-filled from your data.
Producer and carrier onboarding
E&O acknowledgments, producer agreements, and carrier appointment paperwork routed and tracked without leaving your platform.
Claims and authorizations
Signatures with identity assurance that scales to the stakes, from an emailed link up to knowledge-based authentication.
What integration means when you are the system of record
Your AMS stays the system of record. Verdocs never becomes one. Signing is an API call from your backend and a component in your front end, so there is no document migration, no parallel store to reconcile, and no rip and replace of anything an agency already uses.
Your record fills the document
Create the envelope from your template with the fields already populated from the AMS record. The signer corrects what is wrong instead of retyping what is right.
Signing renders in your interface
Web components, not iframes: override any control, style with standard CSS. The agency sees your product, not a signing portal, and the policyholder never leaves the page they trust.
Your record hears back
A webhook fires the moment a recipient opens, signs, or declines. The signed PDF, the certificate, and the audit trail return through the API, into the file they belong to.
Each step in detail, including how an existing fillable ACORD form becomes a template: fill, sign, write back. The same three calls in React, with the component API: embed signing in a React app. When an AI agent fills the packet instead of a person: where human approval still counts.
Every agency in the book, under its own brand
One platform, many agencies, and none of them want a vendor they have never heard of appearing in front of their policyholders. 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.
Build
Agencies build and edit their own templates inside your product. The builder ships as white-label components, the same way the signing does.
Notify
Requests and reminders send from the agency's own domain and sender name. In the policyholder's inbox, neither you nor Verdocs has to appear.
Sign
The signing page carries the agency's logo, colors, and domain, rendered inside your platform rather than on a portal the policyholder has to go and find.
Prove
Disclosures, signing certificates, and tamper-evident audit trails carry the agency's brand from consent to completion.
What multi-tenant signing requires across a distribution network, down to the notification senders.
Assurance that matches the document
A renewal acknowledgment and a total-loss settlement release should not prove the same thing or cost the same to send. Set the authentication level per document type and per recipient, from a simple emailed link up to knowledge-based authentication and live ID scans. Every step a signer clears is recorded in the same audit trail as the signature, so the evidence reflects the assurance actually applied.
KBA and ID scan are per-transaction add-ons; see pricing.
Common questions from AMS teams
Do we have to move our documents into Verdocs?
No. Your AMS stays the system of record. Verdocs creates the envelope, renders the signing, and returns the signed PDF, the certificate, and the audit trail through the API. Nothing is migrated, and agencies never get a second place to log in.
Can each agency have its own branding, including the emails?
Yes. White-label operates at the multi-tenant level: each agency in your book gets its own logo, colors, domain, and email sender on every document it sends. The notification sender is where partial implementations usually break, so it is the part worth testing first.
What does it cost as we add agencies?
There are no per-seat fees. You pay for envelopes and the identity add-ons you use, and every plan includes the whole platform: no user limits, no template limits, no feature ladders.
How long does the integration take?
Live in 1-2 business days. What has to exist on your side is a template, a call that creates the envelope from your record, and an endpoint that receives the webhook.
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.
See how insurance platforms run signing on Verdocs on the insurance page, or model the economics in the ROI calculator.