Logo

Dropbox Sign is one step.
Apdf is all three.

Generate the agreement from your HTML, send it as a personal link, see every page read and collect the signatures — behind one API key, for less than a signature-only plan.

Free plan, no card Unlimited team members API on every plan
Generate, track, sign Live
document:loaded Northwind · CEO
page:read p3 · 52s
signature:signed Northwind · CEO
signature:completed sealed PDF
Streamed to your stack
API
Webhook
MCP
Sound familiar?

Why teams outgrow the Dropbox Sign API.

Dropbox Sign does one step well: the signature. The PDF before it and the reading around it stay your problem — and every extra request moves you up a plan.

$75 for 50 requests

The Essentials API plan is $75 a month for a starting 50 signature requests. Doubling to 100 means Standard, at $250 a month.

Bring your own PDF

Documents arrive as files or file URLs. There’s no HTML to PDF, and no merge, compress or OCR endpoint — that’s a second vendor.

One “viewed” event

Callbacks report sent, viewed, signed and declined. Viewed is one event — nothing on which page was read, or for how long.

Free means three

The free package allows up to three signature requests a month. Test mode is free, but its requests are watermarked and not legally binding.

What you get instead.

The signature, plus the step before it and the reading around it — one key, one plan, every step reported to your app.

50 requests $39 / mo
100 requests $69 / mo
generation & tracking included
More signatures per dollar

Pro covers 50 signature requests a month for $39 and 100 for $69 — up to ten signers each, with the sealed PDF and its audit trail. No plan jump to double the volume.

<html> PDF
fill form merge compress
The PDF, generated

Render the agreement from your HTML or fill a PDF form, merge in the annexes, compress it — then request the signatures with the same key. No second vendor for the PDF.

event: "page:read"
page: 3
your webhook
Every read, not one “viewed”

Opens, page reads, comments and form entries reach your app as typed events with the signer’s name — so a nudge goes to the signer who stalled on page three, not to everyone.

Side by side

Apdf vs. Dropbox Sign

Both collect the signature. Only one also makes the PDF and tells your app how it was read.

Capability
Apdf
Generate · track · sign
Dropbox Sign
Signature API
E-signatures with audit trail
100 signature requests a month
$69/mo
$250/mo
Real signatures on the free plan
5 a month
3 a month
Signature events as webhooks
Pro plans
Page reads as webhooks
Pro plans
One "viewed" event
Comments and form entries as webhooks
Pro plans
Generate PDFs from your own HTML
Files or URLs only
Merge, split, compress, OCR
MCP server for AI agents
Pro plans
Docs search only
EU data residency
Premium
Qualified signatures via eID
Paid add-on
Included Limited / gated Not available

Need qualified signatures? Use Dropbox Sign. Sending from your app? Use Apdf.

The math

Half the price,
all three steps.

Dropbox Sign charges for the signature step alone. Apdf prices the workspace — generation, tracking and signatures in one plan.

Dropbox Sign
$75 / mo

Essentials API — a starting 50 signature requests a month.

  • 100 requests a month: Standard at $250/mo
  • No PDF generation or PDF operations
  • One “viewed” event, no reading data
  • Free package: three requests a month
Apdf One flat price
$39 / mo

Pro — the whole team, one workspace.

  • 50 signature requests a month — 100 for $69
  • Generation and 20,000 PDF operations included
  • Page reads, comments and signatures as webhooks
  • Hard caps, never an overage charge
Low switching cost

Switch in an afternoon.

Same shape as a Dropbox Sign request: a file, the signers and their fields. What changes is what comes back.

1

Generate or bring the PDF

Render it from HTML, fill a PDF form, or pass the URL of the file you already send — the same way you passed file URLs before.

2

Send the request

One signature request names the signers and places the fields by text anchor, coordinates or the PDF’s own form fields.

3

Swap callbacks for events

Point an automation at your endpoint. Signed, declined and completed arrive there — and every page read before them.

Questions

Switching, answered.

For apps that send agreements as a link and need them signed, yes — and it adds the two steps around the signature: generating the PDF and tracking how it was read. If your documents legally require qualified signatures, Dropbox Sign offers them through eID and we don't.
Dropbox Sign's Essentials API plan is $75 a month ($900 billed yearly) for a starting 50 signature requests, and Standard is $250 a month for 100. Apdf Pro is $39 a month for 50 signature requests and $69 for 100, with tracked documents and 20,000 PDF operations a month included (40,000 at $69), unlimited members and hard caps. The free Hobby plan includes 5 signature requests a month.
Apdf signatures are simple electronic signatures: each signer confirms with a code sent to their email, and the sealed PDF carries an audit trail and a trusted timestamp. Where the law asks for a qualified signature, Dropbox Sign offers one through eID as an add-on; we don't.
Dropbox Sign's callbacks report sent, viewed, signed, all signed and declined. Apdf sends signature:signed, signature:declined and signature:completed — plus document:loaded, page:enter, page:read every 15 seconds while a reader stays on a page, page:leave, link:clicked, form:submit and annotation:create, each with the recipient behind the link.
Yes. Send HTML and get a PDF back, convert Word, Excel or PowerPoint files, or fill an existing PDF form by field name. Merge, split, compress, OCR and watermark run through the same API. Then add the PDF as a tracked document and request signatures on it.
Yes. Apdf's MCP server lets an agent generate a PDF, create tracking links, read sessions and page reads, and request signatures — agents request, only people sign. Dropbox Sign's official MCP server searches its documentation.

Generate, track and sign.
From one API key.