Skip to content

Zoho: Pipeline schemas

11 Zoho schemas with complete fields and constraints.

← Pipeline operations · All schemas

Pipeline — pipeline create Pipeline — request body — body

FieldTypePresenceDescription and constraints
$objectRootRequest body for creating a pipeline configuration with a custom pipeline label and mapped stage values for a specific Deals layout.
Additional keys: not allowed
pipelinearrayRequired within parentArray of pipeline picklist configurations to create or update.
Maximum items: 1
Minimum items: 1
pipeline[]objectEach itemPicklist value configuration for pipeline customization, including stage mappings.
Additional keys: not allowed
pipeline[].defaultbooleanOptionalIndicates if this picklist value should be set as the default option.
pipeline[].display_valuestringRequired within parentUser-facing display name for the picklist value.
Format: string
pipeline[].mapsarrayRequired within parentArray of stage mappings defining which stages this picklist value connects to and their sequence.
Maximum items: 200
Minimum items: 1
pipeline[].maps[]objectEach itemMapping configuration for associating a picklist value with a specific pipeline stage.
Additional keys: not allowed
pipeline[].maps[].display_valuestringOptionalUser-facing display name for the pipeline stage.
Format: string
pipeline[].maps[].idstringRequired within parentUnique identifier of the target pipeline stage to map.
Format: int64
pipeline[].maps[].sequence_numberintegerOptionalOptional position of this stage mapping in the pipeline sequence (overrides default positioning).
Format: int32

Pipeline — pipeline create Pipeline — response body

FieldTypePresenceDescription and constraints
$objectRootBatch success response for pipeline creation/update operations, maintaining 1:1 correspondence with request items.
Additional keys: not allowed
pipelinearrayRequired within parentArray of individual success responses matching the request pipeline items.
Maximum items: 1
Minimum items: 1
pipeline[]objectEach itemIndividual success response for a pipeline operation, mirroring the request structure.
Additional keys: not allowed
pipeline[].codestringRequired within parentRepresents the success code indicating the type of successful operation.
Known values: SUCCESS
pipeline[].detailsobjectRequired within parentOperation-specific success details including resource identifiers.
Additional keys: not allowed
pipeline[].details.idstringRequired within parentUnique identifier of the newly created pipeline configuration.
Format: int64
pipeline[].messagestringRequired within parentRepresents the confirmation of the successful operation.
Format: string
pipeline[].statusstringRequired within parentOverall status indicator.
Known values: success

Pipeline — pipeline update Pipeline By Id — request body — body

FieldTypePresenceDescription and constraints
$objectRootRequest body for updating or creating pipeline configurations with custom picklist values and stage mappings.
Additional keys: not allowed
pipelinearrayRequired within parentArray of pipeline picklist configurations to create or update.
Maximum items: 1
Minimum items: 1
pipeline[]objectEach itemPicklist value configuration for pipeline customization, including stage mappings.
Additional keys: not allowed
pipeline[]._deleteobjectOptionalDeletion metadata object.
Additional keys: not allowed
pipeline[]._delete.permanentnullRequired within parentIndicates if the deletion was permanent (true), soft delete (false), or status unknown/null.
pipeline[].defaultbooleanOptionalIndicates if this picklist value should be set as the default option.
pipeline[].display_valuestringOptionalUser-facing display name for the picklist value.
Format: string
pipeline[].mapsarrayOptionalArray of stage mappings defining which stages this picklist value connects to and their sequence.
Maximum items: 200
Minimum items: 1
pipeline[].maps[]ModelEach itemExpand Pipeline — pipeline update Pipelines — request body — body pipeline item maps item

Referenced models: Pipeline — pipeline update Pipelines — request body — body pipeline item maps item

Pipeline — pipeline update Pipelines — request body — body

FieldTypePresenceDescription and constraints
$objectRootRequest body for updating or creating pipeline configurations with custom picklist values and stage mappings.
Additional keys: not allowed
pipelinearrayRequired within parentArray of pipeline picklist configurations to create or update.
Maximum items: 1
Minimum items: 1
pipeline[]objectEach itemPicklist value configuration for pipeline customization, including stage mappings.
Additional keys: not allowed
pipeline[]._deleteobjectOptionalDeletion metadata object.
Additional keys: not allowed
pipeline[]._delete.permanentnullRequired within parentIndicates if the deletion was permanent (true), soft delete (false), or status unknown/null.
pipeline[].defaultbooleanOptionalIndicates if this picklist value should be set as the default option.
pipeline[].display_valuestringOptionalUser-facing display name for the picklist value.
Format: string
pipeline[].idstringRequired within parentID of the pipeline
Format: int64
pipeline[].mapsarrayOptionalArray of stage mappings defining which stages this picklist value connects to and their sequence.
Maximum items: 200
Minimum items: 1
pipeline[].maps[]ModelEach itemExpand Pipeline — pipeline update Pipelines — request body — body pipeline item maps item

Referenced models: Pipeline — pipeline update Pipelines — request body — body pipeline item maps item

Pipeline — pipeline update Pipelines — request body — body pipeline item maps item

FieldTypePresenceDescription and constraints
$objectRootMapping configuration for associating a picklist value with a specific pipeline stage.
Additional keys: not allowed
_deleteobjectOptionalDeletion metadata object.
Additional keys: not allowed
_delete.permanentnullRequired within parentIndicates if the deletion was permanent (true), soft delete (false), or status unknown/null.
display_valuestringOptionalUser-facing display name for the pipeline stage.
Format: string
idstringRequired within parentUnique identifier of the target pipeline stage to map.
Format: int64
sequence_numberintegerOptionalOptional position of this stage mapping in the pipeline sequence (overrides default positioning).
Format: int32

