Zoho CRM (via Apideck)

Access Zoho CRM through Apideck's CRM unified API — one of 21 CRM connectors that share the same method surface. Code you write here ports to Odoo, Salesforce, HubSpot and 17 other CRM connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Zoho CRM plumbing.

Quick facts

Apideck serviceId: zoho-crm
Unified API: CRM
Auth type: oauth2
Gotchas: page
Zoho CRM docs: https://www.zoho.com/crm/developer/docs/api/
Homepage: https://www.zoho.com/crm/

At a glance

Implementation difficulty: straightforward — Self-Service OAuth Client + Free Edition for Testing, No Review or Partnership
Vendor partnership required: no (Zoho API console) — No partner programme and no app review: you register a Server-based client yourself.
Apideck-managed credentials: available — The Zoho consent screen shows "Apideck"; use your own Zoho client in production.
Account type required: Any Zoho CRM edition, including Free
Consumer access level: Any user whose profile has the Zoho CRM API Access permission (Administrators have it by default)
Sandbox: available (signup) — A Free edition org for your own testing, or a Developer Edition org by invitation from a sandbox-enabled customer.
Costs: None. Registering a Zoho API client is free and API calls draw on the consumer's own edition credits.
Rate limits: Daily credits per org by edition: 5,000 (Free) to 50,000 plus 250 to 2,000 per user (paid); 5 to 25 concurrent calls; HTTP 429 on excess
Authentication: Authorization Code flow via Zoho Accounts.
Webhooks: No webhooks — Zoho CRM changes are not surfaced as Apideck events; sync by polling the CRM and Lead APIs

Important to know:

Zoho runs nine data centres (US, EU, India, Australia, Japan, China, Canada, Saudi Arabia, UK). Your client needs Multi-DC enabled for every data centre your consumers' accounts live in, or their authorisation fails; the connector detects each consumer's data centre itself.
Zoho keeps at most 20 refresh tokens per user per client and 15 live access tokens per refresh token: a 21st authorisation by the same user silently invalidates the oldest connection. Refresh tokens otherwise never expire unless revoked.
Your consumers' other Zoho apps draw on the same daily credit pool as your integration, so a busy organisation can throttle your sync well before its edition's headline limit.
Zoho's Sandbox feature is included only from the Enterprise edition up, so a consumer on a lower edition has no test copy of their org.

Facts synced from Apideck's connector metadata API — GET /connector/connectors/zoho-crm (overview field) is the live, authoritative version.

When to use this skill

Activate this skill when the user explicitly wants to work with Zoho CRM — for example, "pull contacts in Zoho CRM" or "sync leads in Zoho CRM". This skill teaches the agent:

Which Apideck unified API covers Zoho CRM (CRM)
The correct serviceId to pass on every call (zoho-crm)
Zoho CRM-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-rest

For the raw OpenAPI spec:

CRM: https://specs.apideck.com/crm.yml · API Explorer

Minimal example (TypeScript)

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List contacts in Zoho CRM
const { data } = await apideck.crm.contacts.list({
  serviceId: "zoho-crm",
});

Portable across 21 CRM connectors

The Apideck CRM unified API exposes the same methods for every connector in its catalog. Switching from Zoho CRM to another CRM connector is a one-string change — no rewrite, no new SDK.

// Today — Zoho CRM
await apideck.crm.contacts.list({ serviceId: "zoho-crm" });

// Tomorrow — same code, different connector
await apideck.crm.contacts.list({ serviceId: "odoo" });
await apideck.crm.contacts.list({ serviceId: "salesforce" });

This is the compounding advantage of using Apideck over integrating Zoho CRM directly: code against the unified CRM API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.