Skip to content
Compare

E-signature APIs compared

There are three ways to put signing in a product. Send: the vendor emails a link to a signing page it hosts. Embed: the vendor's signing screen sits inside your app. Build your own: your app renders the screen and an independent service keeps the record. This page sorts eight products by those three models.

Send, embed or build your own

Every e-signature API answers one question first: who draws the screen the signer signs on. The answer decides how the signing step looks, who you depend on at that moment, and where the evidence ends up.

Send

The vendor emails a hosted signing page

Your server creates a signature request through the API. The vendor emails each signer a link, the signer signs on the vendor's page, and you get a webhook and a signed PDF back.

Embed

The vendor's signing screen inside your app

Your server creates the request and asks for a signing URL or session. Your app opens the vendor's signing screen in a frame, a component or a redirect, so the signer stays in your product while they sign on the vendor's screen.

Build your own

Your screen, with an independent record

Your app renders the document, the notice, the field and the button. A headless SDK reports each step from the signer's browser to a record keeper that is not a party to the agreement, and you get a signed receipt.

The three e-signature API models: how each works, who renders the signing screen, where the evidence record lives and which of the eight products support it
ModelHow it worksWho renders the signing screenWhere the evidence record livesProducts that support it
SendThe vendor emails each signer a link to a signing page that it hosts.The vendorWith the vendor, or in your own instance when you self-host an open source product.DocuSign, Dropbox Sign, Adobe Acrobat Sign, PandaDoc, signNow, Documenso, DocuSeal
EmbedYour app opens the vendor's signing screen in a frame, a component or a redirect.The vendorWith the vendor, or in your own instance when you self-host an open source product.DocuSign, Dropbox Sign, Adobe Acrobat Sign, PandaDoc, signNow, Documenso, DocuSeal
Build your ownYour app renders the signing screen, and a headless SDK reports each step from the signer's browser.YouWith an independent record keeper. You store a signed receipt.Esign Comply

E-signature APIs by model, signing screen and evidence

Eight products, six questions. The cells hold what each vendor says about its own product, with the source for every row. Prices and plan tiers are left out: they change often, and each vendor's pricing page is the place to read them.

E-signature APIs compared by signing model, who renders the signing screen, open source, self-hosting, where the evidence record lives and typical fit
ProductModelsWho renders the signing screenOpen sourceSelf-hostableWhere the evidence record livesTypical fit
DocuSignSources for DocuSign:[1][2][3][4]SendEmbedDocuSign. Remote signers open the DocuSign web app from an email, SMS or WhatsApp notice. Embedded signers use its Embedded Recipient View from inside your app.NoNo. Hosted by DocuSign.With DocuSign. Its eSignature service generates a Certificate of Completion as the record of the transaction, and customers download it.Sending agreements from a finished signing product, with an API and an embeddable signing view.
Dropbox SignSources for Dropbox Sign:[5][6][7]SendEmbedDropbox Sign. Signers follow an emailed link to its signing page, or sign in an iFrame that its embedded library opens on your site.NoNo. Hosted by Dropbox.With Dropbox Sign. An audit trail is appended to each completed request, and the transaction log is kept in its database.Signature requests by API, and its signing frame inside a web app.
Adobe Acrobat SignSources for Adobe Acrobat Sign:[8][9][10]SendEmbedAcrobat Sign. Recipients get a notification email, or your app asks the API for a signing URL and opens it for the signer.NoNo. Hosted by Adobe.With Adobe. Acrobat Sign documents the milestones of every transaction in an audit report.Sending agreements for signature and tracking them through an API.
PandaDocSources for PandaDoc:[11][12][13]SendEmbedPandaDoc. Recipients open the document in PandaDoc from an emailed link, or sign in a session that its signing library mounts in your page.NoNo. Hosted by PandaDoc.With PandaDoc. It keeps the audit trail, generates signature certificates and stores the signed PDF copies.Proposals, quotes and contracts built from templates and sent for signature.
signNowSources for signNow:[14][15][16]SendEmbedsignNow. Signers get an email invite, or sign in a signNow iFrame inside your app.NoHosted by signNow. It also offers a private cloud solution that deploys on-premises or in your own cloud.With signNow. You download signed PDFs with a certificate of events, its audit trail of the document history.Send-for-signature and signing links through an API, with a signing frame for apps.
DocumensoOpen sourceSources for Documenso:[17][18][19][20]SendEmbedDocumenso. Recipients sign from an emailed link, or in its embed components for React, Vue, Svelte and other frameworks inside your app.Yes. AGPL-3.0.Yes, with Docker and other methods. A hosted cloud is also offered.In the Documenso instance, which is on your servers when you self-host. The completed PDF is sealed with a digital certificate and an audit log is generated.A complete signing app with open source code that you can run yourself.
DocuSealOpen sourceSources for DocuSeal:[21][22][23][24][25]SendEmbedDocuSeal. Signers get an email or a text with a link, or sign in its embedded form component for JavaScript, React, Vue and Angular.Yes. AGPLv3 with additional terms.Yes, on your own servers. A hosted cloud is also offered.In the DocuSeal instance, which is on your servers when you self-host. A signature certificate with the audit log is generated when all parties have signed.An open-source document signing platform that you can run on your own servers.
Esign ComplySources for Esign Comply:[26][27][28]Build your ownYou. Your app renders every signing screen, and a headless SDK attaches to your own elements. There is no hosted signing page and nothing to embed.No. The offline verifier, esigncomply-verify, is open source.No. Esign Comply keeps the record so that it is independent of your app.With Esign Comply, a third party to the agreement: sealed, hash-chained, signed with keys you do not hold and timestamped by an outside RFC 3161 authority. You store the signed receipt, and the evidence package verifies offline.Developers who build their own signing UI with an AI coding tool, from one clickwrap to a full send-for-signature app.

