Zoho CRM's API documentation, and the API domain itself, varies depending on which data centre your account is hosted in, since Zoho CRM operates multiple regional data centres to meet local data protection requirements.
Each data centre exclusively holds the data of accounts registered there, and every API call needs to be made against the correct domain for your account. Copying an API endpoint from documentation written for a different region and using it as-is simply won't work, since it's pointed at the wrong data centre entirely.
| Region | Accounts domain | API domain |
|---|---|---|
| United States | accounts.zoho.com | www.zohoapis.com |
| European Union | accounts.zoho.eu | www.zohoapis.eu |
| India | accounts.zoho.in | www.zohoapis.in |
| Australia | accounts.zoho.com.au | www.zohoapis.com.au |
| China | accounts.zoho.com.cn | www.zohoapis.com.cn |
| Japan | accounts.zoho.jp | www.zohoapis.jp |
| Canada | accounts.zohocloud.ca | www.zohoapis.ca |
| Saudi Arabia | accounts.zoho.sa | www.zohoapis.sa |
Check the URL you use to log in to Zoho CRM day to day. Its domain suffix tells you which data centre your account lives on, for example crm.zoho.eu means you're on the EU data centre, and you should use the EU accounts and API domains above for every request.
If your application needs to serve users registered in more than one data centre, you'll need to enable Multi-DC support in the Zoho API Console. Without it, your application can only access accounts in the single data centre it was originally registered against, and authorisation requests should always be initiated from the accounts.zoho.com domain regardless of which data centre the user's account is actually on.