Embedded e-signature
Add contract signing directly to your product.
Embedded e-signature means the signing step happens inside your product, under your brand, instead of redirecting your users to a signing vendor. Conovo generates the document first, orders the signers from the parties confirmed on the template, dispatches through a real e-signature provider, and reports every transition back to your platform as a signed webhook.
The honest version: signing is the last step of the pipeline, not the product. If you already have a signature vendor and someone on your team is still assembling the document by hand before each request, the assembly is the part worth replacing.
The gap
A signature API starts one step late.
Signature APIs assume the document already exists.
Every e-signature API takes a finished PDF and collects signatures on it. That is a real and well-solved problem. It is also the second half of the job: someone still has to decide what this particular agreement says, put this customer’s numbers in it, check the numbers agree with each other, and produce the file.
In most platforms that someone is a human with a Word document, or an engineer maintaining a template system nobody wanted to own. Conovo is the layer that does it, and because it produced the document, it can order the signers, place the signature fields, and refuse to send when the contract doesn’t hold up.
What you get
Execution, under your brand, with a real trail.
Signing that belongs to your product.
Your brand, end to end
Components render inside your product, themed with CSS custom properties. The businesses using your platform and the customers who sign never see Conovo’s name, an account, or a separate portal.
Multi-party signing in order
Signing parties confirmed on the template become recipient rows; their order is the signing order, passed through to the provider so signers are prompted in sequence rather than all at once.
Sign-here boxes derived, not drawn
Conovo locates each party’s signature line in the execution zone of the document and derives the field coordinates at dispatch. When it cannot place a field confidently it places none, because a wrong anchor is worse than an absent one, and placement never blocks a send.
Optional phone-verified signers
A recipient sent with a mobile number can be required to pass an SMS code before the signing link is released. The phone number never appears in logs and is masked in responses; the verification itself is a content-free audit event.
Every transition, signed
Drafted, needs attention, sent, viewed, signed, completed, declined, each signed with your account secret in the scheme @conovo/node verifies, retried with backoff, and logged in the console.
Execution sits behind an interface
Conovo signs on your own pages by default. That is an adapter, not an assumption and an account that would rather use an outside provider can, Documenso included, without your integration changing either way.
Honest fit
When not to buy this.
When a signature API alone is the right answer.
- Your users upload their own finished PDFs. If the document arrives complete and nothing needs computing, you need signatures, not generation. Integrate a signature API directly.
- You send one contract, rarely, internally. Infrastructure is the wrong shape for that.
- Your legal team is the user. They want a contract lifecycle platform they log into, which is a different product for a different buyer.
Questions
Asked on most first calls.
Common questions.
What is embedded e-signature?
Embedded e-signature means the signing step happens inside the product your user is already using, under that product's brand, rather than redirecting them to a separate signing vendor's website. The platform controls the workflow, the sender identity, and what the signer sees. The signature itself is still executed by a real e-signature provider with the audit trail that implies.
Does Conovo replace DocuSign?
Not in the way that question usually means. Conovo produces the document, controls the send, and executes the signature itself on your own pages, and it keeps that behind a swappable interface, so an outside provider like Documenso remains available per account. If you already have a signature vendor and only need signatures, you do not need Conovo. If someone on your team is still assembling the document before the signature request, that assembly is what Conovo replaces.
Do our users or their customers see Conovo branding?
No. Conovo ships as React components that render inside your product under your own styling, themed with CSS custom properties. The businesses using your platform and the customers who sign the contracts never encounter Conovo's name, an account, or a separate portal.
How are multi-party signings ordered?
By the signing parties confirmed on the template. Each counterparty becomes a recipient row in the send panel, the list order is the signing order, and that order is passed through to the provider so signers are prompted in sequence rather than all at once. Templates with no declared parties fall back to a single generic recipient.
Can we verify the signer is who they claim to be?
A recipient sent with a mobile number can be required to pass an SMS one-time code before the signing link is released to them. Verification is recorded as a content-free audit event; the phone number itself never appears in logs and is masked in API responses. This gates Conovo's own signing surface. If you dispatch through a provider that also emails its own links directly, those links are outside that gate.
What does our platform receive back?
Signed webhooks for every transition: drafted, needs attention, sent, viewed, signed, completed, and declined. They are signed with your account's secret in the same scheme @conovo/node verifies, delivery is retried with backoff, and the delivery log is visible in the console. Generation events also carry the payload paths that could not be resolved, so your system learns which schema gaps to close.
Next
See the whole path, not just the signature.
Start with the contract generation API, then how templates get set up. Security and data handling are documented on the security page.