1 creditFill PDF Form API
Fill PDF forms by field name. Unknown fields are reported, never silently dropped.
Fill PDF Form sets each field you name to the value you give it, by field name — any name in your request that doesn't match a real field on the form comes back in `unmatched` instead of being silently ignored, and `strict: true` turns an unmatched field into a 422 instead. Checkboxes accept true, false, "Yes" or "Off". Set `flatten: true` to make the filled values permanent (non-editable) in the same call.
How does the Fill PDF Form API work?
One HTTP request from any language. Every ASHDOCS endpoint uses the same X-API-Key header.
curl -X POST 'https://api.ashdocs.com/api/v2/tools/pdf-form-fill' \
-H 'X-API-Key: ash_live_...' \
-F 'file=@form.pdf' -F 'fields={"full_name":"Ada Lovelace","agree":true}'Common use cases
- →Auto-filling a contract from CRM data
- →Generating a filled application PDF per applicant
- →Batch-filling the same template for many recipients
Frequently asked questions
How much does the Fill PDF Form API tool cost?+
1 credit per successful call. Sandbox keys (prefix ash_test_) run the tool end-to-end without ever consuming credits — use them in CI or for tuning.
What is the endpoint URL for this tool?+
The endpoint is documented in the curl example on this page. All ASHDOCS endpoints share the base URL https://www.ashdocs.com and require an X-API-Key header.
Can I run this tool inside Make, Zapier, or n8n?+
Yes — through each platform's built-in HTTP mechanism (Make's HTTP module, Webhooks by Zapier, n8n's HTTP Request node). Nothing to install: point it at this exact endpoint with your X-API-Key header. See /integrations/make, /integrations/zapier or /integrations/n8n for step-by-step setup.
Does this tool support batch or scheduled runs?+
Yes. POST /api/v1/batch runs any tool over up to 50 files with a single credit ledger entry, and pipeline schedules let you trigger the same tool on a cron. Both are documented in /docs.