11 Best PDF Filling APIs for Document Automation (2026)

TL;DR

• Anvil is the top pick for developers who want one REST API that fills PDFs, collects e-signatures, and runs full workflows.
• Anvil offers a documented fill endpoint that accepts JSON and returns a completed PDF. E-signatures and workflows are available when a project needs them.
• Anvil supports filling PDF templates independently of its optional e-signature and workflow products. Flat PDFs need template setup and a review of detected field placement.
• For HR onboarding, Anvil's casts conditional logic builds state- and role-specific packets from a single pipeline.
• For flat PDFs with no form fields, Anvil offers AI-assisted field detection and schema mapping on paid plans; review the resulting template before filling it through the API.
• Anvil's Free plan is UI-only until you add a card for metered API use. New metered accounts receive 2,500 starter PDF fill/generation credits, then pay $0.10 per fill or generation; test mode is unlimited. See Anvil's pricing.

What Is a PDF Filling API?

A PDF filling API lets you write data into a PDF programmatically, sending a JSON payload of field values and receiving a completed document back. A fillable PDF carries embedded form fields, each one a named object an API can target directly. A flat PDF has no interactive form fields, though its text may still be selectable. A form-field filling API cannot target named fields until someone prepares a template or places values at specified coordinates. Filling a flat PDF means detecting where the fields should go and placing data at those coordinates, which may require manual template setup or a tool that detects field positions. When you evaluate a PDF filling API, check whether it handles flat PDFs natively, because many forms you receive from clients and agencies arrive flattened.

Quick Picks by Use Case

• Simplest REST integration: Anvil. POST a JSON body keyed by template field aliases to one endpoint and get filled PDF bytes back, with SDKs for JavaScript, TypeScript, Python, and C#/.NET.
• E-signature and fill in one workflow: Anvil combines fill, e-sign, and webform building blocks in a single Workflow, so you avoid stitching together two vendors.
• HR onboarding automation: Anvil. Conditional logic builds state- and role-specific packets, as covered in Anvil's HR onboarding comparison.
• Repeated template fills: Anvil. Send an array of data objects to fill a template multiple times and receive one merged PDF, subject to the fill API's 1 MB JSON request-body limit. Metered usage is $0.10 per fill after starter credits.
• Compliance-heavy regulated industries: DocuSign for enterprise signature orchestration. Its Developer API plan matrix lists SOC 2 Type II across tiers, advanced eIDAS options on Enhanced, and HIPAA support through a BAA as "Contact sales" on Enhanced.
• Flat PDF template setup: Anvil. AI-assisted field detection and schema mapping can help prepare PDFs without an existing form layer; check field placement before using the template in production. API access to Document AI starts with AI Pack.

11 Best PDF Filling APIs for Document Automation

These 11 options serve different jobs. Compare fill-and-return APIs with signature-led platforms and document SDKs based on how your application prepares templates, returns completed PDFs, and handles signing.

For API-first filling: Anvil offers metered PDF fills at $0.10 each after starter credits. Its Product Pack costs $425/month before metered usage and adds signing features. Compare total costs at your expected volume, including any plan, signing, and workflow charges.

Anvil

Anvil can turn a flat PDF without interactive form fields into a template for API filling. Its AI-assisted field detection helps identify where values belong, and schema mapping can connect detected fields to your existing keys. Review field placement and mappings before using a template in production; programmatic Document AI access is included with AI Pack. You can test the upload flow without signing up using Anvil's PDF filling API.

The fill API itself is a single REST endpoint. You POST a JSON body to https://app.useanvil.com/api/v1/fill/{pdfTemplateID}.pdf with a data object keyed by template field aliases, and Anvil returns the filled PDF as binary bytes. Nested objects work for grouped fields like an address split into street, city, and state, and top-level keys let you set title, font size, and text color in the same call, as detailed in Anvil's fill API docs.

Anvil provides SDKs for JavaScript and TypeScript, Python, and C#/.NET. For other languages, use the documented REST API. Conditional logic runs through Anvil's "casts" language, so a packet can change its composition based on the data you send. A full-time California hire and a Texas contractor receive different documents from the same pipeline, an approach covered in Anvil's HR onboarding comparison.

