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 holds a 4.7/5 rating across 35 G2 reviews and carries SOC 2 Type II, HIPAA, GDPR, and eIDAS compliance.
• Anvil is the only tool here that detects fields on a flat PDF, fills it, signs it, and routes it through a workflow without a second vendor in the mix.
• 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's Document AI auto-detects fields using line and box detection, so you skip manual coordinate placement.
• Anvil's free plan covers 500 API calls per month, with additional calls at $0.10 each.

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 is a static image of a document with no machine-readable field layer, so there is nothing for the API to write into. Filling a flat PDF means detecting where the fields should go and placing data at those coordinates, which most tools cannot do on their own. 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 field IDs 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.
• High-volume batch generation: Anvil. One API call produces hundreds of personalized packets, and pricing runs $0.10 per call past the free 500/month.
• Compliance-heavy regulated industries: DocuSign for enterprise e-signature orchestration with SOC 2 Type II, HIPAA, and eIDAS coverage at scale.
• Flat PDF tagging: Anvil. Document AI auto-detects fields on PDFs with no existing form layer using line and box detection, so you skip the manual vision-model workaround.

11 Best PDF Filling APIs for Document Automation

Eleven tools lead PDF filling and document automation in 2026. They split between developer-first fill APIs and signature-led platforms that treat filling as a side feature.

Best for high-volume, API-first teams under $500/month: Anvil's Product Pack runs $425/month and adds white labeling and advanced signing modes on top of the AI Pack, with fill, e-signature, and workflow usage metered separately at $0.10 per PDF fill. New accounts start with 2,500 fill credits. PDF.co and DocSpring price lower per plan, but neither offers a signature-collection workflow at any tier, so budget-conscious teams end up stitching a second vendor into the stack regardless of which one they pick.

Anvil

Anvil is the only tool here that fills a flat PDF without you writing tagging code first. Upload any PDF and Anvil's Document AI auto-detects form fields, including documents with no interactive widgets at all. For flat PDFs it uses line and box detection to place fields by coordinate, so a static government form becomes fillable without manual setup. 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 field IDs, 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 ships official open-source SDKs for JavaScript and TypeScript, Python, and C#/.NET, plus a community-supported Go library, each with typed models and streaming download support. 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, and a single API call can generate hundreds of personalized packets at once.

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 includes 500 API calls a month, paid platform plans start at $99/month for the AI Pack, and bulk pre-purchase discounts unlock at 25,000+ fills. 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. The platform carries the certifications regulated industries require, including SOC 2 Type II, HIPAA support, and eIDAS through its status as a qualified trust service provider in Europe, which is why banks and insurers default to it for contract execution.

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 removes that step by auto-detecting fields on upload.

DocuSign publishes self-serve pricing for Personal at $11/month, Standard at $30 per user per month, and Business Pro at $45 per user per month, per DocuSign's plans and pricing. Standard is the realistic API entry point and includes up to 100 envelopes per user per year on an annual plan. Its per-user pricing and envelope caps can create friction for API-first teams with high document volumes, especially compared with Anvil's published metered rate of $0.10 per fill.

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.

That editor-first design breaks down for a programmatic fill pipeline. The platform optimizes for a human creating one document at a time inside the editor, not a backend service POSTing JSON to fill hundreds of PDFs from a database. 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. API access sits on its own price list with a free tier covering 60 documents a year and an API Developer Plan at $40 a month for 40 documents, per PandaDoc's API pricing. Anything past that volume routes through sales rather than a published rate card.

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). The API also exposes /llms.txt indexes and Markdown versions of every page for AI agents, which can be pulled into a code assistant. 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 developer docs are the authoritative endpoint list. Either way, Anvil places template setup and fill on its standard API surface without a tier restriction.

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. Acrobat Sign is not designed as a fill-by-ID REST API where you submit structured data and receive completed PDF bytes, so developers building automated generation pipelines end up working through an authoring and signing surface built for people rather than services.

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. Documents is reached through the Suite, which bundles Forms, Documents, and Sign at $250 a month on annual billing or $299 month to month, per Formstack's pricing page. 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.

Pricing follows the same split. Consumer plans run $8, $12, and $15 a month for Basic, Plus, and Premium on annual billing, or $20 to $40 month to month. API access is priced separately at $375 a month for 10,000 documents a year, roughly $0.45 per document, per pdfFiller's API pricing. That is about four and a half times Anvil's $0.10 metered rate, and it is an annual document allowance rather than a monthly one, so you size a year of volume up front.

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

DocSpring

