FreePDF Info API — inspect a PDF without opening it
Page count, sizes, fonts embedded or not, forms, tagging, PDF/A claim, linearization — one call.
PDF Info reports page count, each page's size in mm, PDF version, encryption, AcroForm/XFA presence, tagging (`/MarkInfo`), any PDF/A conformance claim found in the XMP metadata, embedded file count, every font used with whether it's actually embedded (not just referenced), image count, producer, creation date, file size and whether the file is linearized — free, and never modifies the file.
How does the PDF Info 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-info' \ -H 'X-API-Key: ash_live_...' \ -F 'file=@document.pdf'
Common use cases
- →Validating an upload before running a paid tool on it
- →Checking whether a PDF is already tagged/accessible
- →Auditing a batch of PDFs for embedded fonts before archiving
Frequently asked questions
How much does the PDF Info API tool cost?+
Nothing — this is a local page operation with no rendering engine, OCR or AI behind it, so it runs free on every plan. Sandbox keys (prefix ash_test_) also never consume credits.
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.