Electronic signature API for SaaS products: what embedded and white label signing really costs

If you are embedding signing inside your own product, the per signature rate is not the number that decides your bill. The tier that permits embedded and white labelled signing is, and at most vendors it sits three to six times above the entry API plan. Dropbox Sign puts embedded signing on a $250 a month plan when its entry API plan is $75. Documenso puts white labelled embedding on a $250 a month plan when its team plan is $40. Two vendors charge nothing extra for it at all. Every figure and quotation below was read off the vendors own pricing pages and documentation on 2 September 2026.

This matters because a SaaS product buys signing differently from a business that sends contracts. A business wants a place to send documents from. A product wants the signing screen to appear inside its own interface, carrying its own brand, so the customer never realizes a third party is involved. That second thing is a distinct SKU almost everywhere, and it is rarely the one on the plan card you costed.

What embedded signing costs at each vendor

Embedded signing means the signature ceremony renders inside your application, usually in an iframe, instead of the signer being emailed a link to the vendor site. White labelling goes one step further and removes the vendor branding from that screen. They are separate gates at several vendors, and the second one is always the expensive one.

Two of the seven publish enough to plan a budget from, two publish the entry price and hide the gate, and three do not publish the gate at all. That ratio is normal for this category and it is the reason a shortlist built from plan cards falls apart in week three of an integration.

Why Dropbox Sign is the clearest example

Dropbox Sign sells its API entirely separately from its application, on its own pricing page, which already makes it more honest than most. Essentials is $75 a month, or $900 billed yearly, described as "Starting at 50 signature requests / mo." Standard is $250 a month, or $3,000 billed yearly, starting at 100 a month. Premium is a custom quote.

On volume alone you would start at Essentials. But the FAQ on the API product page settles it: "The option to custom brand your eSignature forms and assets is included with both our Standard and Premium packages, together with other super features including audit trails, data validation, embedded signing, and advanced signing tools."

So embedded signing and branding both start at Standard. For a product integration the real entry price is $250 a month, not $75, and the 50 request Essentials tier is for teams automating their own paperwork rather than building a feature. Note what else is bundled into that jump: audit trails. If your customers are in a regulated industry and will ask for an audit trail, you were going to Standard regardless.

Documenso splits embedding from white labelling, and charges for the second

Documenso is the other vendor that publishes its gate clearly, and it draws the line in a different place. Its Teams plan at $40 a month, $480 billed yearly, includes five users, unlimited documents, "API Access for Automation" and "Embedded Signing". That is a genuinely cheap way to put a signing screen inside your product.

The Platform plan at $250 a month, $3,000 billed yearly, is the one that lists "Embedded Signing (Whitelabel)" alongside unlimited documents and users and "Unlimited API access". So embedding costs $40 and removing the Documenso branding from the embedded screen costs $250, a 6.25 times step for what is, from your side, a styling change.

Whether that step is worth taking is a product question rather than an engineering one. If you sell to enterprises who will notice another vendor logo inside your app, it is not optional. If you sell to small businesses who mostly do not look, $40 a month buys you the same functionality with someone else name on it, and you can move later. Documenso also offers a self hosted route, which is the usual reason teams shortlist it in the first place.

The two vendors that do not charge extra to embed

DocuSeal prices embedding as ordinary usage. Its published API and embedding rate is "$0.20 / completion" for documents signed "via API or Embedding", on top of a Pro seat at $20 per user a month, and sandbox documents are "$0/ document". There is no embedded tier because embedding is not a tier. If you want the vendor gone entirely, the open source edition is free to self host with unlimited emails and submissions, which is white labelling by a different route and the cheapest one on this page.

SignNow includes both at its entry API tier. API Professional is $146 a month billed annually for 1,000 signature invites a year, and the plan card lists "Embedded signing and sending", "White labeling", "Document generation" and "Bulk signature invites" together. That is expensive per signature, roughly $1.75, and cheap for what it unlocks. SignNow also describes its API plans in a way no other vendor here does: they "focus on sending signature invites through one or more integrations rather than through users."

The pattern is worth naming. The two vendors that charge nothing extra for embedding are the two that treat the API as the main product. The vendors that charge three to six times for it are the ones whose main product is a web application, where embedding is an upsell to a different kind of customer. Shortlist accordingly.

Why the per signature rate matters less than you expect

Run the arithmetic at the volumes a mid-size SaaS product actually sees and the ranking barely moves on usage.

Take 500 signatures a month, 6,000 a year, which is a healthy product doing real business. On DocuSeal that is $1,200 of completions plus a seat, about $1,440 a year. On BoldSign at $0.75 an envelope it is $4,500. On Documenso Teams it is $480, because documents are unlimited and you are paying for users. On SignNow you would be on a 5,000 or larger invite plan. On Dropbox Sign Standard you are at $3,000 a year plus whatever the volume band above 100 a month costs.

Now compare those differences against the embedded tier step. Moving from Documenso Teams to Platform costs $2,520 a year and changes nothing about your volume. Moving from Dropbox Sign Essentials to Standard costs $2,100 a year and changes nothing about your volume. At 6,000 signatures a year those tier steps are the same size as the entire usage bill, and at lower volumes they dwarf it.

The practical consequence: work out which tier you need first, from your product requirements, and only then compare per signature rates within that tier. Doing it the other way round, which is how every comparison article in this category is organized, produces a shortlist you will have to throw away. The full rate cards for all eight vendors, normalized to the same annual job, are on our e-signature API pricing comparison.

What to check before you build against any of them

Does embedded signing require a plan you can afford at launch? Ask before you prototype, because the sandbox usually permits features the entry paid plan does not, and finding out after the integration is written is expensive.

Whose name is on the signature request email? Embedding only covers the screen. If the vendor still emails your customer from its own domain, you have not white labelled anything that matters. This is a separate setting from embedded signing at several vendors and is often gated separately again.

What does the completed document flow look like? Every vendor emails a signed copy and an audit certificate when a document completes, and those notifications pile up in whatever mailbox you set as the sender. If your operations team is filing them by hand, it is worth being able to extract the details straight out of those emails into a spreadsheet rather than opening each one.

Are you generating the document as well as signing it? Signing vendors charge for signatures, not for producing the PDF that gets signed. If your product assembles the agreement from customer data, that is a separate job with separate economics, covered on our document generation API page. Teams selling into law firms should also read legal document automation software, where the assembly platform usually sits above both the renderer and the signing API.

What happens at the ceiling? SignNow moves you up a plan automatically rather than blocking or billing overage: "Once you reach your plan limit, we will automatically upgrade you to the next subscription plan tier." Others stop. For a product where a signature failure is a checkout failure, which behaviour you get is a real reliability decision, not a billing footnote.

Is embedded signing worth paying for?

For a product that sells to businesses, usually yes, and for a reason that has nothing to do with branding. Redirecting a customer to a third party site mid workflow is where funnels leak. The customer opens a new tab, gets an email from a company they have never heard of, and completes the signature hours later or not at all. Keeping the ceremony inside your interface removes an entire context switch from the most important step in the flow.

White labelling on top of that is a narrower call. It matters if you resell, if you sell to enterprises with vendor review processes, or if your customers would reasonably ask why another company is in the room. It matters much less if you are a small business tool where a discreet vendor logo reads as normal. The prices above make the decision concrete: at Documenso it is a $2,520 a year question, and at DocuSeal you can sidestep it entirely by hosting the thing yourself.