Documentation Index
Fetch the complete documentation index at: https://nango.dev/docs/llms.txt
Use this file to discover all available pages before exploring further.
🚀 Quickstart
🧑💻 OAuth app setup
🔗 Useful links
🚨 API gotchas
Authorize Zoho People
Go to Connections -> Add Test Connection -> Authorize, then log in to Zoho People. Later, you’ll let your users do the same directly from your app. Call the Zoho People API
Let’s make your first request to the Zoho People API (retrieves basic organizational information). Replace the placeholders below with your secret key, integration ID, and connection ID:curl "https://api.nango.dev/proxy/api/v3/organization" \
-H "Authorization: Bearer <NANGO-SECRET-KEY>" \
-H "Provider-Config-Key: <INTEGRATION-ID>" \
-H "Connection-Id: <CONNECTION-ID>"
Install Nango’s backend SDK with npm i @nangohq/node. Then run:import { Nango } from '@nangohq/node';
const nango = new Nango({ secretKey: '<NANGO-SECRET-KEY>' });
const res = await nango.get({
endpoint: '/api/v3/organization',
providerConfigKey: '<INTEGRATION-ID>',
connectionId: '<CONNECTION-ID>'
});
console.log(res.data);
Or fetch credentials dynamically via the Node SDK or API. ✅ You’re connected! Check the Logs tab in Nango to inspect requests.Next step: Embed the auth flow in your app to let your users connect their Zoho People accounts. Access the Zoho API Console
Create a new client
- In the API Console, click on the + ADD CLIENT button and select Server-based Applications as your client type.
- Fill in all the required information. For Authorized Redirect URIs enter
https://api.nango.dev/oauth/callback
- Click Create to register your client. You will then receive a Client ID and Client Secret, which are required to configure your integration in Nango.
Configure Multi-DC
- On the Settings tab, check the option to use the same OAuth credentials for all data centers, this enables you to handle users from different regions
Common Scopes
| Scope | Description |
|---|
ZohoPeople.employee.ALL | Full access to all employee-related operations. |
ZohoPeople.forms.ALL | Full access to all forms (read, create, update, delete). |
ZohoPeople.forms.READ | Read-only access to People forms. |
ZohoPeople.leave.ALL | Full access to all leave-related operations (read, create, update). |
ZohoPeople.leave.READ | Read-only access to leave data. |
ZohoPeople.attendance.ALL | Full access to attendance-related operations. |
ZohoPeople.timetracker.ALL | Full access to timetracker-related operations. |
ZohoPeople.organization.READ | Read-only access to organization details. |
-
Zoho uses datacenter-specific URLs for authentication. Make sure to use the correct datacenter domain extension (
com, eu, in, com.cn, com.au) based on where your user’s account is registered.
-
For production applications, consider implementing multi-datacenter support to handle users from different regions.
-
For specific scopes, refer to the API documentation pages to find the exact scopes needed per API and per method.
-
Zoho People requires a partnership to deploy to production.