The Big Shift: From Browser Editing to Developer Automation

Zoho PDF Editor started as a web-based tool: open a PDF, make changes, and download the result. That approach works when a person is handling documents one by one, but it becomes a bottleneck when teams need to process PDFs at scale—contracts, onboarding packets, invoices, or long reports that must be split and routed automatically.

Over time, Zoho expanded from “editor features” into a broader API-driven model. Instead of relying on a user interface, developers can now run page-level PDF operations through REST endpoints as part of automated workflows. This transition has reshaped how businesses handle repetitive document tasks: extraction becomes a backend step triggered by an app event (upload, approval, form submission), not a manual action done after downloading a file.

Where things were “before”

Previously, extracting pages was primarily a user-facing action. Someone opened a PDF, selected pages to pull out, and saved the result. That worked for occasional tasks, but it didn’t scale well. Any workflow that required consistency—like always extracting signature pages or always isolating a specific section of a report—depended on people doing it correctly every time.

What’s different “today”

Now the same page extraction action can be executed programmatically. The Extract Pages endpoint is designed to pull selected pages from a PDF without opening an editor interface. The output can be a new PDF or image formats, which makes it useful for everything from document routing to generating previews in web apps.

What the Extract Pages API Does Today

The Extract Pages endpoint allows you to extract specific pages from a PDF and return them as either:

  • a new PDF (merged or separated by page), or
  • images (JPEG or PNG), depending on the output format you choose.

This is particularly helpful when you want only a portion of a document to move forward in a process—for example, a single signed page, a summary section, or a set of pages needed for a review step.

Common use cases

Teams typically use this endpoint for:

  • Signature-page extraction: isolate signature pages from longer agreements
  • Report segmentation: split a long report into smaller PDFs for distribution
  • Preview creation: extract pages as images to generate thumbnails or review previews
  • Workflow routing: pass only specific pages to downstream systems (storage, analysis, approval)

Requirements You Need Before You Call the Endpoint

A successful integration usually comes down to getting three things right: selecting the correct API domain, using a token with the right scope, and staying within file constraints.

Choose the correct data center domain

Zoho hosts accounts across multiple regions (such as US, EU, IN, and others). The API domain you use depends on where your account is hosted. In practice, your request URL uses a placeholder like {zohoapis_domain}, which you replace with the correct regional domain for your environment.

If the domain doesn’t match your account’s data center, you can run into authentication or request-routing issues—so treat this as a core configuration item, especially for multi-tenant or multi-region applications.

LOOKING FOR A ONE-STOP SOLUTION TO YOUR GROWTH NEEDS?

Use the correct OAuth scope

Your access token must include:

  • ZohoWriter.pdfEditor.ALL

Without that scope, the API will not authorize extraction requests.

Respect input file constraints

The input PDF is subject to size constraints (commonly referenced as a 50 MB maximum in documentation notes and implementation guidance). In production systems, it’s best to validate file size before upload so jobs don’t fail after you’ve already sent the request.

The Endpoint You’ll Call

To extract pages, you send a POST request to:

https://{zohoapis_domain}/pdfeditor/api/v1/pdf/pages/extract

This endpoint is part of the base API path:

.../pdfeditor/api/v1

How Requests Are Structured

The API uses multipart form data. Conceptually, you send:

  1. the input PDF
  2. a JSON object describing which pages to extract
  3. a JSON object describing how to package and name the output

File input (required)

You provide the PDF in one of two ways:

  • Upload the file directly as multipart form data, or
  • provide a publicly accessible URL string (depending on your chosen request approach)

input_options (required JSON)

This JSON controls:

  • page_ranges: which pages you want to extract
  • format: the output format, such as pdf, jpeg, or png

Page range patterns you can use

Typical page selection patterns include:

  • 1,2,5 for specific pages
  • 2-4,7-9 for combined ranges
  • -5 for “from the first page through page 5”
  • 7- for “from page 7 through the last page”

output_settings (JSON)

This JSON typically includes:

  • name: output file name
  • single_pdf (optional):
    • true to merge extracted pages into a single PDF
    • false to output separate PDFs per extracted page

If single_pdf is omitted, the default behavior is generally a single merged PDF output.

A Clean, Working cURL Example

Below is a corrected template you can reuse. Replace the domain, token, file path, and ranges as needed:

curl --location --request POST "https://www.zohoapis.com/pdfeditor/api/v1/pdf/pages/extract" \
  --header "Authorization: Zoho-oauthtoken YOUR_ACCESS_TOKEN" \
  --form 'files=@"/path/to/Sample.pdf"' \
  --form 'input_options={"page_ranges":"2-4,7-","format":"pdf"}' \
  --form 'output_settings={"name":"Extracted.pdf","single_pdf":true}'

The Job-Based Flow: Submit, Poll, Download

A major operational detail is that extraction runs as a scheduled process rather than returning the final output immediately.

What you receive first

After submitting the request, the system returns a response indicating the job is in progress, along with a status check URL. That URL is used to monitor progress.

How you retrieve the output

Once processing completes successfully, you receive (or can retrieve via the status check flow) a download URL containing the job identifier. Your application can then download the extracted result and store it wherever your workflow requires.

How the Integration Changed From “Before” to “Today”

The most significant change is that extraction no longer needs a manual editor session. What once required a person to open a document, select pages, and save a new file can now be executed automatically through an API call.

This is not just a convenience upgrade—it alters how businesses design document workflows:

  • Before: extraction depended on manual steps and human accuracy
  • Today: extraction can be embedded into systems, triggered automatically, and tracked as a job

That shift improves consistency, speeds up processing, and enables higher-volume document workflows without increasing staffing.

Final Takeaway

If your workflow still treats PDF extraction as a manual step, you’re leaving a major automation opportunity on the table. With the Extract Pages endpoint, you can define page rules once (like “always extract the signature page”) and let your application execute the process reliably at scale.

If you want, I can also produce a second version tailored for a non-technical audience (less code, more real-world examples), while keeping the structure and formatting professional.

© Image credits to Steve Johnson

LOOKING FOR A ONE-STOP SOLUTION TO YOUR GROWTH NEEDS?

Posted in CRM