1 creditRepair PDF API
Recovers a damaged PDF through an escalating repair cascade — reports which tier actually fixed it.
Repair first tries to open and re-save the PDF (recovering common damage like a broken or missing cross-reference table); a file too damaged for that falls back to a second, more tolerant rewrite pass. The response's `repaired_via` reports which tier actually fixed it — `no_repair_needed`, or the tier used — and any file neither tier can open returns a 422 rather than a false claim of success.
How does the Repair PDF 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-repair' \ -H 'X-API-Key: ash_live_...' \ -F 'file=@damaged.pdf'
Common use cases
- →Recovering a PDF with a broken cross-reference table
- →Salvaging a file that other tools refuse to open
- →Cleaning up a PDF before running further processing on it
Frequently asked questions
How much does the Repair PDF 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.