Fill is one building block among several. Anvil combines fill, e-signature, and webforms inside Workflows, and you can publish a Workflow as its own production API for downstream systems to call. A Zapier integration covers no-code automation. For repeated fills, the fill API accepts an array of data objects and merges the results into one PDF; JSON requests have a 1 MB body limit.

Pricing is metered and published upfront. PDF fills cost $0.10 each on a pay-as-you-go basis, and new accounts get 2,500 starter credits before billing begins. The Free plan is UI-only until a card enables metered API use; unlimited test mode is available. AI Pack costs $99/month and adds API access to Document AI and schema mapping, while Product Pack costs $425/month and adds advanced signing. Anvil's pricing page lists HIPAA and DPA under Enterprise and references BAA in its feature comparison. Confirm BAA availability and terms for your proposed agreement. Annual billing cuts 20% off, and Anvil holds SOC 2 Type II, GDPR, HIPAA, and eIDAS compliance, as listed on Anvil's pricing page.

Best for: Developers who want flat PDF support, fill, e-signature, and composable workflows behind one clean REST API.

DocuSign

DocuSign built its business on enterprise e-signature, and the API reflects that priority. Most teams reach for it when they need signature orchestration at scale, with routing rules, multi-party approval chains, and the audit trails that legal and compliance departments demand. For regulated use, check the security documentation and contractual terms for the DocuSign product and plan you intend to buy. Its developer pricing marks HIPAA support through a BAA as a sales inquiry rather than a standard Starter entitlement.

PDF filling exists in the DocuSign API, but it sits underneath the signature workflow rather than standing on its own. You can place fields on a document and populate them before sending for signature, yet the model assumes the end goal is a signed agreement. If you want to fill a PDF and return the bytes without involving a signing ceremony, you fight the grain of the product. Developers building pure document generation pipelines, where the output is a completed form rather than an executed contract, find the signature-first design adds steps they do not need.

Flat PDFs expose the same limitation. DocuSign expects you to tag fields by hand or work from documents that already carry form fields, so a stack of scanned government forms means manual placement before any automation runs. Anvil's Document AI can detect candidate fields during template setup, but you should review their placement before filling documents through the API.

DocuSign's US production Developer API plans start at $50/month on annual billing for Starter and 40 sent envelopes. Intermediate is $300/month for 100 envelopes, and Advanced is $480/month for 100; Enhanced, which lists embedded signing, is custom-priced. HIPAA support through a BAA is marked “Contact sales” on Enhanced. Personal and Standard web-app seat prices are not production Developer API prices.

Best for: enterprises that need signature orchestration and compliance coverage as the primary job, with PDF filling as a supporting step rather than the core workflow.

PandaDoc

PandaDoc builds documents from templates and drives them through a sales cycle, which makes it strong for proposals, quotes, and contracts tied to a CRM. Its editor lets your sales team assemble a proposal from reusable blocks, drop in pricing tables, and route it for signature without touching code. Native connectors to Salesforce, HubSpot, and Pipedrive pull deal data straight into the document, so a rep can generate a quote from an opportunity record in a few clicks.

PandaDoc also has a documented template API, so its editor-first approach does not rule out programmatic document creation. For an existing PDF fill-and-return pipeline, compare its template preparation and API document allowances with a dedicated JSON-to-filled-PDF endpoint. If your goal is to take an existing flat PDF, map field IDs to values, and return filled bytes on demand, PandaDoc routes you toward template authoring in its UI rather than a clean fill-by-ID endpoint like Anvil's fill/{pdfTemplateID}.pdf.

Pricing splits across two lines. Platform plans are per seat, at $19 per seat per month for Starter and $49 per seat per month for Business, per PandaDoc's pricing page. Its dedicated Developer API pricing lists a free tier of 60 documents a year and an API Developer plan at $40/month for 40 documents. On standard seat plans, optional API creation instead uses purchased Usage Credits after first-time trial credits; API document creation pauses when credits run out.

At volume that matters. A pipeline filling several hundred PDFs a month runs past the 40-document developer tier immediately and into a quoted plan, while Anvil's metered model charges $0.10 per fill, so 500 fills costs $50. PandaDoc's pricing makes sense when the document includes editing, approval routing, and signature. It makes less sense when the job is fill-and-return.

Best for: sales and revenue teams generating CRM-linked proposals and quotes, not developers building bulk programmatic PDF fill pipelines.

