Zoho CRM
Service ID: zoho-crm
Zoho makes it easy to get the complete picture of your sales cycle and stay on top of your business opportunities. Never lose another lead again.
At a Glance
- Difficulty
- ✅STRAIGHTFORWARDSelf-Service OAuth Client + Free Edition for Testing, No Review or Partnership
- Authentication
- OAuth 2.0Authorization 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
- Partnership Required
- No(No partner programme and no app review: you register a Server-based client yourself.)
- Partnership Application
- Zoho API console↗
- Apideck Credentials
- AvailableThe Zoho consent screen shows "Apideck"; use your own Zoho client in production.
- Costs
- None. Registering a Zoho API client is free and API calls draw on the consumer's own edition credits.
- Sandbox Availability
- Available — Access Sandbox↗(A Free edition org for your own testing, or a Developer Edition org by invitation from a sandbox-enabled customer.)
- 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)
- 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
What are Apideck credentials?
For select connectors, Apideck has established partnerships allowing you to integrate immediately without your own partnership. When using Apideck credentials, “Apideck” appears as the requesting application during OAuth. Learn more about partnership categories →
Responsibility matrix
| Task | You (Customer) | Your Consumer | Apideck |
|---|---|---|---|
| Register a Server-based client in the Zoho API console | ✓ (or use Apideck credentials) | — | Docs provided |
| Enable Multi-DC for the data centres your consumers use | ✓ | — | — |
| Add Client ID, Client Secret and scopes in the Apideck Dashboard | ✓ | — | — |
| Authorize the connection in Vault | — | ✓ (user with API Access permission) | — |
| Token refresh, credential storage and data-centre routing | — | — | ✓ |
| Maintain the connector and unified CRM and Lead APIs | — | — | ✓ |
Environments
- Testing and production
- One Zoho API client serves testing and production. Zoho separates environments at the organisation level: a production org, a Sandbox org (on its own sandbox API domain) and a Developer Edition org are each authorised separately, and a token issued for one organisation cannot call another. Apideck's temporary shared test credentials are an alternative for early evaluation (request access via https://help.apideck.com/en/articles/7774658). Take care when testing against a production org.
🚨Important to Know About Zoho CRM
- 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.
⚠️
10 gotchas across 7 resources
Connector-specific behaviors and limitations to be aware of
📦
7 supported resources
View field mappings, supported operations, and schema details