# FAQ (/docs/learn/FAQ)




<div className="flex flex-col align-start faq-section">
  ## Getting Started & Platform Overview [#getting-started--platform-overview]

  <FAQEntry learn="{text: 'View the quick start guide.', path: '/docs/guides/getting-started'}" question="What can I build with the Verdocs API?" answer="&#x22;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.&#x22;" />

  <FAQEntry learn="{text: 'View our complete component library', path: '/docs/reference/SDK/web/components'}" question="Is Verdocs designed for embedded/OEM eSignature use cases?" answer="&#x22;Yes. Verdocs is built for software companies, vertical SaaS platforms, ISVs, and OEM partners that want eSignature to ship as part of their own product, not as a separate signing portal users must visit. That includes platforms that bundle signing into a workflow, monetize it per envelope, or resell it under their own brand. Verdocs provides the APIs, SDKs, and multi-tenant organization model these business models require. For how signers experience embedded signing in your UI, see the Signer Experience & Embeds section below.&#x22;" />

  <FAQEntry learn="{text: 'See the guide for organization hierarchies', path: '/docs/guides/tutorials/organization-hierarchies'}" question="Does Verdocs support multi-tenant SaaS platforms?" answer="&#x22;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.&#x22;" />

  <FAQEntry learn="{text: 'Start with the developer quick start and testing guide.', path: '/docs/guides/getting-started'}" question="Does Verdocs have a sandbox or test mode?" answer="&#x22;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.&#x22;" />

  <FAQEntry learn="{text: 'Review our product demo.', path: 'https://www.youtube.com/watch?v=cdLn_2oS8ow'}" question="How do I move from development to production?" answer="&#x22;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.&#x22;" />

  <FAQEntry learn="{text: 'Explore Verdocs SDKs, Web Components, and the API reference.', path: '/docs/reference'}" question="What SDKs, OpenAPI specs, and developer tools are available?" answer="&#x22;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.&#x22;" />

  <FAQEntry learn="{text: 'View pricing or contact Verdocs for volume/API pricing.', path: 'https://verdocs.com/pricing/apiplans/'}" question="How does usage-based pricing work for API customers?" answer="&#x22;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.&#x22;" />

  ## Authentication & API Keys [#authentication--api-keys]

  <FAQEntry learn="{text: 'Read the API documentation for API Key routes.', path: '/docs/reference/Rest-API/api-docs/api-keys/createApiKey'}" question="How do I get API credentials?" answer="&#x22;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.&#x22;" />

  <FAQEntry learn="{text: 'Create an API key and authenticate', path: '/docs/reference/Rest-API/api-docs/authentication/authenticate'}" question="How do I authenticate server-to-server API calls?" answer="&#x22;Create an API key in the Developer Center or via the API, then exchange the key's client ID and secret for a short-lived bearer token using the OAuth2 client credentials grant. Send that token in the `Authorization: Bearer` header on subsequent REST calls. Treat client secrets as server-side credentials only, never embed them in browser code or mobile apps.&#x22;" />

  <FAQEntry learn="{text: 'Rotate an API key; update webhook config', path: '/docs/reference/Rest-API/api-docs/api-keys/rotateApiKey'}" question="How do I rotate API keys or webhook secrets without downtime?" answer="&#x22;Create or rotate a new API key, deploy the new client secret to your servers, verify traffic with the new credentials, then revoke the old key. For webhooks, generate a new HMAC secret in the webhook settings, deploy the verifier that accepts both secrets during a short overlap window, then remove the old secret. Rotate on the same cadence as database passwords and CI secrets.&#x22;" />

  <FAQEntry learn="{text: 'Review REST API reference and webhook guide', path: '/docs/reference/Rest-API'}" question="Are there API rate limits or upload size limits I should plan for?" answer="&#x22;Verdocs applies plan-level envelope quotas and platform upload limits (for example, multi-megabyte JSON bodies and per-file upload caps on documents and images). Webhook deliveries expect a quick `2xx` response within a few seconds. Design integrations to backoff on errors, avoid tight polling loops, and upload large artifacts directly via supported document endpoints rather than inlining binary data in JSON.&#x22;" />

  ## Organizations & Profiles [#organizations--profiles]

  <FAQEntry learn="{text: 'Read Understanding Profiles and Managing Your API Keys', path: '/docs/guides/tutorials/understanding-profiles-or-why-do-my-api-calls-return-the-wrong-data'}" question="What is the difference between a user, profile, organization, and recipient?" answer="&#x22;A user is a login identity (email and password). A profile is that user's membership in one organization and determines which templates, envelopes, and settings your API token can see. A recipient is a signer, approver, CC, or preparer on a specific envelope, recipients do not need a Verdocs account to sign. Most API calls are scoped to the organization tied to your active profile, so mixing these concepts is the leading cause of \&#x22;wrong data\&#x22; bugs in integrations.&#x22;" />

  <FAQEntry learn="{text: 'Switch profile or read the profiles guide', path: '/docs/reference/Rest-API/api-docs/profiles/switchProfile'}" question="Why do my API calls return templates or envelopes from the wrong organization?" answer="&#x22;This usually means your access token is scoped to a different active profile than you expect. Check which profile your API key or session is using, then switch profiles or create a key tied to the correct organization. See What is the difference between a user, profile, organization, and recipient? above for the underlying model. If you are building multi-tenant SaaS, see How should my SaaS map each customer to Verdocs? for the recommended tenant layout.&#x22;" />

  <FAQEntry learn="{text: 'Read organization hierarchies', path: '/docs/guides/tutorials/organization-hierarchies'}" question="How should my SaaS map each customer to Verdocs?" answer="&#x22;A proven pattern is one child organization per SaaS tenant under your parent platform organization. That isolates templates, branding, usage, and API credentials per customer while you retain parent-level visibility for billing and support. Avoid sending all customers' envelopes from a single shared org unless you intentionally want one shared template library and combined usage.&#x22;" />

  <FAQEntry learn="{text: 'Get organization usage metrics', path: '/docs/reference/Rest-API/api-docs/organizations/getOrganizationUsage'}" question="How can I see envelope usage for billing my own customers?" answer="&#x22;Use the organization usage API to read metered activity for your org or child orgs. This helps ISVs reconcile Verdocs consumption with the usage-based fees they charge their own tenants. Combine usage data with `entitlement_used` webhooks if you need near-real-time dashboards inside your product.&#x22;" />

  <FAQEntry learn="{text: 'Read Corporate Email Safeguard', path: '/docs/learn/whats-new/corporate-email-safeguard'}" question="Why does Verdocs require a corporate email to sign up or invite teammates?" answer="&#x22;Verdocs enforces a corporate-email safeguard on self-service signup and certain invitation flows to reduce abuse, improve account recovery, and align with how B2B platforms onboard customers. Consumer mailbox domains are rejected. If your team legitimately uses a non-corporate domain, contact Verdocs support for onboarding options.&#x22;" />

  ## Templates & Documents [#templates--documents]

  <FAQEntry learn="{text: 'Read Template Changes and Sent Envelopes', path: '/docs/guides/tutorials/template-changes-and-sent-envelopes'}" question="Does updating a template affect envelopes already sent?" answer="&#x22;No. In Verdocs, each new envelope receives its own envelope documents, envelope fields, and recipient records; roles remain tied to the template. Later template edits do not change the documents or field definitions in envelopes already sent. Use the updated template when creating new envelopes; editing the template does not apply corrections to an existing sent envelope.&#x22;" />

  <FAQEntry learn="{text: 'Follow the server workflow with static templates', path: '/docs/guides/tutorials/server-workflow-with-static-templates'}" question="What is the difference between a template and an envelope?" answer="&#x22;A template is a reusable definition: documents, field placements, roles, and default workflow settings. An envelope is a live signing transaction created from a template (or from ad hoc documents) with real recipients, values, and status. Think of templates as your product's \&#x22;document type\&#x22; library and envelopes as per-customer executions. Most production apps create envelopes programmatically while templates are authored once in the editor or via API.&#x22;" />

  <FAQEntry learn="{text: 'Tutorial: send an envelope without a template', path: '/docs/guides/tutorials/send-an-envelope-without-a-template'}" question="Can I send a document for signature without creating a template first?" answer="&#x22;Yes. You can create an envelope directly from uploaded PDF or DOCX files, define recipients and fields in the same request or via PDF tags, and send immediately. This is useful for one-off documents, mail-merge style generation, or systems that already produce the final PDF server-side. Templates remain the better choice when business users need a repeatable, governed document type.&#x22;" />

  <FAQEntry learn="{text: &#x22;Read DOCX support in What's New&#x22;, path: '/docs/learn/whats-new/docx-support'}" question="Does Verdocs support Word (DOCX) documents?" answer="&#x22;Yes. You can upload DOCX files to templates or envelopes and Verdocs converts them to PDF for signing and archival. The legally binding artifact remains a signed PDF, which is standard for eSignature compliance. Validate layout after conversion for complex Word formatting, and keep PDF as the source of truth for pixel-perfect legacy documents.&#x22;" />

  <FAQEntry learn="{text: 'Read dynamic tagging and the tagging tutorial', path: '/docs/guides/tutorials/tagging-dynamic-documents'}" question="What are dynamic tags or PDF tags for field placement?" answer="&#x22;Dynamic tags let you embed machine-readable placeholders in documents so Verdocs can place signature, initial, date, and text fields automatically at send time. This is ideal for server-generated contracts, mail merge, or documents that are poor fits for a visual template builder. Tags can reduce manual template maintenance when field positions are deterministic from your document generator.&#x22;" />

  <FAQEntry learn="{text: 'Create an envelope and update envelope fields', path: '/docs/reference/Rest-API/api-docs/envelopes/createEnvelope'}" question="How do I prefill fields without removing the signer's ability to edit them?" answer="&#x22;Supply default values when creating the envelope or updating fields before signing begins. Defaults appear in the signer UI as starting values; unless a field is marked read-only in template settings, signers can still change them. Use read-only fields only for data your system must lock down (account numbers, calculated totals, system-generated clauses).&#x22;" />

  <FAQEntry learn="{text: 'Learn more about Document Processing', path: '/docs/guides/tutorials/document-processing'}" question="Why are tags in my PDF not creating fields?" answer="Text-tag processing is opt-in per organization. Enable `process_tags: true` on the organization that owns the profile or API key used for the upload." />

  <FAQEntry learn="{text: 'Read about Dynamic Tagging', path: '/docs/guides/tutorials/tagging-dynamic-documents'}" question="Can I use AcroForm detection and Dynamic Tagging together?" answer="Yes, but they interact: AcroForm detection runs only when no text tags are found. A PDF with both embedded tags and fillable widgets will follow the text-tag path when `process_tags` is enabled." />

  <FAQEntry learn="{text: 'Does Verdocs support DOCX files?', path: '/docs/learn/whats-new/docx-support'}" question="Do DOCX uploads respect these settings?" answer="Yes. DOCX files are converted to PDF first; `process_tags` controls whether the converted PDF is scanned for tags. AcroForm detection applies to the resulting PDF when no tags are present." />

  <FAQEntry learn="{text: 'Learn more about organization profiles', path: '/docs/guides/tutorials/understanding-and-managing-profiles'}" question="Who can change pipeline settings?" answer="Organization admins for that organization. Regular members cannot read or update pipeline settings." />

  <FAQEntry learn="{text: 'Which route attaches documents to a template?', path: '/docs/reference/Rest-API/api-docs/template-documents/createTemplateDocument'}" question="Can I use an existing fillable PDF without modifying it?" answer="Yes. That is the main benefit. Upload the PDF exactly as you have it today, no need to embed Verdocs tags, measure field coordinates, or recreate the form in the template builder. Once `process_acroforms` is enabled, you can turn a standard fillable form (such as an I-9 or signature card) into a send-ready template with roles and fields already in place. You can still fine-tune field types, labels, and layout afterward through the builder or API before your first envelope goes out." />

  <FAQEntry learn="{text: 'How to mutate template roles.', path: '/docs/reference/Rest-API/api-docs/roles/updateTemplateRole'}" question="Can I assign AcroForm fields to different signers?" answer="Not automatically at upload time. AcroForm PDFs do not encode signer roles, so Verdocs assigns every detected field to a single Recipient role. After the template is created, you can rename that role, add additional roles, and reassign fields through the template builder or the Roles and Fields APIs, or use Dynamic Tagging (DOCX) if you need multiple signers defined in the source document from the start." />

  <FAQEntry learn="{text: 'Learn about our dynamic tags.', path: '/docs/learn/whats-new/dynamic-tagging'}" question="Does AcroForm detection work on DOCX uploads?" answer="No. AcroForm is a PDF-native format. DOCX files are converted to PDF first; only the resulting PDF is eligible for widget detection. For Word-based workflows, use Dynamic Tagging in the source document instead." />

  ## Envelopes & Signing Workflow [#envelopes--signing-workflow]

  <FAQEntry learn="{text: 'Read about envelope status and document downloads', path: '/docs/reference/Rest-API/api-docs/envelopes/getEnvelope'}" question="When is an envelope actually finished and safe to download?" answer="&#x22;An envelope can show `complete` in the API or signing UI before cryptographically signed PDFs and the audit certificate are ready. After the last signer submits, Verdocs runs a background finalization step that stamps fields, applies PKI signatures, generates the certificate, and prepares download links. For production integrations, treat the `envelope_completed` webhook (or an explicit document download after that event) as the signal that signed artifacts are available, not the moment the signer sees a \&#x22;done\&#x22; screen.&#x22;" />

  <FAQEntry learn="{text: 'Create an envelope with sequenced recipients', path: '/docs/reference/Rest-API/api-docs/envelopes/createEnvelope'}" question="How does signing order work when I have multiple recipients?" answer="&#x22;Verdocs supports sequenced routing. Recipients in the same sequence may sign in parallel; the next sequence is invited only after everyone in the current sequence has submitted. Use sequence and order fields when creating recipients to model approver-then-signer flows, parallel co-signers, or CC/preparer roles. CC recipients are typically notified without blocking completion.&#x22;" />

  <FAQEntry learn="{text: 'View our certificate tutorial', path: 'https://www.youtube.com/watch?v=dydfrsmRNoU'}" question="How does Verdocs handle signed PDFs, audit trails, and certificates?" answer="&#x22;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.&#x22;" />

  <FAQEntry learn="{text: 'View our certificate tutorial', path: 'https://www.youtube.com/watch?v=dydfrsmRNoU'}" question="How do I verify a completed Verdocs PDF?" answer="&#x22;Verify the document in the desktop version of Adobe Acrobat or Adobe Acrobat Reader, not in a browser preview. Download the original PDF, open the Signatures panel, and expand the entry labeled Rev. 1: Signed by Verdocs, Inc. Acrobat should show a green checkmark confirming the signature is valid, the document has not been modified since signing, the signer's identity is valid, the signature includes an embedded timestamp, and the signature is LTV enabled. Select Certificate Details to review the certificate and trust chain; Acrobat should show a valid path through the Sectigo document-signing chain.&#x22;" />

  <FAQEntry learn="{text: 'View our certificate tutorial', path: 'https://www.youtube.com/watch?v=dydfrsmRNoU'}" question="Why doesn't the European Commission DSS validator show my Verdocs PDF as valid?" answer="&#x22;The European Commission DSS website is not the appropriate validation method for completed Verdocs PDFs. Verdocs applies an embedded document-signing certificate trusted through the Adobe Approved Trust List (AATL). Use Adobe Acrobat or Acrobat Reader to verify these documents instead.&#x22;" />

  <FAQEntry learn="{text: 'Read about envelope completion and downloads', path: '/docs/reference/Rest-API/api-docs/envelopes/getEnvelope'}" question="Why don't individual signer fields appear as separate certificate-backed signatures?" answer="&#x22;For completed Verdocs envelopes, the cryptographic verification point is the Verdocs digital certificate applied to the final PDF, not separate per-signer certificate entries in third-party validators. That certificate confirms the authenticity and integrity of the completed document and whether it has been altered since certification. Individual signer fields should not be expected to appear as separate certificate-backed signatures in tools like DSS.&#x22;" />

  <FAQEntry learn="{text: 'Read about envelope completion and downloads', path: '/docs/reference/Rest-API/api-docs/envelopes/getEnvelope'}" question="What can cause a Verdocs PDF to fail signature validation?" answer="&#x22;Always verify the original downloaded PDF from Verdocs. Printing the document to PDF, flattening it, or resaving it through another application can remove or disrupt the embedded validation information. If Acrobat still does not show a valid signature after reviewing the original file, contact Verdocs support with the exact PDF under review and your Adobe Acrobat version.&#x22;" />

  ## Recipients [#recipients]

  <FAQEntry learn="{text: 'Start a signing session', path: '/docs/reference/Rest-API/api-docs/recipients/startSigningSession'}" question="Do my signers need Verdocs accounts?" answer="&#x22;No. Signers interact through invite links, embedded signing, or hosted signing flows using an envelope access key. They may receive a lightweight guest signing session without creating a password or joining your organization. Your own team members, the people building and sending envelopes, typically do need Verdocs users and profiles for the Developer Center and API automation.&#x22;" />

  <FAQEntry learn="{text: 'Read the recipient auth ladder', path: '/docs/guides/tutorials/the-recipient-auth-ladder'}" question="What recipient authentication options does Verdocs support?" answer="&#x22;You can require combinations of disclosure acceptance, private passcode, email OTP, SMS OTP, knowledge-based authentication (KBA), and additional identity checks depending on plan and configuration. Auth methods are configured per recipient on the envelope. Failed verification emits `recipient_auth_fail` webhooks so your support team can react. KBA and SMS are commonly enabled through paid plans or sales-supported setup rather than the self-serve Basic plan alone.&#x22;" />

  <FAQEntry learn="{text: 'Review recipient actions in the API reference', path: '/docs/reference/Rest-API/api-docs/recipients/delegateRecipient'}" question="Can a signer decline, delegate, or ask the sender a question?" answer="&#x22;Yes. Signers can decline disclosures or the envelope, delegate signing to another email address, and ask the sender a question without completing the envelope. Each action emits webhook events (`recipient_declined`, `recipient_delegated`, etc.) so your application can update CRM records, reopen internal review, or reissue the envelope. Design your UX and support playbooks around these branches, they are normal in regulated workflows.&#x22;" />

  <FAQEntry learn="{text: 'Get an in-person signing link', path: '/docs/reference/Rest-API/api-docs/recipients/getInPersonLink'}" question="How do I run an in-person signing flow on a tablet or front desk?" answer="&#x22;Use the in-person signing link API to generate a session suitable for handing a device to a signer on site, common in real estate closings, branch banking, and clinic intake. Your staff member stays authenticated as the sender while the signer completes fields in a controlled device context. Pair this with embedded signing UI for the cleanest kiosk experience.&#x22;" />

  ## Signer Experience & Embeds [#signer-experience--embeds]

  <FAQEntry learn="{text: 'View our components available via the Web SDK.', path: '/docs/reference/SDK/web/components'}" question="Can my users sign documents without leaving my application?" answer="&#x22;Yes. With embedded signing, signers review, fill, and submit documents inside your application's pages, no redirect to a separate signing product. That keeps users in familiar navigation, preserves brand trust, and lets you control what happens before and after signing (prefill, validation, post-sign redirects). Implement embedded signing with Web Components, SDK helpers, or IFRAME embeds; see \&#x22;What is the difference between embedded signing and hosted signing?\&#x22; if you are choosing between in-app and hosted flows.&#x22;" />

  <FAQEntry learn="{text: 'Explore Web SDK components and IFRAME embeds', path: '/docs/reference/SDK/web/components'}" question="What is the difference between embedded signing and hosted signing?" answer="&#x22;Embedded signing renders the signing experience inside your application using Web Components, SDK helpers, or IFRAME embeds, so users never leave your product shell. Hosted signing sends signers to a Verdocs-hosted signing URL (still brandable) via email or your own notification. Embedded signing maximizes UX continuity; hosted signing is faster to launch when you do not control the front end for every signer.&#x22;" />

  <FAQEntry learn="{text: 'Read the IFRAME embeds tutorial', path: '/docs/guides/tutorials/iframe-embeds'}" question="When should I use Web Components versus IFRAME embeds?" answer="&#x22;Prefer Web Components in modern React, Vue, Angular, or vanilla apps. They offer tighter styling control and a more native feel. Use IFRAME embeds when your stack cannot load Web Components cleanly (some CMS platforms, legacy portals, or strict CSP environments). Both paths support branded signing; the tradeoff is integration flexibility versus hosting constraints.&#x22;" />

  ## Branding [#branding]

  <FAQEntry learn="{text: 'Watch our email customization tutorial.', path: 'http://youtube.com/watch?v=SMcV05bNzew'}" question="Does Verdocs support white-label branding?" answer="&#x22;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.&#x22;" />

  ## Notifications [#notifications]

  <FAQEntry learn="{text: 'Read Bring-Your-Own Notification', path: '/docs/guides/tutorials/bring-your-own-notification'}" question="&#x22;What is `no_contact`, and when should I use it?&#x22;" answer="&#x22;Set `no_contact: true` on an envelope when your application, not Verdocs, will send all signer-facing communications. This is common for embedded SaaS products that already email or push notifications from their own domain and template system. Verdocs still runs routing, signing, and completion, but you become responsible for delivering invite links and status updates. Listen for events such as `recipient_invited` and `recipient_invite_failed` to drive your own notification pipeline.&#x22;" />

  <FAQEntry learn="{text: 'Control workflow behaviors and notification templates', path: '/docs/guides/tutorials/controlling-workflow-behaviors-notifications-names-and-more'}" question="Can I customize the emails and sender name signers see?" answer="&#x22;Yes. You can override sender display names, configure custom notification templates per event, and apply brand-level email identity as your white-label setup matures. For full control of delivery timing and copy, use `no_contact` and send notifications yourself. Even with Verdocs-sent email, branding fields and templates let the experience match your product voice.&#x22;" />

  <FAQEntry learn="{text: &#x22;View your email notification templates&#x22;, path: '/docs/reference/Rest-API/api-docs/notifications/getNotificationTemplates'}" question="Can I customize the SMS body like I do for email?" answer="Not today. Transactional SMS uses standardized copy so messages stay short, actionable, and carrier-friendly. Email supports org-, template-, and parent-scoped notification templates; SMS does not." />

  <FAQEntry learn="{text: 'Sending an email reminder', path: '/docs/reference/Rest-API/api-docs/organization-invitations/resendOrganizationInvitation'}" question="Will signers get an SMS when I send a reminder?" answer="No. Reminders use the recipient:reminder event, which is email-only today. The same applies to manual resends. Only the initial recipient:invited event can trigger a text. If you need to nudge a signer by SMS after the first invite, your application must send that message yourself (for example, using a signing link from Start Signing Session)." />

  ## Brands [#brands]

  <FAQEntry learn="{text: 'Which route can I use to add a custom email domain?', path: '/docs/reference/Rest-API/api-docs/brands/addBrandEmailDomain'}" question="When integrating your own custom email domain, can I use my root domain, or do I need a subdomain?" answer="Both are supported. You can set subdomain to acme.com or notify.acme.com. We recommend a dedicated subdomain (notify.acme.com) to isolate notification deliverability from your primary business mail." />

  <FAQEntry learn="{text: &#x22;How can I view my email domain's status?&#x22;, path: '/docs/reference/Rest-API/api-docs/brands/getBrand'}" question="What sender do recipients see while DNS is still pending?" answer="notifications@verdocs.com (with your brand's display name or organization name where applicable). Custom From addresses do not go live until verification completes." />

  <FAQEntry learn="{text: 'What are these acronyms?', path: 'https://www.cloudflare.com/learning/email-security/dmarc-dkim-spf'}" question="What happens if I only add SPF but not DKIM or DMARC?" answer="The domain stays pending. All three checks must pass. The API response and dashboard show per-record status so you can see exactly which records are still missing." />

  <FAQEntry learn="{text: 'How can I re-verify?', path: '/docs/reference/Rest-API/api-docs/brands/verifyBrandEmailDomain'}" question="Why did my domain move from 'verified' to 'suspended'?" answer="A daily re-verification check found that SPF, DKIM, or DMARC records are no longer valid: for example, if someone removed a CNAME or changed the DMARC policy away from 'p=reject. Restore the correct DNS records and trigger verification again." />

  ## Webhooks [#webhooks]

  <FAQEntry learn="{text: 'Read the webhook guide and event reference.', path: '/docs/reference/Rest-API/webhooks'}" question="How do webhooks work, and which events are supported?" answer="&#x22;Webhooks are the recommended way to track envelope status. Use them instead of aggressive API polling. Verdocs pushes events to your endpoint when signing activity occurs so you can update CRM records, trigger workflows, and retrieve completed PDFs and audit trails. At minimum, handle `recipient_submitted`, `recipient_declined`, `envelope_completed`, and `recipient_auth_fail` (if using recipient verification); also plan for sent, viewed, expired, canceled, and voided events as your integration matures. Reserve polling for admin dashboards or repair jobs only. Design consumers to be idempotent, delivery is at-least-once.&#x22;" />

  <FAQEntry learn="{text: 'Read Securing Your Webhooks: HMAC vs OAuth', path: '/docs/guides/tutorials/securing-your-webhooks-hmac-vs-oauth'}" question="How do I verify that a webhook really came from Verdocs?" answer="&#x22;Configure your webhook endpoint to require either an HMAC signature on the raw JSON body or OAuth client-credentials authentication where Verdocs fetches a bearer token from your token endpoint before delivery. HMAC is the fastest path for most backends; OAuth fits enterprises that already issue machine tokens to partners. Reject requests that fail verification, and rotate webhook secrets on the same schedule as other production credentials.&#x22;" />

  ## Entitlements [#entitlements]

  <FAQEntry learn="{text: 'Learn about Organization Hierarchies', path: '/docs/guides/tutorials/organization-hierarchies'}" question="Do child organizations need their own entitlements?" answer="Usually no. Child orgs inherit active entitlements from their parent. If a sub-account can't use SMS or hits a brand limit unexpectedly, confirm the parent org has the right entitlement and that the child was created with the correct parent_id." />

  <FAQEntry learn="{text: 'Want to handle your own notifications?', path: '/docs/guides/tutorials/bring-your-own-notification'}" question="Why did my recipient get an email but not an SMS?" answer="SMS invitations and reminders require the SMS notifications entitlement. Without it, Verdocs still delivers email on the same events. It simply does not send the text message. This is intentional: your workflow continues, but the SMS channel stays off until you're entitled to it." />

  ## AI Agents & MCP [#ai-agents--mcp]

  <FAQEntry learn="{text: 'Connect your client to the documentation MCP', path: '/docs/learn/mcp'}" question="Can I give Claude, Cursor, or another AI coding agent access to the Verdocs docs?" answer="&#x22;Yes. The Verdocs Developer Center runs an MCP server at https://developers.verdocs.com/mcp that lets an AI assistant search and read this documentation directly, so it works from what Verdocs actually does rather than from general knowledge about eSignature APIs. In Claude Code the command is: claude mcp add --transport http verdocs-docs https://developers.verdocs.com/mcp. Clients that support remote MCP over HTTP take the URL directly, and clients that only speak stdio can bridge to it with mcp-remote. The documentation MCP is read-only and anonymous, so there is no key to configure and nothing it can change.&#x22;" />

  <FAQEntry learn="{text: 'See the machine-readable endpoints', path: '/docs/learn/mcp'}" question="How do I feed the Verdocs documentation into a RAG pipeline or a custom agent?" answer="&#x22;Every page is available as plain markdown by appending .mdx to its URL, which is a few kilobytes of content instead of roughly 300 KB of rendered HTML. https://developers.verdocs.com/llms.txt is an index of every page with titles, descriptions, the API base URL, and the auth model, and https://developers.verdocs.com/llms-full.txt is the full text of the whole site in one response. The OpenAPI specification is at https://developers.verdocs.com/openapi.json if you would rather generate a client than read prose. None of these require MCP or an account.&#x22;" />

  <FAQEntry learn="{text: 'Read about the planned platform MCP', path: '/docs/learn/mcp'}" question="Can an AI agent send envelopes or act on my Verdocs account?" answer="&#x22;Not through the documentation MCP, which is read-only and reads a public site. A separate platform MCP that exposes Verdocs API operations as tools, including creating and sending envelopes, checking signing status, and managing templates and recipients, is in development. It will be a separate endpoint with its own authentication, scoped to the permissions your API credentials already carry, so connecting an agent to the documentation today gives it no access to your account.&#x22;" />

  ## Compliance & Enterprise [#compliance--enterprise]

  <FAQEntry learn="{text: 'Contact Verdocs for enterprise/HIPAA options', path: 'https://verdocs.com/product'}" question="Does Verdocs support HIPAA-aligned workflows?" answer="&#x22;Verdocs supports HIPAA-oriented deployment options for qualifying enterprise customers, including dedicated storage configurations for regulated organizations. HIPAA readiness also depends on your BAAs, access controls, and how you handle signer PHI in your own application. Talk to Verdocs sales or support if your vertical requires HIPAA before go-live.&#x22;" />

  <FAQEntry learn="{text: 'See our certificate in action', path: 'https://www.youtube.com/watch?v=dydfrsmRNoU'}" question="In which countries is an electronic signature created with Verdocs considered legally valid?" answer="Verdocs supports legally valid electronic signatures in 50+ countries and 60+ jurisdictions, including the United States, Canada, the United Kingdom, Australia, New Zealand, Singapore, Japan, South Korea, India, Brazil, Mexico, South Africa, and all European Union member states: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, and Sweden." />

  <FAQEntry learn="{text: 'Learn about our PDF verification process', path: '/docs/guides/tutorials/verifying-a-completed-verdocs-pdf-signature'}" question="What are the eIDAS signature levels?" answer="eIDAS recognizes three tiers of electronic signatures: Simple Electronic Signatures (SES), Advanced Electronic Signatures (AES), and Qualified Electronic Signatures (QES). Verdocs supports SES and AES workflows today, and we also support QES through qualified trust service provider partnerships where a customer use case requires it." />

  ## Knowledge-Based Authentication (KBA) [#knowledge-based-authentication-kba]

  <FAQEntry learn="{text: 'Submit your KBA identity', path: '/docs/reference/Rest-API/api-docs/kba/submitKbaIdentity'}" question="What is Knowledge-Based Authentication?" answer="Knowledge-Based Authentication, or KBA, is an identity-verification method that requires a recipient to answer questions based on information associated with their identity. It provides a higher level of assurance than email access alone and is commonly used for tax, financial services, insurance, lending, and other sensitive workflows. KBA acts as an authentication step before signing. The recipient must successfully verify their identity before they can access and sign the documents." />

  <FAQEntry learn="{text: 'Understanding the KBA workflow', path: 'https://duo.com/learn/knowledge-based-authentication'}" question="How does Verdocs KBA work?" answer="The recipient is asked to provide identifying information, including their name, residential address, date of birth, and the last four digits of their Social Security number. If the information can be matched, the recipient is presented with challenge questions, such as questions about previous addresses. The recipient must successfully complete the challenge before proceeding to the signing experience." />

  <FAQEntry learn="{text: 'See The Recipient Authentication Ladder for implementation details', path: '/docs/guides/tutorials/the-recipient-auth-ladder'}" question="How do I add KBA to a recipient?" answer="Configure kba as an authentication method for the recipient. When using the Verdocs signing components, the KBA interface automatically collects the required information and guides the recipient through the verification process. Developers building a custom signing experience can submit the recipient’s identity information and challenge responses via our API." />

  <FAQEntry learn="{text: 'Verdocs supports SSN workflows via KBA', path: '/docs/learn/whats-new/knowledge-based-authentication-now-requires-ssn-last-4'}" question="Can KBA information be prefilled?" answer="Yes. The API supports prefilling the recipient’s address, city, state, ZIP code, date of birth, and last four digits of their Social Security number. These fields may only be changed before the recipient successfully completes KBA. Only prefill information that your application is authorized to collect and process, and avoid including sensitive information in application logs." />

  <FAQEntry learn="{text: 'See our pricing for KBA services', path: 'https://verdocs.com/pricing'}" question="Does KBA require activation?" answer="Yes. KBA is a metered authentication feature that must be enabled for your organization through a Verdocs entitlement. KBA currently costs $1 per use. Contact support@verdocs.com to request activation. For multi-tenant platforms, child organizations can inherit the KBA entitlement from their parent organization, and usage can be monitored for billing purposes." />

  <FAQEntry learn="{text: 'Learn about the recipient authentication methods', path: '/docs/guides/tutorials/the-recipient-auth-ladder'}" question="What happens if a recipient cannot complete KBA?" answer="A recipient who does not successfully complete KBA cannot proceed to the signing step. KBA sessions also have a limited verification window and may expire if the recipient waits too long. Authentication failures can be surfaced to the sender through the recipient status, notifications, and webhook events." />
</div>