Dropbox Sign

Dropbox Sign, the rebranded HelloSign, runs a dependable e-signature API with broad SDK coverage, but it leans on signature orchestration rather than native PDF fill intelligence. You upload templates and route them for signing, yet the API gives you no automatic field detection on a flat PDF the way Anvil's Document AI does. If your documents already carry form fields and your main job is collecting signatures, that gap rarely matters. The wall comes when you need to fill an unstructured PDF programmatically.

The API ships official SDKs for Python, Node, PHP, .NET, Ruby, and Java, with a published OpenAPI spec and a "Try it" console in the documentation (developers.hellosign.com). Field types cover signature blocks, text fields, checkboxes, dates, dropdowns, radio buttons, and signer attachments.

Pricing splits into three tiers, all quoted on annual billing. Essentials starts at $75 a month, billed annually as $900, for 50+ signature requests and 5 templates. Standard starts at $250 a month, billed annually as $3,000, for 100+ requests and 15 templates. Premium moves to contact sales for unlimited templates, per the Dropbox Sign API pricing. The endpoint set scales with the tier.

That tier gating creates real friction, because embedded template creation through template/create_embedded_draft and template/update_files/{template_id} is listed only under Premium, according to the Dropbox Sign developer docs. Dropbox Sign's marketing pricing table shows an embedded templates row checked on Standard as well, so the two pages disagree; the two pages do not establish a clear entitlement for that endpoint. Confirm access to embedded template creation for the plan you are considering.

Rate limits sit at 100 requests per minute for standard endpoints and drop to 25 per minute for signature send, template, file, and unclaimed-draft endpoints, with test mode capped at 10 per minute, as documented in the Dropbox Sign API reference. Free accounts can exercise every endpoint with test_mode=true, though documents come watermarked and are not legally binding.

Best for: teams that need a reliable, well-documented e-signature API on pre-built fillable templates and don't need automatic field detection on flat PDFs.

Adobe Acrobat Sign

Adobe Acrobat Sign combines Adobe's established PDF editing tools with e-signature capabilities, making it a natural fit for teams that already create and manage documents in the Adobe ecosystem. Acrobat Standard runs $14.99 per month and Acrobat Pro $19.99 per month on an annual plan, per Adobe's Acrobat pricing. Teams can prepare PDFs, tag fields, and route documents for signature without moving them into a separate document environment.

Acrobat Sign does place fields on flat documents automatically. It scans for visual cues that suggest where fields belong, and skips the scan when a file already carries AcroForm fields or text tags, per Adobe's authoring documentation. Adobe describes this as visual-cue detection rather than AI-assisted detection, and it runs inside the authoring UI.

The gap for a backend service is shape, not coverage. The authoring feature described above detects fields in Adobe's interface. It does not, by itself, establish an API that accepts field IDs and returns a completed PDF, so assess Acrobat Sign's API separately if your application needs fill-and-return automation.

Best for: Adobe-native teams that prioritize hands-on PDF editing and e-signature over a programmatic fill-by-ID API.

Formstack

Formstack ties no-code document generation to online form building, allowing non-technical teams to turn form submissions into documents and route them through repeatable workflows. That suits operations teams that want to collect information through online forms, generate documents from the responses, and add e-signature without building the entire workflow in code.

Formstack does not sell a standalone Documents plan. The Formstack Suite bundles Forms, Documents, and Sign starting at $250 a month, billed annually. The pricing display also shows $299, but does not establish it as the current month-to-month rate. The Suite includes 250 document deliveries a month and unlimited e-signatures.

The platform is less suited to a backend service that needs a pure REST fill-by-ID endpoint. Formstack Documents expects you to define merge fields up front and steers users toward Word templates rather than fillable PDFs, so a document with no existing field layer requires setup rather than automatic tagging. Compared with Anvil, it favors no-code workflows built around form submissions over direct programmatic filling of arbitrary PDFs.

Best for: non-technical teams building no-code document generation and signing workflows from online form submissions.

PDF.co

PDF.co runs a broad REST API for PDF manipulation. Form filling, field extraction, flattening, merging, splitting, OCR, and barcode reading all live behind one credit-based plan structure rather than separate products, which makes it a reasonable pick for a team that needs several PDF operations beyond just filling.