Pipelines — response body — pipeline

FieldTypePresenceDescription and constraints
$objectRootRoot response object containing all pipeline configurations configured for a given Deals layout in Zoho CRM.
Additional keys: not allowed
pipelinearrayRequired within parentArray of pipeline configuration items.
Maximum items: 90
Minimum items: 1
pipeline[]ModelEach itemExpand Pipelines — response body — pipeline pipeline item

Referenced models: Pipelines — response body — pipeline pipeline item

Pipelines — response body — pipeline pipeline item

FieldTypePresenceDescription and constraints
$objectRootPicklist option representing a pipeline configuration with associated stage mappings.
Additional keys: not allowed
actual_valuestringRequired within parentInternal API value for the picklist option.
Format: string
defaultbooleanOptionalIndicates if this is the default picklist value.
display_valuestringRequired within parentDisplay name of the picklist value as shown to users.
Format: string
idstringRequired within parentUnique identifier for this picklist value.
Format: int64
mapsarrayRequired within parentArray of stage mappings for this picklist value.
Maximum items: 200
Minimum items: 1
maps[]ModelEach itemExpand Pipelines — response body — pipeline pipeline item maps item

Referenced models: Pipelines — response body — pipeline pipeline item maps item

Pipelines — response body — pipeline pipeline item maps item

FieldTypePresenceDescription and constraints
$objectRootMapping between a picklist value and a specific pipeline stage, including its position and forecasting details.
Additional keys: not allowed
actual_valuestringRequired within parentInternal system value/API name for the stage.
Format: string
colour_codestringOptionalHexadecimal color code associated with the stage for UI representation.
Format: string
display_valuestringRequired within parentUser-facing display name of the pipeline stage.
Format: string
forecast_categoryobjectRequired within parentRepresents a forecast category used in sales pipeline stages for revenue forecasting and reporting.
Additional keys: not allowed
forecast_category.idstringRequired within parentUnique system identifier for the forecast category.
Format: int64
forecast_category.namestringRequired within parentRepresents the name of the forecast category (e.g., 'Pipeline', 'Closed', 'Omitted').
Format: string
forecast_typestringRequired within parentForecast type indicating stage status (e.g., 'Open', 'Closed Won', 'Closed Lost').
Format: string
idstringRequired within parentUnique identifier for this stage mapping.
Format: int64
sequence_numberJSONRequired within parent
sequence_number (anyOf 1)integerAlternativePosition of this stage in the pipeline sequence (1-based indexing).
Format: int32
sequence_number (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$

Specific Pipeline — response body — pipeline

FieldTypePresenceDescription and constraints
$objectRootRoot response object containing an array of pipeline configurations from Zoho CRM.
Additional keys: not allowed
pipelinearrayRequired within parentArray of pipeline configuration items.
Maximum items: 1
Minimum items: 1
pipeline[]ModelEach itemExpand Pipelines — response body — pipeline pipeline item

Referenced models: Pipelines — response body — pipeline pipeline item

Transfer Pipeline — request body — body

FieldTypePresenceDescription and constraints
$objectRootResponse confirming pipeline transfer operation with source-to-target mappings for pipeline and stages.
Additional keys: not allowed
transfer_pipelinearrayRequired within parentArray of pipeline transfer mappings showing source and target configurations.
Maximum items: 1
Minimum items: 1
transfer_pipeline[]objectEach itemIndividual pipeline transfer mapping.
Additional keys: not allowed
transfer_pipeline[].pipelineobjectRequired within parentPipeline-level transfer mapping from source to target pipeline.
Additional keys: not allowed
transfer_pipeline[].pipeline.fromstringRequired within parentSource pipeline ID.
Format: int64
transfer_pipeline[].pipeline.tostringRequired within parentTarget pipeline ID.
Format: int64
transfer_pipeline[].stagesarrayRequired within parentArray of stage mappings showing which stages transferred to which target stages.
Maximum items: 200
Minimum items: 1
transfer_pipeline[].stages[]objectEach itemIndividual stage transfer mapping.
Additional keys: not allowed
transfer_pipeline[].stages[].fromstringRequired within parentSource stage ID.
Format: int64
transfer_pipeline[].stages[].tostringRequired within parentTarget stage ID.
Format: int64

Transfer Pipeline — response body

FieldTypePresenceDescription and constraints
$objectRootSuccess response for pipeline transfer scheduling operation with job tracking information.
Additional keys: not allowed
transfer_pipelinearrayRequired within parentArray of pipeline transfer scheduling results maintaining 1:1 correspondence with request.
Maximum items: 1
Minimum items: 1
transfer_pipeline[]objectEach itemIndividual pipeline transfer scheduling result.
Additional keys: not allowed
transfer_pipeline[].codestringRequired within parentRepresents the success code indicating the type of successful operation.
Known values: SUCCESS
transfer_pipeline[].detailsobjectRequired within parentSuccess details including the scheduled job identifier.
Additional keys: not allowed
transfer_pipeline[].details.job_idstringRequired within parentUnique identifier of the scheduled pipeline transfer job for tracking.
Format: int64
transfer_pipeline[].messagestringRequired within parentRepresents the confirmation of the pipeline transfer scheduling.
Format: string
transfer_pipeline[].statusstringRequired within parentOverall status indicator.
Known values: success

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.