The numbers under each product name point to the sources at the end of this page. Which features a plan or edition includes differs by vendor.

When each model fits

None of the three is the right answer for every team. The fit follows from how much of the signing step you want to own.

Send

When send fits

  • You want agreements out the door today and do not want to build a signing screen.
  • Your signers are fine with an email from the vendor and a page with the vendor's name on it.
  • A person on your team sends the documents, and an API call from your backend is an extra.
  • You want the vendor to run reminders, signing order and the completed PDF.
Embed

When embed fits

  • Signing has to happen inside your app, without an email round trip.
  • The vendor's signing screen in a frame or a component is acceptable in your product.
  • You want the vendor to own the signing screen and its upkeep.
  • You want open source code on your own servers: Documenso and DocuSeal both offer embedding.
Build your own

When build your own fits

  • The signing step has to look and behave like the rest of your product, on your domain.
  • You build with an AI coding tool, so a new screen costs you a prompt.
  • You want the evidence held by someone who is not a party to the agreement, and not in a table you can edit.
  • You are building a signing product of your own: uploads, signing links, a sender dashboard.
Four questions

How to choose an e-signature API

Answer these in order. The first one that settles it is your model.

  1. 01
    Do you want to write any code at all?If not, buy a send product and use its web app. DocuSign, Dropbox Sign, Adobe Acrobat Sign, PandaDoc and signNow all work without an integration.
  2. 02
    Does the code have to run on your own servers?If yes, look at the open source options. Documenso and DocuSeal can both be self-hosted, and the signing data then sits in your own instance.
  3. 03
    Is someone else's signing screen fine inside your product?If yes, embed. Every product in the table except Esign Comply offers a signing view you can place in your app.
  4. 04
    Do you want the signing screen to be yours?Then build it, and hand the record to a third party. That is the model Esign Comply exists for.

What Esign Comply is for

Esign Comply is for people who build the signing flow themselves, with Cursor, Claude Code, v0, Lovable, Bolt or Replit, and want the two parts they should not build handled for them.

Prompt generator

The rules, as a prompt

Pick your use case, regions, signers and stack and get one prompt with the ceremony rules, drawn from the U.S. ESIGN Act, state UETA laws and leading U.S. online-assent decisions. Your AI tool builds the screens from it.

Prompt generator
API and headless SDK

The record, kept outside your app

The browser SDK reports each step from the signer's browser. The record is hash-chained, signed with keys you do not hold and timestamped by an outside authority, and anyone you give the evidence package to verifies it offline.

Evidence and verification
Your codebase

Everything else is yours

Upload, PDF viewer, field placement, signer emails and links, the signed PDF, the dashboard. That includes a full send-for-signature product with your name on it.