The credit model is the thing to understand before committing. Plans consume credits per request, and the rate varies by endpoint: some calls bill per call and others bill per page, per PDF.co's pricing documentation. That makes budgeting less predictable than a flat per-document rate.

PDF.co can stamp a signature image onto a PDF, but there is no signature-request workflow behind it: no signer routing, no signing order, no audit trail, and no workflow orchestration layer. If a project needs real signature collection on top of filling, PDF.co expects a second vendor for that half of the pipeline, the same gap Anvil's Workflows close by combining fill, sign, and multi-step logic in one place.

Pricing starts at $8.99/month for 16,500 credits and climbs to $270/month for 483,000 credits on the Business 3 plan, all on annual billing, per PDF.co's pricing page. Month-to-month billing costs more. The $44.99/month Business 1 tier, at 80,500 credits, is the most popular option and stays well under a $500 budget.

Best for: teams that need a wide PDF manipulation API surface and don't need signature collection or workflow orchestration bundled in.

pdfFiller

pdfFiller built its product around an embedded PDF editor first, with API access added on top. The editor covers annotation, form building, and hosted fillable form links, which suits a team that wants end users to interact with PDFs through a visual interface rather than a pure backend pipeline.

pdfFiller does include e-signature, with role assignment, signing order, and scheduled reminders, so the difference against Anvil is shape rather than coverage. A developer building a pure fill-by-ID pipeline, the way Anvil's PDF filling API works, will find pdfFiller's editor-centric design adds UI concepts that a backend service does not need.

The pdfFiller developer site's Transparent Pricing tab lists Starter at $1,000 per year for 1,000 documents ($1.00 per document), Professional at $3,000 per year for 4,000 documents ($0.75 per document), and Enterprise at $5,000 per year for 10,000 documents ($0.50 per document). It also invites developers to try the API for free, without stating a free document allowance. These are annual API plans, not consumer subscription prices; compare annual costs and included document volumes against your expected usage.

Best for: teams that want an embeddable PDF editing interface for end users, not developers building a bulk programmatic fill pipeline.

DocSpring

DocSpring fills PDF templates from JSON through a REST API and also offers signature requests. Its pricing uses credits for document generation and adds credits for each signer asked to sign or initial. DocSpring's pricing page lists AI-assisted field setup, so compare template-preparation allowances as well as PDF and signer costs.

DocSpring's current pricing lists a free Developer plan with 200 credits per month, enough for about 10 filled PDFs of up to 10 pages. Starter is $49/month for 10,000 credits, or about 500 such PDFs at 20 credits each; Growth starts at $149/month, and Scale at $399/month. Longer or more complex documents can use more credits. Every plan includes API access and test PDFs; paid-plan credits roll over for 12 months. A signature request adds 60 credits for each signer asked to sign or initial, on top of the PDF's credit cost.

DocSpring's AI field setup includes 5 free pages per month on Developer and 50 on Starter, with extra AI setup pages priced at $0.25 each. Compare that allowance with Anvil's Document AI and review detected field placement before using either template in production.

Best for: developers who want a credit-based PDF filling API with AI field setup and optional signature requests, and can estimate document and signer credits for their workload.

Apryse

Apryse, formerly PDFTron, sells a modular document SDK spanning web, server, and mobile, with add-ons for DOCX editing, spreadsheet handling, digital signatures, and smart data extraction. It is built for teams embedding a full-featured document viewer or processing engine into their own product, not for a lightweight fill-and-return API call.

Pricing reflects that scope. Entry-level packages start at $1,500, according to Apryse's own pricing page, with no self-serve tier below that and no published rate card beyond the entry point. Every plan beyond entry level routes through a custom quote based on features, document volume, and deployment model.

Because Apryse's pricing page does not state a billing interval for its $1,500 entry-level package, that figure cannot establish a monthly cost or rule out every configuration under a $500/month budget. A team evaluating Apryse against Anvil's $0 free tier and $99/month AI Pack is comparing an enterprise SDK license to a metered API, not two versions of the same product.

Best for: enterprises that need a heavyweight, customizable document SDK across web, mobile, and server, not budget-conscious teams looking for an API-first fill service.

Nutrient