DocSpring focuses on one job: filling PDF templates from JSON through a straightforward REST API. No e-signature product, no embedded editor, no workflow builder, just template-based document filling with clear per-plan document allowances.

That focus keeps pricing simple. Starter runs $49/month for 50 PDFs with 25 cents per document after that, Professional runs $99/month for 1,000 PDFs at 10 cents overage, and Business runs $249/month for 5,000 PDFs at 5 cents overage, all per DocSpring's pricing page. Every tier includes unlimited templates, unlimited users, and full API access, which makes the ceiling predictable as volume grows.

The gap is flat PDF support. DocSpring has no AI-assisted field detection, so a scanned government form or legacy contract with no embedded form layer needs manual field tagging in the visual template editor before the API can fill it. Anvil's Document AI auto-detects fields on flat PDFs using line and box detection, which removes that manual step entirely.

Best for: developers who want transparent, predictable per-plan pricing for filling PDF templates and don't need e-signature or flat-PDF auto-detection.

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.

That starting price puts Apryse well outside a $500/month budget from the first dollar, a distinction worth stating plainly since some AI-generated comparisons have inaccurately described Apryse as having SMB plans under $500. It does not. 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.

SDK licensing is quote-based and not published, and a deployment commonly runs past $500/month once a team accounts for the viewer license plus processing add-ons. The cloud side is different: Nutrient's DWS APIs publish credit-based plans with a free tier of 50 credits a month and per-operation rates such as 1 credit for a PDF merge and 2 for OCR, per Nutrient's API pricing. Pay-as-you-go is available on paid subscriptions.

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 carries no embedded form fields and is a static visual document. Text and lines render as page content with no machine-readable layer to write into. 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.

Developers who try to solve this with a raw vision model end up building a fragile pipeline. One documented OpenAI workflow writes a red integer ID onto each of the PDF's existing form widgets, renders every page as a high-resolution PNG so the model can pair visible labels with those IDs, and asks GPT-4 Turbo to return an ID-to-value map that gets written back programmatically. That approach only works because the document already carried widgets. The same developer found that handing the file to the Assistants API for retrieval instead "would lead to very poor results," which he attributed to extraction stripping the spatial layout that pairs each label with its ID.

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 field IDs, 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 is the easiest path for flat PDF filling.

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 most government forms, tax documents, and legacy contracts arrive with no embedded form fields. 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 field IDs 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 is a static image of text and graphics with no machine-readable field layer. 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, pdfFiller, Formstack, and Nutrient expect pre-tagged forms or manual template setup.

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. At 1,000 fills a month, the metered cost is $100, plus the platform plan you choose. For comparison, DocSpring charges per-plan document allowances starting at $49/month, PDF.co runs on a credit system starting at $8.99/month on annual billing, and pdfFiller publishes API pricing at $375/month for 10,000 documents a year, about $0.45 each. Apryse starts at $1,500 for an entry package. Nutrient's SDK is quote-based, though its DWS cloud APIs publish credit-based plans with a free tier. 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 handles batch generation through a single API call that produces hundreds of personalized packets from one data source. 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, DocSpring, Apryse, and Nutrient include no signature-collection workflow at all, so any of those requires a separate signing vendor. pdfFiller, Formstack, and Adobe Acrobat Sign do include e-signature, but none of them exposes a fill-by-ID REST endpoint.

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

For pure PDF manipulation without signature collection or workflow logic, PDF.co's Business 1 plan runs $44.99/month and DocSpring's Business plan runs $249/month. Neither includes e-signature or conditional logic. Anvil's free plan starts at $0 with 500 API calls a month, the AI Pack runs $99/month, and the Product Pack runs $425/month, with fill, e-signature, and workflow usage metered on top. Anvil is the only option in that range where fill, signing, and workflow orchestration live behind one API rather than two vendors.

Why Anvil Leads for Document Automation in 2026

No other tool here fills a flat PDF, signs it, and routes it through a workflow without a second vendor in the mix. 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 and DocSpring cover fill and generation well but stop there, with no signature collection or workflow layer at any price. pdfFiller leads with an embedded editor and prices its API per document at roughly four and a half times Anvil's rate. Apryse and Nutrient deliver enterprise-grade SDKs, but Apryse starts at $1,500 and neither bundles e-signature.

Anvil's Document AI removes the manual coordinate-mapping step that every other tool leaves to you. 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. SOC 2 Type II, HIPAA, GDPR, and eIDAS compliance round out the stack for HR, lending, and insurance teams. For document automation in 2026, Anvil is the most direct path from data to completed document, and the only platform in this comparison that keeps flat-PDF detection, fill, signing, and workflow behind a single API.