Based on the document content: Title Zoho DataPrep REST API – Metering, Units & Rate Limits | API Pricing Guide

Zoho DataPrep REST API - Metering, Units & Limits

In order to ensure effective resource utilization and service quality, Zoho DataPrep API usage will be measured based on units consumed and frequency of API calls.

API Units

Each Zoho DataPrep API method is associated with a defined unit cost. The total units consumed by an application are calculated on a per-day basis, based on the type and frequency of API methods invoked. Each Zoho DataPrep pricing plan includes a daily unit allowance, and usage beyond this cap requires add-on purchases.

In addition to unit consumption, certain API types are subject to frequency (rate) limits that cap the number of requests allowed within a given time window, regardless of available units.

API Units per Plan

The table below summarizes the daily unit allocation for each Zoho DataPrep plan.

Plan

Daily Unit Allocation

Free

Standard / Trial

1,000 units/day

Enterprise / Trial

4,000 units/day


Add-on Unit Pricing

Additional API units can be purchased in bulk. The table below shows available add-on tiers and pricing in USD.

 

API Units (Add-on Volume)

Price (USD)

Price per 1,000 Units

1K

$18

$18.00

2K

$30

$15.00

5K

$60

$12.00

10K

$90

$9.00

25K

$150

$6.00

 

Notes
Note: Add-on units are available for Standard and Enterprise plans only. The Free plan does not support API access.

API Unit Consumption

The table below lists every available REST API method, its description, the unit cost per invocation, and the HTTP method used.

 

API Name

Description

Units

Method

PIPELINE OPERATIONS

Get Job Status

Returns the current status of a pipeline job.

5 units

GET

Get All Jobs in a Pipeline

Lists all jobs run for a given pipeline.

5 units

GET

Get Pipeline Info

Fetches details of all stages, datasets, and configuration within a pipeline.

5 units

GET

Get All Pipelines

Lists all pipelines across workspaces in the organization.

5 units

GET

Create Pipeline

Creates a new pipeline inside a workspace.

2 units

POST

Clone Pipeline

Creates a copy of an existing pipeline with a new name.

50 units

POST

Clone Workspace

Creates a copy of an existing workspace and all its pipelines. Consumes 50 x N units, where N = number of pipelines.

50 x N units

POST

Schedule Pipeline

Schedules a pipeline to run automatically at a configured time and frequency.

2 units

POST

Webhook Triggered Run

Triggers a pipeline run immediately via a webhook call.

50 units

POST

Rename Pipeline

Renames an existing pipeline.

1 unit

PUT

Trash Pipeline

Moves a pipeline to trash. Can be restored later.

1 unit

POST

Permanent Delete Pipeline

Permanently deletes a trashed pipeline. Cannot be recovered.

1 unit

DELETE

WORKSPACE OPERATIONS

Get All Workspaces

Lists all workspaces in the organization.

5 units

GET

Get Organization ID

Fetches the portal name and organization ID.

1 unit

GET

Create Workspace

Creates a new workspace in the organization.

2 units

POST

Rename Workspace

Renames an existing workspace.

1 unit

PUT

Trash Workspace

Moves a workspace to trash. Can be restored later.

1 unit

POST

Permanent Delete Workspace

Permanently deletes a trashed workspace. Cannot be recovered.

1 unit

DELETE

STAGE OPERATIONS

Create Stage

Creates a dataset stage in a pipeline from an imported data source.

2 units

POST

Derive Stage

Creates a new derived dataset stage from an existing stage in the pipeline.

2 units

POST

Get Stage Output Details

Retrieves output file details of a dataset stage after a pipeline run.

5 units

GET

Load Sample

Fetches column names and preview data for a dataset stage using its sample ID.

2 units

GET

Mark as Ready

Marks a dataset stage as ready for pipeline execution.

2 units

PUT

Rename Stage

Renames a dataset stage in a pipeline.

1 unit

PUT

Delete Stage

Removes a dataset stage from a pipeline.

1 unit

DELETE

DATA SOURCE OPERATIONS

Get Connection ID

Fetches the connection ID of an existing source (e.g. S3, FTP) for use in import.

1 unit

GET

Initiate Import

Starts the import process from a connected source using a connection ID.

1 unit

POST

Create Data Source

Creates a pipeline data source using the import output. Returns a dataset ID.

2 units

POST

Change Data Source

Replaces the existing datasource of a pipeline with a newly imported one.

2 units

POST

Add Cloud Destination

Connects a dataset stage to a cloud destination (S3 or FTP) for export.

5 units

POST

File Export

Configures a dataset stage to export its output as a file.

5 units

POST

Remove Destination

Removes a configured destination from a pipeline.

2 units

PUT

TRANSFORM OPERATIONS

Join

Joins two dataset stages in a pipeline.

10 units

POST

Append

Appends one dataset stage to another in a pipeline.

10 units

POST

Pivot

Applies a pivot transformation to a dataset stage.

10 units

POST

Unpivot

Applies an unpivot transformation to a dataset stage.

10 units

POST

Other Transforms

Applies any other transform rule to a dataset stage (e.g. filter, rename, formula).

3 units

POST

RULESET OPERATIONS

Get Ruleset History

Retrieves the list of transform rules applied on a dataset stage.

2 units

GET

Get Ruleset Template IDs

Lists all saved ruleset templates available in the organization.

3 units

GET

Save Ruleset Template

Saves the current ruleset of a dataset stage as a reusable template.

2 units

POST

Apply Saved Ruleset Template

Applies a saved ruleset template to a dataset stage.

5 units

POST

Import Ruleset Template File

Uploads a ruleset template file (.zdrt) for use in a pipeline.

5 units

POST

Apply Ruleset Template File

Applies an uploaded ruleset template file to a dataset stage.

10 units

POST

Export Ruleset as .zdrt File

Exports the ruleset of a dataset stage as a .zdrt template file.

2 units

POST

 

Alert
* Clone Workspace: Units = 50 × N, where N is the number of pipelines in the workspace.
* Rate limits apply by HTTP method: GET requests are capped at 60 per minute; POST requests are capped at 3 per hour. These limits apply independently of daily unit quotas.

API Frequency Limits

API frequency limits define the maximum number of requests that can be made within a specific time window. These limits apply independently of unit balances - exceeding a frequency limit will result in request throttling even if daily unit quota remains available.
GET requests are limited to 60 per minute. POST requests are limited to 3 per hour.

SEE ALSO