Zoho CRM API transport and object-surface contracts.
Scope
Primary execution surface: server.
Developer Source Map
RudderStack Cross-Check
RudderStack is used here only as secondary engineering evidence for discovery and cross-check.
| Destination | Type | Link |
|---|
zoho | Discovery lead | source |
Verified Contracts
Transport / Payload Rules
| Object / Event | Field | Applies To | Type | Requirement | Exact Format | Normalization | Hashing | Examples | Caveat | Primary Source | Status | Confidence |
|---|
request | endpoint | server | object | Required | Endpoint and authentication/request transport contract are documented on the referenced developer page. | Not clearly specified | Not clearly specified | - | Verified against vendor-owned developer documentation for this contract category. | www.zoho.com | Verified | High |
Candidate / Needs Review Items
Event Contracts
| Object / Event | Field | Applies To | Type | Requirement | Exact Format | Normalization | Hashing | Examples | Caveat | Primary Source | Status | Confidence |
|---|
event | event_contract | server | object | Conditional | Current evidence is CRM CRUD-oriented and not a clean analytics event-ingest contract. | Not clearly specified | Not clearly specified | - | Blocker: surface_mismatch — Connector maps CRM CRUD/query operations; no explicit event-ingest surface is documented for this contract category. | www.zoho.com | Needs manual review | Low |
User Data Contracts
| Object / Event | Field | Applies To | Type | Requirement | Exact Format | Normalization | Hashing | Examples | Caveat | Primary Source | Status | Confidence |
|---|
user | user_data_contract | server | object | Conditional | Current evidence is CRM CRUD-oriented and not a clean analytics event-ingest contract. | Not clearly specified | Not clearly specified | - | Blocker: surface_mismatch — Current docs describe CRM object fields; mapping to analytics-style user-data contract requires explicit surface split and row pinning. | www.zoho.com | Needs manual review | Medium |
Normalization Rules
| Object / Event | Field | Applies To | Type | Requirement | Exact Format | Normalization | Hashing | Examples | Caveat | Primary Source | Status | Confidence |
|---|
normalization | hashing_contract | server | string | Optional | No explicit field-level hashing contract is documented for the scoped rows. | Not clearly specified | Not clearly specified | - | Blocker: hashing_contract_missing — No explicit client-side hashing contract for scoped CRM fields. | www.zoho.com | Needs manual review | Medium |
normalization | normalization_contract | server | string | Optional | Current evidence is CRM CRUD-oriented and not a clean analytics event-ingest contract. | Not clearly specified | Not clearly specified | - | Blocker: surface_mismatch — Normalization behavior is implementation-derived from CRM CRUD payload handling, not an explicit analytics/event contract. | www.zoho.com | Needs manual review | Medium |
Excluded Items
No excluded rows in this revision.
Last Reviewed
2026-03-31