PandaDoc API Pricing: What the PandaDoc API Costs per Document, and When a Render API Is Cheaper

PandaDoc runs two price lists that are easy to confuse. The standard plans on pandadoc.com/pricing are sold per seat: Starter at $19 and Business at $49 per seat a month billed annually, with a free plan capped at 5 documents a month and an Enterprise tier described as "per seat or per document pricing". On that list, the API appears only in the Enterprise column. The second list lives on the developer site and is the one that matters if you are writing code against PandaDoc.

The FAQ on the same page adds three things worth knowing before you sign. Production access is up to 300 documents created per minute. There is a startup package for teams that are unsure how many calls they need over a 12 month contract, quoted on request. And the unit being counted is described in two slightly different ways, which is the subject of the next section.

Compare that with the per-seat side of the house. If a sales team of eight already sits on Business at $49 a seat, that is $4,704 a year, and it still does not include the API. The developer plan is a separate purchase, which surprises teams who assume the seats they already pay for cover an integration.

The API Developer card says "Includes 40 documents sent per month, then $4 per additional document sent." The FAQ on the same page says "PandaDoc API charges based on the volume of documents generated via Production API. You can generate documents by uploading your existing document or using one of our templates." Elsewhere PandaDoc describes a usage credit as any document created through the API, web forms, bulk send or automation tools such as Zapier and Make.

For an app that sends everything it creates for signature, the difference does not matter. For an app that creates a quote, lets a salesperson look at it and only sends one in three, it is the whole bill. On the "sent" reading, a month with 900 documents created and 300 of them sent costs $40 plus 260 times $4, or $1,080. On the "generated" reading the same month costs $40 plus 860 times $4, or $3,480.

We are not going to guess which reading applies to your contract, and neither should you. Ask for it in writing, with the words "created", "sent" and "completed" defined, before you commit to a volume. It is the single question most likely to move a PandaDoc API quote, and the vendor has already shown you that its own pages use the words interchangeably.

Look at what the $4 is paying for: a legally binding e-signature under ESIGN and eIDAS, a signing experience, reminders, an audit trail and a hosted copy of the completed document. That is a reasonable price for a signature. The e-signature APIs we compared on the same job run from about $0.20 a completion on DocuSeal to $1.50 a request at the Dropbox Sign Essentials anchor and more on Docusign, so PandaDoc sits at the premium end, but it sits there with an embedded editor and a template library the others do not ship.

Most software that generates documents is not generating contracts, though. It generates invoices, order confirmations, statements, packing slips, certificates, quotes that are accepted by clicking a button in the app, and monthly reports. Those documents need to be correct, branded, paginated and kept, and they need nobody's signature. Push them through a signature platform and each one is billed as if it did.

The numbers make the point quickly. A billing system producing 1,000 invoices a month pays $3,880 on the PandaDoc Developer card. Rendering those same invoices from your own HTML template on an API that meters renders costs $29, and at that tier the first 10,000 are covered. The difference is not a discount; it is two different products being priced for what each one does.

The pattern is simple. Your app renders every document from its own HTML template, which it probably already has because the same invoice or quote is shown in the browser. The rendered PDF is stored and delivered. For the minority of documents that need a signature, your app hands that PDF to a signature API as the envelope's document, and pays the signature rate on those alone.

At 1,000 documents a month with 150 signed, that is $29 for rendering plus about $50 on DocuSeal, $79 in total, against $3,880 on the PandaDoc Developer card. Swap DocuSeal for BoldSign at $0.75 an envelope and the signature leg is about $113, still under $150 all in. Every figure for the signature leg, and the tradeoffs between those vendors, is on the e-signature API pricing comparison.

The split also fixes a problem that has nothing to do with price. When the document is produced by your own template, it looks exactly like the version your customer saw in the app, down to the font and the page breaks. A dated archive copy of every render means you can show later precisely what was issued, which matters for invoices and statements whether or not anyone signed them. The rendering side of that is covered on the document generation API comparison, which puts template-merge engines and HTML renderers side by side.

If almost every document you create is a contract, a proposal or an order form that gets signed, PandaDoc is a strong choice and the per-document price is not the problem it looks like. At 40 signed documents a month the Developer plan is $40, which is less than the split once you add a signature seat. You also get things a renderer does not have at all.

• An embedded editor. Your users can adjust a document inside your app before it goes out, which a render-from-template flow does not offer without you building an editor.
• Pricing tables and CPQ on Enterprise, so a proposal can calculate its own totals and options as the buyer picks them.
• Signing, reminders and the audit trail in one vendor. One contract, one webhook model, one place for legal to look.
• Pre-built CRM integrations with Salesforce and HubSpot on Enterprise, for teams that want documents to start from a deal record.

If that is your workload, the thing to negotiate is the Enterprise volume rate and the definition of a document, not the vendor. SitePDF does not do e-signatures or in-app document editing, and we would not suggest replacing PandaDoc where those are the reason you bought it.

Three moves, in order of how much they save. First, take the unsigned documents out. Invoices, receipts and reports rarely need to go through a signature platform, and every one that leaves saves $4 on the card rate. Second, stop creating drafts you do not send, or get the "sent" definition in writing, because on the generated reading a draft costs the same as a completed contract. Third, if you are past a few hundred documents a month, ask for the Enterprise volume rate with those numbers in hand; the Developer plan is the ceiling the conversation starts from.

If you arrived here from a Salesforce org, the Salesforce-native document generation apps work differently again, sold per user rather than per document, and the Conga Composer pricing comparison covers what Conga, Nintex DocGen, S-Docs and PDF Butler publish. For a wider view of per-document API prices across twelve vendors, see the PDF API pricing comparison.