Organize PDF Pages API
Reorder, rotate, duplicate and remove PDF pages in one secure asynchronous task.
Endpoint and task semantics#
Operation code: organize
Start this operation with POST /v1/tasks and the tool code shown above. Upload and attach source PDFs (or use task-scoped upload endpoints), then call POST /v1/tasks/{task_id}/process with operation settings.
Assemble or rearrange a document without scanning or re-uploading every page.
Inputs: One verified PDF, maximum 500 pages and up to 500 output pages; plan limits may be lower.
Configuration and extra parameters#
| Setting | Type | Behaviour |
|---|---|---|
| pagesrequired | {source:number,rotation:0|90|180|270}[] | Output sequence, 1-based source page numbers. Repeated source duplicates; absent source deletes. Rotation is clockwise and relative to original rotation. |
Options are validated by the API. Unknown settings and unsupported values return an error instead of being ignored.
Working request sequence#
Programming language: cURL
Choose a language · scroll horizontally for all 10 SDK languages
# Server-side API calls. Save the returned task_id.
curl -fsS -X POST 'https://api.pdfhq.io/v1/tasks' \
-H 'x-api-key: YOUR_API_KEY' -H 'Content-Type: application/json' \
-d '{"tool":"organize"}'
# Upload and verify 1 PDF(s), then obtain and approve a credit quote:
curl -fsS 'https://api.pdfhq.io/v1/tasks/TASK_ID/quote' -H 'x-api-key: YOUR_API_KEY'
# ONLY after explicit customer approval:
test "$PDFHQ_APPROVE_QUOTE" = yes || { echo "Approval required" >&2; exit 1; }
curl -fsS -X POST 'https://api.pdfhq.io/v1/tasks/TASK_ID/process' \
-H 'x-api-key: YOUR_API_KEY' -H 'Content-Type: application/json' \
-d '{"options":{"pages":[{"source":3,"rotation":90},{"source":1,"rotation":0}]}}'
curl -fsS 'https://api.pdfhq.io/v1/tasks/TASK_ID' -H 'x-api-key: YOUR_API_KEY'After starting a task, upload and verify PDFs, review the credit quote, and get explicit approval before processing. API keys belong on your server, never on signed storage uploads.
Generated downloadable packages cover the task workflow only. Full-service SDKs require a verified runtime OpenAPI specification; the Python, JavaScript and TypeScript task SDKs stream file uploads; the other languages require signed multipart uploads implemented by the caller.
The returned task ID is used for both status polling and retrieval. After the task succeeds, request a signed output URL rather than embedding a download secret.
Output and important details#
New PDF in requested page order; original retained according to retention policy.
Rewriting breaks cryptographic PDF signatures. Signed PDFs are rejected. AcroForm documents and signed PDFs are rejected. Internal links and bookmarks may not survive page restructuring; review before distributing.
Errors, retries and billing