Loading
Loading
Split a PDF into multiple parts based on specified page numbers or ranges.
The PDF Split API divides a PDF document into smaller files at specified page boundaries. You can split by individual pages, ranges, or keywords such as even, odd, or all pages.
Pass your API key as the apiKey parameter in every request.
This is version v1.0 of the API.
The PDF Split API accepts a file upload, query parameters, and webhook headers described below.
The request body is a single optional file upload sent as multipart/form-data. All other parameters (including file_id and pages) are passed as query parameters, not in the request body.
{
"file": "/path/to/document.pdf"
}fileoptionalmultipart/form-dataThe PDF file to process.
All parameters must be included as query parameters. Any parameters sent in the form data will be ignored.
formatoptionalStringdefault: jsonResponse format: 'json' (default) or 'xml'.
file_idoptionalStringThe unique ID of a file already present on our server. Use this instead of uploading the file again.
outputoptionalStringdefault: split_outputName of the output PDF (without extension).
destroyoptionalBooleandefault: falseIf true, we delete the input file immediately after generating the output.
pagesoptionalArray<String>default: allDefines the page numbers or ranges at which to split the PDF. You can provide individual page numbers and/or page ranges in any order (e.g., 1-4,9-5,16-last). Use commas ( , ) to separate entries and hyphens ( - ) for ranges. Special keywords: even - splits at every even-numbered page, odd - splits at every odd-numbered page, all - splits the PDF into single pages, last - represents the last page (e.g., 5-last, 10 or 1,last-2). Examples: "1,4-2,last" / "odd" / "all" / "1,odd" (invalid). Note: Only "last" is allowed to be used with pages/ranges. Other keywords are passed on their own. Multiple pages param can be passed at once to get multiple output files.
webhook_urloptionalStringThe URL where we'll send the webhook notification after the task completes. Authentication parameters in the URL (e.g., ?auth=token123) are passed as-is.
webhook_failure_notificationoptionalBooleandefault: falseIf true, we'll send an email notification if the webhook request fails after 3 retries. The email goes to the requesting user or their org admin if user is part of an organization.
Optional custom headers for webhook authorization
X-Webhook-AuthorizationoptionalStringCustom authorization header sent with the webhook request. Format: Key:Value (e.g., Authorization:Bearer token123).
A successful request returns a 200 OK response with a JSON object containing the task ID and input file IDs.
taskIdUnique identifier for the PDF task, used to check status.
inputIdsArray of file IDs referencing input files used for the task. Not returned when destroy=true.
See the HTTP Status Codes documentation for a complete reference of common API errors and HTTP status codes.
Please provide a valid PDF file. Other file types are not supported.
Please provide either a file or a file ID.
Invalid parameter value provided for 'param_name'.
Please provide a valid file ID.
These errors might appear in the task-status response if the background job fails.
The provided file is not a valid PDF file.
An unknown error occurred while saving the file. Try again later.
An unknown error occurred while generating the PDF. Try again later.
Internal Server Error Occurred.
The provided PDF file is encrypted. Please decrypt it first to perform operations.
The provided page number format is invalid. Refer to the documentation for valid page number formats.
An error occurred while creating the ZIP file. Please try again later.