FAQ

Verdocs lets developers build embedded eSignature and document workflow experiences directly inside their own applications. You can use Verdocs to create or import templates, map fields and roles, send envelopes for signature, embed signing flows, receive webhook updates, and route completed signed PDFs and audit trails back into your own system of record. Verdocs is especially useful for product teams that want eSignature to behave like a native product feature rather than a separate third-party signing portal.

Yes. Verdocs is built for software companies, vertical SaaS platforms, ISVs, and product teams that want to embed eSignature into their own workflows. Instead of forcing users into a standalone signing application, Verdocs gives developers APIs, SDKs, and Web Components to create branded, application-native signing experiences. That makes it a fit for platforms that want to bundle, monetize, or resell eSignature as part of their own product.

Yes. Verdocs supports embedded signing so users can review, complete, and sign documents inside your application experience. Developers can use Verdocs Web Components and hosted embeds to create a signing flow that aligns with their product UI, styling, and domain strategy. This helps reduce user friction, preserve brand trust, and keep document execution inside the workflow your users already know.

Yes. Verdocs supports white-labeling, but it is important to think of white-labeling as a spectrum rather than a single on/off feature. In an embedded eSignature workflow, branding can touch multiple parts of the signer experience, including the disclosure acceptance flow, email notifications, signing interface, post-signing experience, completed documents, and digital certificate. Verdocs gives software platforms the flexibility to decide how much of the experience should be branded as their own. Some customers may only need an embedded signing flow that matches their application’s UI. Others may want deeper control over signer-facing emails, redirect URLs, disclosure language, certificates, and the overall workflow. Verdocs is designed to support these different levels of white-labeling based on the needs of the platform, the use case, and the end-customer experience.

Yes. Verdocs is well suited for SaaS platforms that support multiple customers, workspaces, teams, or end clients. Developers can design workflows where each customer has its own templates, branding, roles, routing, and usage patterns while the host application remains the primary user experience. This is particularly valuable for insurance, financial services, legal, accounting, HR, real estate, and other document-heavy vertical platforms.

Create a Verdocs account and use the Developer Center and API Dashboard to start building. Verdocs provides Resource Owner API access, REST API documentation, SDKs, Web Components, and implementation guides for creating and sending templates, embedding signing, and receiving status updates. API credentials should be treated as server-side secrets and should not be exposed in client-side code.

Verdocs does not use a separate API sandbox environment. Instead, the Basic Plan gives developers access to a production account with full access to most API capabilities, plus unlimited test documents. The Basic Plan includes 25 envelopes per month, 5 templates, webhooks, the web platform, Resource Owner API access, Verdocs Auth, customizable and hosted embeds, embeddable Fill & Sign, embedded search, embedded editor, embedded template preview, and the API Dashboard. KBA and SMS are add-ons that are generally enabled through a paid plan or sales-supported setup.

Because Verdocs gives developers access to a production-capable account from the start, moving to production is less about migrating from a sandbox and more about completing your go-live checklist. Before launch, confirm your plan and envelope volume, finalize templates and field mappings, configure embedded signing and post-signing pages, choose your email notification strategy, validate webhook handling, enable any required recipient authentication methods such as SMS or KBA, and confirm where completed PDFs and audit trails will be stored in your application.

Verdocs provides REST API documentation, an OpenAPI-powered API reference, JavaScript/TypeScript SDKs, Web Components, and framework-friendly front-end components for React, Angular, Vue, and vanilla JavaScript. The JavaScript/TypeScript SDKs are designed for both browser and server-side applications, and Verdocs’ SDKs are open source under the MIT license. Developers should use the Developer Center for API reference material, guides, embeds, SDK documentation, and implementation examples.

Webhooks let your application react to signing activity without constantly polling the API. Use webhooks to update envelope status, trigger downstream workflows, notify internal users, sync data back to your application, and store completed signed PDFs and audit trails. At minimum, your webhook implementation should handle key lifecycle events such as sent, viewed, signer completed, envelope completed, declined, expired, canceled or voided, and authentication or recipient-action failures where enabled.

Completed Verdocs documents are designed to be legally binding, tamper-proof, and supported by a detailed audit trail. Verdocs electronic signatures are E-SIGN Act and UETA compliant, use PKI-based digital signatures, and include an audit log showing when and where a document was signed and by whom. Completed documents and certificates can include document, recipient, and event-history details, helping developers preserve the evidence package required for regulated document workflows.

Verdocs is designed around usage-based pricing for software platforms and high-volume workflows. Rather than forcing every customer into seat-based pricing, Verdocs aligns cost to envelope consumption so teams can start small, scale usage over time, and preserve margin when bundling or monetizing eSignature inside their product. For software publishers that want to white-label or resell eSignature, Verdocs also supports platform pricing designed for partner and ISV business models.