# India ATS Jobs: Zoho Recruit, Keka, Freshteam (Half Price) (`laudable_instrument/india-ats-jobs-zoho-recruit-keka`) Actor Open jobs from company career sites on Zoho Recruit, Keka and Freshteam, India's most-used SMB ATSs. Public listings only, robots.txt honoured. One normalised schema with experience, department, location and description. $2 per 1,000 jobs. - **URL**: https://apify.com/laudable_instrument/india-ats-jobs-zoho-recruit-keka.md - **Developed by:** [Unadhi](https://apify.com/laudable_instrument) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing Pay per usage This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## India ATS Jobs: Zoho Recruit, Keka and Freshteam career sites (half price) This actor pulls every open job from company career sites hosted on **Zoho Recruit** and **Keka**, the ATSs most Indian SMBs and startups use, plus **Freshteam** (legacy). It covers only public, login-free listings. Paste career-page URLs and you get one clean row per job in the same schema as our Greenhouse/Lever/Ashby actor. **Price: $2 per 1,000 jobs** ($1.75 on SILVER, $1.25 on GOLD+), with no $0.03 start fee. That is half of memo23/career-site-ats-jobs-api at every tier. You only pay for jobs delivered after your filters. Failed boards, duplicates and filtered-out jobs are free. ### Sources and why they're allowed We checked each platform on 29 Sep 2026 before building it. This is our reading, not legal advice. | Source | How we read it | robots.txt | Terms | Status | |---|---|---|---|---| | Zoho Recruit (`*.zohorecruit.in/.com/.eu/...`) | Server-rendered `/jobs/Careers` page; the jobs JSON is embedded in it | Allows `/jobs`, `/jobs/*`, `/careers` | Zoho terms: no anti-scraping clause | ✅ Supported | | Keka (`*.keka.com/careers`) | Keka's public jobs-embed endpoint under `/careers/api/…` (what Keka gives customers to embed jobs on their own sites) | `Disallow: /`, `Allow: /careers`. We only touch `/careers…` | Keka MSA: no anti-scraping clause | ✅ Supported | | Freshteam (`*.freshteam.com/jobs`) | Server-rendered list page. The description is the list excerpt; detail pages aren't fetched | Allows `/jobs` | Freshworks terms: no clause | ⚠️ Legacy: Freshworks is shutting Freshteam down (access ends about April 2027) | | Darwinbox | n/a | robots.txt redirects to a login page, and jobs load only through an undocumented app API | Terms page can't be read without JS | ❌ Not supported (failed the gate) | robots.txt is fetched and obeyed per host (RFC 9309, including Crawl-delay; at least 0.2 s between requests to a host). Every row carries a `sourceCompliance` object recording the robots and terms basis. ### Output Each row has `ats`, `board`, `jobId`, `title`, `company`, `locations`, `city`, `country`, `workplaceType`, `employmentType`, `department`, `industry` (Zoho), `experience` (Keka, e.g. "1-3"), `skills` (Keka), `publishedAt`, `jobUrl`/`applyUrl`, `requisitionId` (Keka job number), `salary*` (when stated), `description` (plain text), and `sourceCompliance`. There is also a `BOARDS_SUMMARY` record in the key-value store with a status per board. Known gaps: - Keka rarely states the employment type (it only gives a numeric code, kept as `atsJobTypeCode`), so `employmentType` is filled only when the title or description says it (16 of 180 jobs). - None of the tested boards published salaries. - Freshteam gives no posting date. ### Filters `keywords`, `excludeKeywords`, `searchDescription`, `locations`, `remoteOnly`, `departments`, `employmentTypes`, `postedWithinDays`, `maxJobsPerBoard`, `maxJobsTotal`. The run's max total charge is always respected: jobs beyond it aren't delivered and aren't charged. ### Measured (box, 29 Sep 2026) 14 inputs (5 Zoho, 5 Keka, 1 Freshteam, plus Darwinbox, Naukri and a nonexistent Keka tenant as negative tests): **11/11 real boards returned ok, 235 jobs** (Zoho 53, Keka 180, Freshteam 2). The 3 negative inputs were rejected cleanly and cost nothing. 29 requests, 6.6 s wall, 1.62 CPU-s, 118 MB peak. A random job URL from each board: 11/11 returned HTTP 200. Details are in `test/RESULTS.md`. # Actor input Schema ## `boards` (type: `array`): One per line. Zoho Recruit career URLs (https://.zohorecruit.in|com|eu/jobs/Careers), Keka career URLs (https://.keka.com/careers), Freshteam URLs (https://.freshteam.com/jobs), or specs such as 'zoho:sq1' (which means .zohorecruit.in), 'keka:hr' or 'freshteam:acme-123'. Darwinbox is not supported. ## `keywords` (type: `array`): Keep jobs whose title contains any of these words (whole-word, case-insensitive). Empty = all jobs. ## `searchDescription` (type: `boolean`): Match keywords in the job description too, not just the title. ## `excludeKeywords` (type: `array`): Drop jobs whose title contains any of these words (e.g. senior, intern). ## `locations` (type: `array`): Keep jobs whose location or country contains any of these (e.g. Bengaluru, India, Remote). ## `remoteOnly` (type: `boolean`): Keep only jobs marked remote by the ATS or with a remote location. ## `departments` (type: `array`): Keep jobs whose department or team contains any of these. ## `employmentTypes` (type: `array`): Keep only these types. Keka rarely states a type, so most Keka jobs have none and are dropped by this filter. ## `postedWithinDays` (type: `integer`): 0 = any date. ## `includeDescription` (type: `boolean`): Turn off for smaller, faster output. ## `maxJobsPerBoard` (type: `integer`): Newest first. 0 = no limit. ## `maxJobsTotal` (type: `integer`): Hard cap for the whole run. 0 = no limit. You are also protected by the run's max total charge. ## `maxConcurrency` (type: `integer`): Per-host politeness (robots.txt Crawl-delay) is always applied. ## `requestTimeoutSecs` (type: `integer`): Zoho career pages are about 1.7 MB and can take 5-10 s. ## Actor input object example ```json { "boards": [ "https://hr.keka.com/careers", "https://microsave.zohorecruit.in/jobs/Careers", "keka:infra360" ], "searchDescription": false, "remoteOnly": false, "postedWithinDays": 0, "includeDescription": true, "maxJobsPerBoard": 0, "maxJobsTotal": 0, "maxConcurrency": 8, "requestTimeoutSecs": 60 } ``` # Actor output Schema ## `results` (type: `string`): No description ## `summary` (type: `string`): No description ## `runStats` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "boards": [ "https://hr.keka.com/careers", "https://microsave.zohorecruit.in/jobs/Careers", "keka:infra360" ] }; // Run the Actor and wait for it to finish const run = await client.actor("laudable_instrument/india-ats-jobs-zoho-recruit-keka").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "boards": [ "https://hr.keka.com/careers", "https://microsave.zohorecruit.in/jobs/Careers", "keka:infra360", ] } # Run the Actor and wait for it to finish run = client.actor("laudable_instrument/india-ats-jobs-zoho-recruit-keka").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "boards": [ "https://hr.keka.com/careers", "https://microsave.zohorecruit.in/jobs/Careers", "keka:infra360" ] }' | apify call laudable_instrument/india-ats-jobs-zoho-recruit-keka --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,laudable_instrument/india-ats-jobs-zoho-recruit-keka" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/FdnHpM6DdMECfmZhX/builds/0tUQIuA1pW98jE0vP/openapi.json