2 creditsPDF to DOCX API — editable text and tables
Editable text and tables; layout is best-effort.
PDF to DOCX converts a PDF's real text and tables into an editable Word document — not an image of the page. It needs an actual text layer to work from: a scanned or image-only PDF returns a 422 (no_text_layer) telling you to run OCR first, rather than silently producing an empty or image-embedded document. Complex layouts (multi-column, heavy graphic design) convert best-effort — text and tables come through editable, but pixel-perfect layout fidelity isn't the goal.
How does the PDF to DOCX 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-to-docx' \ -H 'X-API-Key: ash_live_...' \ -F 'file=@document.pdf'
Common use cases
- →Turning a received PDF contract into an editable draft
- →Extracting a report's tables into Word for further editing
- →Converting scanned-then-OCR'd PDFs into editable documents
Frequently asked questions
How much does the PDF to DOCX API tool cost?+
2 credits 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.