Build your own DocuSign

Send and embed give you a vendor's signing screen. Build your own, and a third party keeps the record.

Questions about e-signature APIs

What is the difference between send, embed and build-your-own e-signature APIs?

With send, the vendor emails the signer a link to a signing page that the vendor hosts. With embed, the vendor's signing screen is opened inside your app, in a frame or a component. With build your own, your app renders the signing screen itself and a separate service records the ceremony and keeps the evidence.

Which e-signature APIs are open source?

Documenso and DocuSeal. Documenso is published under AGPL-3.0 and DocuSeal under AGPLv3 with additional terms. Both can be run on your own servers and both also offer a hosted cloud. DocuSign, Dropbox Sign, Adobe Acrobat Sign, PandaDoc and signNow are commercial hosted products.

Which e-signature API lets me build my own signing UI?

Esign Comply. It has no hosted signing page and nothing to embed. Your app renders every screen, a headless browser SDK attaches to your own document view, name field, checkbox and button, and the API seals a record of the ceremony. The other products in the table render the signing screen themselves.

How the SDK works

Where is the signing evidence stored with each kind of API?

With a hosted send or embed product, the vendor keeps the audit trail and you download a copy. With a self-hosted open source product, it sits in your own instance, on your own servers. With Esign Comply, the record is kept by a third party to the agreement, and you store a signed receipt that ties your own row to it.

Why a third party keeps the record

Can I self-host an e-signature API?

Yes, with Documenso or DocuSeal, which are open source and run on your own servers. signNow also offers a private cloud solution that deploys on-premises or in your own cloud. Esign Comply is not self-hosted, on purpose: the point of its record is that someone other than you holds it.

Which e-signature API works best with AI coding tools such as Cursor or Claude Code?

Any of them can be called from code an AI tool writes. Esign Comply is built for that workflow: it generates one prompt with the signing rules for your use case, regions and stack, your tool builds the screens from it, and a conformance check over your test records shows what to fix before you go live.

Prompt generator

Build the signing screen yourself. Leave the record to us.

Free plan: 10 live signatures a month and a full test mode. No card required.

Sources

Each row of the table was checked against the vendor's own site or documentation on 22 November 2026. Vendors change their products, so follow the links for the current details.

  1. [1]DocuSign: Embedding, eSignature REST API concepts
  2. [2]DocuSign: How to request a signature by email (remote signing)
  3. [3]DocuSign: How to request a signature through your app (embedded signing)
  4. [4]DocuSign: Use of transaction data: the Certificate of Completion
  5. [5]Dropbox Sign: Signature request walkthrough
  6. [6]Dropbox Sign: Embedded signing walkthrough
  7. [7]Dropbox Sign: Understanding audit trails in Dropbox Sign
  8. [8]Adobe: Acrobat Sign developer guide: API usage
  9. [9]Adobe: Acrobat Sign embedded signing identity and authentication
  10. [10]Adobe: Acrobat Sign audit reports
  11. [11]PandaDoc: Create and send your first document
  12. [12]PandaDoc: Embedded signing, developer documentation
  13. [13]PandaDoc: Embedded signing, product page
  14. [14]signNow: Get started with the signNow API
  15. [15]signNow: Embedded signing
  16. [16]signNow: Private cloud solution
  17. [17]Documenso: Source repository and license
  18. [18]Documenso: Signing workflow
  19. [19]Documenso: Embedding
  20. [20]Documenso: Self-hosting
  21. [21]DocuSeal: Source repository and license
  22. [22]DocuSeal: Cloud and self-hosted options
  23. [23]DocuSeal: Embedded signing form
  24. [24]DocuSeal: API reference: submissions
  25. [25]DocuSeal: Quick start: signature certificate and audit log
  26. [26]Esign Comply: The ceremony, sessions and the browser SDK
  27. [27]Esign Comply: Evidence: sealing, receipt, report and package
  28. [28]Esign Comply: The open-source offline verifier

DocuSign, Dropbox Sign, Adobe Acrobat Sign, PandaDoc, signNow, Documenso and DocuSeal are trademarks of their owners. Esign Comply is not affiliated with them.

Working with an AI tool? This page is also available as Markdown: /compare/e-signature-apis.md