Nutrient, formerly PSPDFKit, shares Apryse's SDK-first heritage: an embeddable viewer and processing engine rather than a simple REST endpoint for filling a PDF and getting bytes back. Teams already running an embedded document viewer in their product are the natural fit, since Nutrient's strength is the viewer experience itself, not a bare fill API.

Nutrient's SDK licensing is quote-based, so the published information does not establish whether a particular deployment costs more or less than $500/month. Nutrient's cloud pricing page lists separate product pages for its Processor API and Viewer API. Check the quote or agreement to determine what an SDK license includes.

Flat PDF filling still works through the SDK's configuration rather than an auto-detection feature, so a document with no embedded form fields needs manual setup work, the same gap that separates every SDK-first tool here from Anvil's Document AI auto-tagging.

Best for: enterprises already invested in an embedded SDK viewer workflow, or teams that want Nutrient's cloud APIs for individual processing operations rather than a fill-and-sign pipeline.

How to Fill a Flat PDF with an API

A flat PDF has no interactive form fields for a form-filling API to target. Its text and lines may still be selectable page content, so the problem is placing values, not necessarily extracting the page as an image. When you hit one for the first time, the usual approach breaks because there are no field objects to iterate over, so a standard fill library has nothing to target.

For a PDF without form fields, prepare a reusable template before sending fill requests. You can place fields manually or use assisted detection, then check each field's position and name against the document.

Anvil's Document AI removes that work in a few steps.

• Upload any PDF, including a flat one with no existing form fields.
• Auto-detect runs Anvil's line and box detection to find field positions and tag them with coordinate placement.
• Map your data as a JSON data object keyed by template field aliases, with nested objects supported for grouped fields like an address.
• Fill by POSTing to the template endpoint, which returns the completed PDF as binary bytes.

You can test the upload and detection flow without a signup. Rather than stitch together a vision model, an image renderer, and an annotation layer yourself, you point Anvil at the flat PDF and let it handle field placement. Anvil's assisted setup is useful when you need to prepare flat PDFs for repeated API fills.

How We Chose These 11 PDF Filling APIs

We ranked these APIs on the criteria that decide real document automation projects, not feature checklists. API maturity came first. A tool needs documented REST endpoints, official SDKs across major languages, and webhooks for event-driven pipelines before it belongs in a developer's stack.

Flat PDF support carried heavy weight because documents without embedded form fields require template preparation before a field-based API can fill them. A fill API that handles only pre-tagged PDFs solves only half the problem.

We checked whether each tool combines fill and e-signature in a single workflow, since the alternative is paying two vendors and maintaining the handoff between them. Anvil's HR onboarding comparison walks through what that looks like in a real packet.

Pricing transparency mattered next. Published per-call rates let you model costs at volume, and vague "contact sales" tiers do not.

Finally, we weighed compliance certifications like SOC 2 Type II, HIPAA, and eIDAS, alongside developer experience measured through docs quality, test modes, and SDK ergonomics.

FAQs

What is a PDF filling API and how does it work?

A PDF filling API accepts structured data and writes it into a PDF template, returning the completed document. With Anvil, you POST a JSON body keyed by template field aliases to a REST endpoint, and the API returns the filled PDF as binary bytes. You skip manual data entry and generate documents directly from your application.

What's the difference between a fillable PDF and a flat PDF?

A fillable PDF contains embedded form fields that software can read and write programmatically, while a flat PDF has no interactive form fields, even if its text is selectable. Most APIs can write to fillable PDFs out of the box but stumble on flat ones. Anvil's Document AI detects field positions on flat PDFs automatically, so both types work the same way.

Can a PDF fill API handle flat PDFs with no form fields?

Yes, but only if it can locate where data should go without existing field objects. Anvil uses line and box detection to place text by coordinates on flat PDFs, then exposes those positions as named fields you can map JSON to. Adobe Acrobat Sign scans flat documents for visual cues inside its authoring UI, which helps a person preparing a document but is not a fill-by-ID API. PDF.co and Apryse handle flat PDFs through general-purpose extraction tools without auto-tagging fields. DocSpring also offers AI field setup, while other products may require different template preparation steps; check each provider's current API workflow before assuming that a flat PDF can be filled directly.

How much does a PDF filling API cost?

