Zoho Recruit API v2: retrieve available modules and their metadata
domain: zoho.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Complete Zoho OAuth2 and obtain an access token with scope=ZohoRecruit.setup.operation.READ or .ALL.
GET https://recruit.zoho.com/recruit/v2/settings/modules with header Authorization: Zoho-oauthtoken {token} to list every module in the account.
GET https://recruit.zoho.com/recruit/v2/settings/modules/{module_api_name} to fetch metadata for a single module (e.g. Candidates).
Inspect the api_supported, creatable, editable, convertable, and generated_type attributes to determine what operations are actually available for that module before building integration logic against it.
Use each module's api_name (not its display label) when constructing subsequent Insert/Update/Search API calls.
Known gotchas
api_supported can be false for modules not yet exposed via API — check this flag rather than assuming every visible UI module is API-accessible.
Custom modules and fields have API names auto-generated by Zoho at creation time and cannot be renamed afterward, so hardcode the exact api_name you observe from this endpoint.
This endpoint only returns setup/schema-level module metadata — it does not return field-level metadata (field definitions require the separate Fields metadata API).
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?