Automate policy application signing, coverage agreements, claims authorization, and renewal documents. Every completed document is PKCS#7-sealed with a full audit trail — defensible evidence for claims disputes and regulatory review.
New policy application packages — property, auto, life, commercial. Sequential routing ensures applicant signs before the broker countersigns.
Master policy documents, endorsements, and riders. Reusable templates send the same coverage agreement for each new policyholder without re-uploading.
FNOL forms, repair authorization, and release of liability. Webhook completion triggers downstream claims workflow updates automatically.
Annual policy renewal packages and mid-term change endorsements. Automated reminders keep signers on schedule before policy expiry.
Carrier-broker appointment and compensation agreements. Multi-signer routing handles all required signatories across both parties.
Signed acknowledgment of cancellation notices creates a defensible record that the policyholder received and acknowledged the notice.
Generate the policy application PDF from your quoting system. POST to /v1/envelopes with the applicant's details and signature fields pre-placed at the standard signature lines.
POST to /send. The applicant receives a link, verifies identity with OTP, and signs on any device. No printing, no scanning, no branch visit required.
Use sequential routing_order to automatically send the countersignature link to the broker only after the applicant completes. No manual coordination.
envelope.completed webhook fires when all parties sign. Download the PKCS#7-sealed document, update your policy management system, and trigger issuance — fully automated.
Yes, for most insurance documents. Policy applications, coverage agreements, claims authorization forms, broker appointments, and renewal documents are covered by the US ESIGN Act, UETA, and Canada's PIPEDA. Some jurisdictions have specific requirements for life insurance and variable product applications — check NAIC guidelines and state-specific regulations. Consult qualified legal counsel for your specific document types and jurisdictions.
GetSigned captures: explicit e-sign consent (logged with timestamp + IP); OTP identity verification proving the correct person signed; a hash-chained audit log of every event; SHA-256 hashes of the original and final document; and a PKCS#7 digital seal proving the document was not modified after signing. This evidence record is embedded as an audit certificate page in the sealed PDF — so the proof of signing travels with the document, available to adjusters, legal teams, and regulators.
Yes. Generate the application PDF from your quoting or policy system, POST it to the GetSigned API with applicant and broker signer details, and call /send. Sequential routing handles applicant → broker automatically. The envelope.completed webhook fires when all parties sign — trigger document archival, policy issuance, and CRM updates from the webhook payload. No human coordination required between steps.
Yes. For policy types you send repeatedly (auto, home, commercial), define a template once with pre-placed signature fields and roles. Each new policy instance populates the template with the specific policyholder details and sends — without re-uploading the base document. Templates significantly reduce per-envelope setup time for high-volume policy operations.
Retention is configurable per tenant. Many insurance regulations require 5–7 year retention for policy documents. You set the retention period per your regulatory requirements; GetSigned retains documents until that period expires, then purges the PDF blob while retaining the audit trail tombstone permanently. The audit trail (hashes + events) allows you to verify the document's authenticity even after the file is purged.
The signing page shows your brand name and logo by default. Full white-labelling — removing the Powered-by attribution and presenting only your carrier or brokerage brand — is available on the Enterprise plan. This matters in insurance where policyholders should associate the signing experience with your company, not a third-party vendor.
This page is for informational purposes only and does not constitute legal or regulatory advice. Consult qualified legal counsel for insurance-specific e-signature requirements in your jurisdiction.
Related: Compliance guide · E-signatures for finance · Template API · Multi-signer routing
Free tier includes 25 envelopes per month. Full API access, PKCS#7 sealing, and audit trails from day one.
Get free API keys →