Anvil charges $0.10 per fill as metered pay-as-you-go usage, and new accounts get 2,500 starter credits before billing begins, per Anvil's pricing page. After starter credits are used, 1,000 fills cost $100 in metered usage, plus any applicable plan charges. For comparison, DocSpring offers a free Developer credit allowance and a $49/month Starter plan with 10,000 credits, where a filled PDF of up to 10 pages costs 20 credits and each signer adds 60 credits, PDF.co runs on a credit system starting at $8.99/month on annual billing, and pdfFiller's API Starter plan costs $1,000 per year for 1,000 documents ($1.00 per document); higher annual tiers list $0.75 and $0.50 per document. Apryse starts at $1,500 for an entry package. Nutrient's SDK is quote-based, while its cloud API products publish separate pricing pages. Bulk pre-purchase discounts on Anvil unlock at 25,000 fills.

Which PDF filling API is best for HR onboarding?

Anvil fits HR onboarding because it combines fill, e-signature, and conditional logic in one workflow. Conditional rules build different packets by state, employment type, or department, so a full-time California hire and a Texas contractor receive the right forms automatically without a second pipeline.

Which tool is best for high-volume batch PDF generation?

Anvil's fill API accepts an array of data objects to fill a template multiple times and returns one merged PDF. A JSON request body is limited to 1 MB, so test how many repeats your actual payload can hold. The AI Pack and Product Pack plans raise the rate limit to 40 requests per second, and the metered $0.10 per fill keeps the cost per document predictable as volume grows.

Do I need a separate API for e-signatures?

Not with Anvil, which combines fill, e-sign, and webform building blocks in one workflow. DocuSign and Dropbox Sign lead with signature orchestration but treat PDF filling as secondary, so pairing them with a generation tool often means stitching two services together. PDF.co's capabilities described here do not include a signature-request workflow; DocSpring does support signature requests and charges signer credits in addition to document credits. Check the relevant Apryse and Nutrient modules before deciding whether you need a separate signing service. pdfFiller, Formstack, and Adobe Acrobat Sign do include e-signature, but compare their API documentation against your required fill-and-return flow rather than assuming their authoring tools provide it.

What's the cheapest PDF filling API under $500 a month?

For PDF manipulation without a signature-request workflow, PDF.co's Business 1 plan runs $44.99/month on annual billing. DocSpring's Starter plan is $49/month for 10,000 credits, and it also supports signature requests at an additional 60 credits per signer asked to sign or initial, on top of the PDF cost. Compare the credit requirements of your actual documents before treating either plan as a per-PDF rate. Anvil's Free plan is UI-only until a card enables metered API use. New metered accounts receive 2,500 starter PDF fill/generation credits, then pay $0.10 per fill or generation; test mode is unlimited. AI Pack is $99/month for programmatic Document AI access, while Product Pack is $425/month for advanced signing features. Compare those costs with the signing and workflow features your project requires.

Why Anvil Leads for Document Automation in 2026

Anvil is a strong fit when an application needs JSON-to-filled-PDF output and may later add signing or workflows through the same platform. DocuSign and Dropbox Sign handle signatures well but treat programmatic PDF filling as secondary. PandaDoc is built for sales proposals, not developer-driven fill pipelines. Adobe Acrobat Sign and Formstack cover editing and no-code generation, but both work through an authoring UI rather than a fill-by-ID endpoint. PDF.co covers broad PDF processing, while DocSpring adds signature requests and AI field setup to its document API; compare its credit-based costs with Anvil's separate fill, signing, and workflow charges. pdfFiller emphasizes an embedded editor and lists annual API plans from $1,000 for 1,000 documents to $5,000 for 10,000 documents. Apryse and Nutrient deliver enterprise-grade SDKs, but Apryse starts at $1,500 and neither bundles e-signature.

Anvil's AI-assisted template setup can reduce manual coordinate mapping for flat PDFs, though detected fields and schema mappings still need review. The REST endpoint accepts a JSON body and returns filled PDF bytes, with official SDKs for JavaScript, TypeScript, Python, and C#/.NET. Pricing is $0.10 per fill, with 2,500 starter credits and bulk discounts past 25,000 fills. For HR, lending, or insurance use, check Anvil's published security and plan details against your specific compliance and contractual requirements, including whether a BAA is available on the plan you need. For teams starting with JSON-to-filled-PDF generation, Anvil's fill endpoint provides a direct path from template data to a completed PDF, with signing and workflows available when the application needs them.