Adobe splits PDF and Sign.
Apdf is one API key.
Generate the PDF from HTML or Office files, send it as a personal link, see every page read and collect the signatures — one API, one published price, no sales call.
Why teams outgrow Adobe’s APIs.
Adobe generates excellent PDFs. Getting one read and signed means a second licence, a sales conversation and an analytics stack of your own.
Two licences
In Adobe’s own words, Acrobat Sign API licensing is separate from PDF Services API licensing — separate credentials, separate agreement.
Contact sales to grow
PDF Services is free for 500 document transactions a month. Past that, paid plans go through sales and a separate written agreement.
Signing needs a bigger plan
Parts of the Acrobat Sign API need its Business or Enterprise edition, and the Sign sandbox only comes with an enterprise-level account.
Bring your own analytics
The PDF Embed API fires page-view callbacks into your own Adobe or Google Analytics. No personal link per recipient, and Sign webhooks stop at “viewed”.
What you get instead.
Generation first, then everything after it — the link, the reading and the signature — on the same key and the same plan.
Generate, then keep going
HTML and Office files to PDF, merge, split, compress, OCR, watermark, protect and fill forms — one operation per call, whatever the page count. Then the same PDF goes out for reading and signing.
Reading, already tracked
Every recipient gets a personal link to a hosted viewer. Opens, page reads, comments and form entries arrive as webhooks with their name — no analytics suite to wire up.
Signing on the same key
Request signatures from up to ten signers on the PDF you just generated — no second licence, no enterprise plan. The sealed PDF comes back with its audit trail.
Apdf vs. Adobe
Both generate the PDF. Only one carries it on to the reader and the signature without a second contract.
Turning PDFs back into Word files? Use Adobe. Getting them read and signed? Use Apdf.
A price on the page,
not a sales call.
Adobe’s paid PDF plans and its Sign API both go through sales. Apdf publishes every plan — start free, upgrade by card when the test works.
500 document transactions a month, then contact sales.
- Paid quota needs a separate written agreement
- Acrobat Sign API licensed separately
- Sign sandbox only with an enterprise account
- Read analytics need your own analytics stack
Pro, paid by card — the whole team, one workspace.
- 20,000 PDF operations a month
- 50 signature requests and 50 tracked documents
- Generation, tracking and signing on one key
- Free plan: 1,000 operations a month, no card
Switch in an afternoon.
One key for everything Adobe splits across PDF Services, PDF Embed and Acrobat Sign. Your generation code barely changes; what comes after it gets shorter.
Swap the generation call
Send the same HTML or Office file to the create or convert endpoint. One API key replaces the client credentials.
Send a personal link
Add the PDF as a tracked document and create a link per recipient — no viewer to embed, no analytics suite to wire up.
Request the signatures
Name the signers and place the fields by text anchor, coordinates or form field. Events and the sealed PDF come back to your app.