FreeReorder PDF Pages API
Rearrange pages by an explicit order list — duplicate a page by naming it twice.
Reorder rebuilds the PDF's pages in exactly the order you list, 1-based. By default the order must include every source page exactly once (`validated: true`) — set `validated: false` to allow a partial reorder, and `allow_duplicates: true` to let the same page number appear more than once, which duplicates that page in the output.
How does the Reorder PDF Pages 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-reorder' \
-H 'X-API-Key: ash_live_...' \
-F 'file=@document.pdf' -F 'options={"order":[3,1,2]}'Common use cases
- →Fixing a scanned document's page order
- →Moving a signature page to the end
- →Duplicating a cover page across a batch
Frequently asked questions
How much does the Reorder PDF Pages 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.