PDFs<\/a> are still the default format for contracts, invoices, reports, onboarding packs, and compliance documents\u2014but the way teams assemble<\/em> those PDFs has changed fast. Not long ago, \u201ccombining PDFs\u201d usually meant a manual step: download files, open a desktop editor<\/a>, drag pages around, export again, and hope nothing breaks.<\/p>\n\n\n\n Zoho PDF Editor<\/a>\u2019s Insert Pages from PDF<\/strong> API was built to remove that manual step. Instead of editing by hand, you can programmatically insert an entire PDF (like Terms & Conditions, a cover sheet, or an appendix) into an existing PDF at a specific page location\u2014either before<\/strong> or after<\/strong> the page number you choose. (Zoho<\/a>)<\/p>\n\n\n\n What makes this especially relevant today is that Zoho\u2019s PDF Editor has evolved from being \u201can online editor\u201d into a broader PDF manipulation API suite<\/strong>\u2014with options not only to return the updated PDF for download, but also to store outputs for longer-term workflows. (Zoho<\/a>)<\/p>\n\n\n\n When Zoho PDF Editor was introduced, the emphasis was primarily on editing and organizing PDFs online. Zoho\u2019s own \u201cWhat\u2019s New\u201d timeline highlights the product\u2019s introduction in September 2024<\/strong>. (Zoho<\/a>)<\/p>\n\n\n\n In practice, early PDF workflows typically looked like this:<\/p>\n\n\n\n By May 2025<\/strong>, Zoho explicitly introduced PDF editing and manipulation REST APIs<\/strong>\u2014including the ability to insert, extract, replace, and split pages, and to insert watermarks or images. (Zoho<\/a>)<\/p>\n\n\n\n Along with that shift came a clearer, more scalable developer model:<\/p>\n\n\n\n And most importantly for teams building document pipelines: Zoho now offers \u201creturn now\u201d and \u201cstore\u201d options for several operations, including inserting pages. (Zoho<\/a>)<\/p>\n\n\n\n At its core, the API takes:<\/p>\n\n\n\n Zoho describes the purpose simply: it inserts an entire PDF into another existing PDF based on a specified page number. (Zoho<\/a>)<\/p>\n\n\n\n This is especially useful when you have repeatable document components, such as:<\/p>\n\n\n\n Zoho documents the primary endpoint format as: (Zoho<\/a>)<\/p>\n\n\n\n Zoho requires that you use the domain-specific API endpoint<\/strong> for your region. Their \u201cGetting Started\u201d page lists multiple regions (US, EU, IN, CN, AU, JP, CA, SA). (Zoho<\/a>)<\/p>\n\n\n\n For example, the US domain is:<\/p>\n\n\n\n Zoho also calls out a base API endpoint pattern:<\/p>\n\n\n\n (Zoho<\/a>)<\/p>\n\n\n\n In real integrations, this matters because mismatching region domains is one of the most common reasons authentication \u201clooks right\u201d but requests still fail.<\/p>\n\n\n\n To use the Insert Pages from PDF endpoint, Zoho states you must generate an OAuth token with the scope:<\/p>\n\n\n\n And send it in the request header using the format shown in their sample request:<\/p>\n\n\n\n (Zoho<\/a>)<\/p>\n\n\n\n A notable evolution is the \u201cstore\u201d variation of the endpoint. Zoho documents a separate API called Insert Pages and Store<\/strong>, which saves the resulting PDF into Zoho WorkDrive. That endpoint requires:<\/p>\n\n\n\n Zoho lists these scopes for the store version:<\/p>\n\n\n\n This is a meaningful change from earlier \u201cdownload-only\u201d patterns, because it enables workflows where the output must live in a managed file system for sharing, auditing, or reuse.<\/p>\n\n\n\n Zoho\u2019s Insert Pages endpoints use a multipart\/form-data<\/strong> request. (Zoho<\/a>)<\/p>\n\n\n\n This is the PDF you are modifying. Zoho allows:<\/p>\n\n\n\n Zoho also sets a maximum size for the input PDF:<\/p>\n\n\n\n This is the PDF that will be inserted. Like Maximum size for the source file:<\/p>\n\n\n\n Zoho\u2019s documented JSON shape looks like:<\/p>\n\n\n\n (Zoho<\/a>)<\/p>\n\n\n\n At minimum, Zoho supports naming the resulting PDF:<\/p>\n\n\n\n (Zoho<\/a>)<\/p>\n\n\n\n For many teams, consistent output naming becomes a hidden success factor\u2014because downstream systems (storage, e-signature, CRM attachments) often depend on predictable filenames.<\/p>\n\n\n\n Zoho provides a sample request in the documentation. Below is a cleaned-up version that matches their required structure and keeps quoting consistent. (Zoho<\/a>)<\/p>\n\n\n\n If you\u2019re inserting via URL instead of file upload, Zoho allows you to pass the URL string using the same parameters ( Zoho runs the insert operation as a scheduled job. That means your first response will not be a finished PDF. Instead, you receive a URL that you can poll to check job status. Zoho explains that once processing begins you\u2019ll initially receive a \u201cstatus URL,\u201d and by invoking it you can monitor the scheduled job. (Zoho<\/a>)<\/p>\n\n\n\n Zoho\u2019s sample response includes:<\/p>\n\n\n\n When successful, the Insert Pages endpoint returns:<\/p>\n\n\n\n This model is ideal for:<\/p>\n\n\n\n One of the biggest practical updates since early guidance is the availability of Insert Pages and Store<\/strong>. This endpoint uses:<\/p>\n\n\n\n (Zoho<\/a>)<\/p>\n\n\n\n Instead of returning a Zoho\u2019s This turns \u201cinsert pages\u201d from a simple transformation into a true document pipeline step\u2014especially if your business needs:<\/p>\n\n\n\n Zoho now positions PDF Editor APIs as a suite that supports a wide range of operations. Their PDF API overview lists capabilities such as inserting images, combining pages, extracting\/splitting\/replacing pages, rotating\/deleting pages, applying watermarks, adding page numbers, and protecting PDFs\u2014often with both \u201cinstant return\u201d and \u201cstore\u201d options. (Zoho<\/a>)<\/p>\n\n\n\n This matters because most real-world workflows aren\u2019t one-step:<\/p>\n\n\n\n Once you treat Insert Pages as one component in a broader toolkit, it becomes easier to design stable, repeatable document automation.<\/p>\n\n\n\n Zoho\u2019s API will do what you ask\u2014so your system should ensure the page number makes sense for the original PDF. The easiest safeguard is to track the page count in your own workflow and prevent invalid insertion points before calling the endpoint.<\/p>\n\n\n\n Zoho\u2019s documentation clearly states:<\/p>\n\n\n\n If you routinely exceed this, you have a few options:<\/p>\n\n\n\n Because the process is job-based, treat Zoho explicitly expects you to invoke the status URL to monitor progress. (Zoho<\/a>)<\/p>\n\n\n\n A simple rule of thumb:<\/p>\n\n\n\n In many orgs, the \u201cstore\u201d variant becomes the default once you move from single-user operations to multi-team automation.<\/p>\n\n\n\n Insert standard Terms after the first page of an invoice, so each customer receives the right legal language without anyone manually assembling PDFs.<\/p>\n\n\n\n Combine offer letters with policy PDFs (benefits, handbook excerpts, confidentiality rules) at predictable insertion points.<\/p>\n\n\n\n Automatically attach exhibits, schedules, and disclosures to contracts\u2014then store the result in WorkDrive for controlled sharing and audit trails.<\/p>\n\n\n\n Insert branded cover pages or appendix sections (methodology, definitions, sources) into exported PDFs so stakeholders always get a consistent deliverable.<\/p>\n\n\n\n Earlier guidance around this API focused mainly on one capability: insert a PDF into another PDF and download the result<\/strong>. That workflow still exists and remains straightforward. (Zoho<\/a>)<\/p>\n\n\n\n Today\u2019s reality is broader:<\/p>\n\n\n\n If you\u2019re building document workflows in 2026, the best approach is to treat Insert Pages as a building block: start with the basic \u00a9 Image credits to Steve Johnson<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"How Things Changed From Earlier Versions to Today<\/h2>\n\n\n\n
Before: Editing-first, Automation-second<\/h3>\n\n\n\n
\n
Today: A Dedicated REST API Suite for Page Operations<\/h3>\n\n\n\n
\n
What the Insert Pages from PDF API Does<\/h2>\n\n\n\n
\n
\n
page_number<\/code> (where the insertion is anchored)<\/li>\n\n\n\nposition<\/code> (before<\/code> or after<\/code>) (Zoho<\/a>)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n\n
Endpoints and Regional Domains<\/h2>\n\n\n\n
The Insert Pages request URL<\/h3>\n\n\n\n
https://{zohoapis_domain}\/pdfeditor\/api\/v1\/pdf\/pages\/insert\n<\/code><\/pre>\n\n\n\nPicking the correct regional domain<\/h3>\n\n\n\n
https://www.zohoapis.com\n<\/code><\/pre>\n\n\n\nhttps://www.zohoapis.com\/pdfeditor\/api\/v1\n<\/code><\/pre>\n\n\n\nAuthentication Requirements<\/h2>\n\n\n\n
OAuth scope for Insert Pages<\/h3>\n\n\n\n
\n
ZohoWriter.pdfEditor.ALL<\/code> (Zoho<\/a>)<\/li>\n<\/ul>\n\n\n\nAuthorization: Zoho-oauthtoken <token>\n<\/code><\/pre>\n\n\n\nWhat\u2019s new today: extra scopes for storing results<\/h3>\n\n\n\n
\n
\n
ZohoWriter.pdfEditor.ALL<\/code><\/li>\n\n\n\nWorkDrive.organization.ALL<\/code><\/li>\n\n\n\nWorkDrive.files.ALL<\/code> (Zoho<\/a>)<\/li>\n<\/ul>\n\n\n\nRequest Format and Parameters<\/h2>\n\n\n\n
Required files<\/h3>\n\n\n\n
original_file<\/code> (File or String)<\/h4>\n\n\n\n\n
\n
source_file<\/code> (File or String)<\/h4>\n\n\n\noriginal_file<\/code>, it can be:<\/p>\n\n\n\n\n
\n
Insertion controls<\/h3>\n\n\n\n
input_options<\/code> (JSON)<\/h4>\n\n\n\n{\n \"page_number\": 3,\n \"position\": \"before\/after\"\n}\n<\/code><\/pre>\n\n\n\n\n
page_number<\/code>: the page where the insertion is anchored (Zoho<\/a>)<\/li>\n\n\n\nposition<\/code>: where to insert relative to that page (before<\/code> or after<\/code>) (Zoho<\/a>)<\/li>\n<\/ul>\n\n\n\nOutput naming<\/h3>\n\n\n\n
output_settings<\/code> (JSON)<\/h4>\n\n\n\n{ \"name\": \"<new document name>\" }\n<\/code><\/pre>\n\n\n\nA Clean, Correct cURL Example<\/h2>\n\n\n\n
curl --location --request POST \"https:\/\/www.zohoapis.com\/pdfeditor\/api\/v1\/pdf\/pages\/insert\" \\\n --header \"Authorization: Zoho-oauthtoken YOUR_TOKEN_HERE\" \\\n --form 'original_file=@\"\/path\/to\/Existing.pdf\"' \\\n --form 'source_file=@\"\/path\/to\/Source.pdf\"' \\\n --form 'input_options={\"page_number\":3,\"position\":\"after\"}' \\\n --form 'output_settings={\"name\":\"Combined.pdf\"}'\n<\/code><\/pre>\n\n\n\noriginal_file<\/code> and source_file<\/code>). (Zoho<\/a>)<\/p>\n\n\n\nUnderstanding the Job-Based Response Model<\/h2>\n\n\n\n
Why the API responds asynchronously<\/h3>\n\n\n\n
Initial response<\/h3>\n\n\n\n
\n
status_check_url<\/code><\/li>\n\n\n\nstatus<\/code> (such as inprogress<\/code>) (Zoho<\/a>)<\/li>\n<\/ul>\n\n\n\nSuccess response (download version)<\/h3>\n\n\n\n
\n
download_url<\/code><\/li>\n\n\n\nstatus: success<\/code> (Zoho<\/a>)<\/li>\n<\/ul>\n\n\n\n\n
What\u2019s New Today: \u201cInsert Pages and Store\u201d for WorkDrive-Based Pipelines<\/h2>\n\n\n\n
https://{zohoapis_domain}\/pdfeditor\/api\/v1\/pdf\/pages\/insert\/store\n<\/code><\/pre>\n\n\n\nHow the store version differs<\/h3>\n\n\n\n
download_url<\/code>, the store version returns WorkDrive identifiers like:<\/p>\n\n\n\n\n
document_url<\/code><\/li>\n\n\n\ndocument_id<\/code>
\u2026and still follows the same job-based pattern with status_check_url<\/code>. (Zoho<\/a>)<\/li>\n<\/ul>\n\n\n\nAdditional output settings<\/h3>\n\n\n\n
output_settings<\/code> for the store version adds:<\/p>\n\n\n\n\n
folder_id<\/code><\/li>\n\n\n\noverwrite_existing_file<\/code> (optional) (Zoho<\/a>)<\/li>\n<\/ul>\n\n\n\n\n
How Insert Pages Fits Into the Bigger PDF API Ecosystem<\/h2>\n\n\n\n
\n
Best Practices That Prevent Pain Later<\/h2>\n\n\n\n
Validate
page_number<\/code> before you call the API<\/h3>\n\n\n\nKeep file sizes under the limits<\/h3>\n\n\n\n
\n
\n
Poll smart, not aggressive<\/h3>\n\n\n\n
status_check_url<\/code> like you would any queue:<\/p>\n\n\n\n\n
Choose \u201cdownload\u201d vs \u201cstore\u201d based on your real workflow<\/h3>\n\n\n\n
\n
Real-World Use Cases That Benefit Most<\/h2>\n\n\n\n
Sales and invoicing packets<\/h3>\n\n\n\n
HR and onboarding<\/h3>\n\n\n\n
Legal and compliance bundles<\/h3>\n\n\n\n
Reporting and analytics exports<\/h3>\n\n\n\n
Final Takeaway: What the Update Really Means<\/h2>\n\n\n\n
\n
\/insert<\/code> endpoint, then expand to \/insert\/store<\/code> when you need reliable storage, sharing, and long-lived document references.<\/p>\n\n\n\n