1 creditPDF to PDF/A API — verified archival conversion
PDF/A-2b or 3b, verified structurally (and by veraPDF when available) — never a false conformance claim.
PDF to PDF/A converts a document to PDF/A-2b or PDF/A-3b using Ghostscript with an embedded sRGB ICC profile, then verifies the result before ever claiming conformance: the XMP metadata must declare pdfaid:part/pdfaid:conformance, and the document must carry a real /GTS_PDFA1 OutputIntent with an embedded color profile. Any verification miss returns a 500 rather than a PDF that merely claims to be PDF/A. `validated_by` reports whether the check was structural or done by veraPDF, when installed.
How does the PDF to PDF/A 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-pdfa' \ -H 'X-API-Key: ash_live_...' \ -F 'file=@document.pdf' -F 'level=2b'
Common use cases
- →Long-term archival of contracts and records
- →Meeting a court or regulator's PDF/A requirement
- →Preparing documents for a digital archive system
Frequently asked questions
How much does the PDF to PDF/A 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.