Naukri Jobs Scraper & Company Hiring Monitor

Find companies advertising relevant roles on Naukri, export the jobs, and identify IDs you have not seen before. Built for recruitment research and recurring hiring watchlists.

Quick start: enter a role and optional city, leave the first test at one page, and run. Open the Jobs dataset for vacancies, COMPANIES for the hiring report, and SUMMARY for coverage. No Naukri login or API key is required.

What you get

Recruitment agencies and recruitment software builders need a repeatable way to discover companies advertising relevant vacancies. This Actor combines job search results with a company hiring report and baseline comparison.

• Search roles and locations, or supply filtered public Naukri search URLs.
• Export unique job IDs, source links, company, location, experience, disclosed salary, skills and description snippets.
• Rank companies by newly observed jobs within the collected sample.
• Pass the previous run's IDs to identify new arrivals without overlapping runs sharing mutable state.
• Inspect each completed page and a coverage report. An all-failed run fails.

Example input

{"queries":["python developer"],"location":"bengaluru","freshnessDays":7,"maxPagesPerSearch":5,"previousJobIds":[],"onlyNew":false}

Use searchUrls to preserve filters from Naukri. These override the generated keyword/location/freshness search. Ten searches and ten pages per search are the hard limits. Source pages normally contain 20 listings; this is not guaranteed.

Outputs

• Jobs dataset: unique jobs, or only newly observed IDs when onlyNew is enabled. Download JSON, CSV or Excel through Apify.
• COMPANIES: observed job counts, counts absent from the baseline, top skills, locations and supporting job IDs.
• SUMMARY: successful pages, source result counts, stop reasons, failed searches and budget status.
• PAGE-0001, PAGE-0002, ...: completed search snapshots, including valid empty results.
• SEEN-JOB-IDS: up to 10,000 IDs for the next run. Save this in your workflow and pass it as previousJobIds.

An empty baseline marks every collected ID new to this comparison; it does not mean the jobs were just posted. Use identical searches and limits when comparing runs. A truncated sample cannot prove a vacancy closed or company hiring increased. Reports count the collected sample, not a company's entire workforce or vacancies. IDs beyond the rolling 10,000-ID baseline may reappear as new.

Hidden salaries remain null. Descriptions are search-result snippets, not guaranteed full job descriptions. The Actor does not collect applicant profiles or CVs, use account cookies, or submit job applications.

Pricing

$0.04 per completed search page before plan discounts. A page normally contains up to 20 jobs. Job exports, company reports, compute and proxy usage during the Actor run are included.

Completed pages	Typical maximum jobs in one search	Event charges before discounts at 1 GB
1	20	$0.04005
3	60	$0.12005
5	100	$0.20005

The completed-page event includes a confirmed empty search or a page containing only previously observed jobs: the purchased result is the completed monitoring check. onlyNew changes which jobs appear in the dataset; it does not make the check free. Blocked or malformed pages do not incur this event. Overlapping searches are checked separately and charged per completed page, while their exported jobs are deduplicated.

Actor start (apify-actor-start) is $0.00005, charged once per GB of selected memory, minimum one event. Page prices are $0.038 for Bronze, $0.036 for Silver and $0.034 for Gold/Platinum/Diamond. Set a maximum run cost to cap event charges; allow room for the start event. Downloads and storage after the run can incur ordinary Apify usage outside the Actor price.

Reliability boundary

Availability depends on Naukri's public pages. This implementation does not solve CAPTCHAs or require account cookies. Partial failure preserves completed output and records missing coverage. Inspect SUMMARY before treating an export as complete. If a source blocks a run, avoid immediately scheduling repeated retries.

The source can refresh or repost listings, reorder results and omit salary details. Use sourceCreatedAt and sourceAgeLabel as source-provided signals, not independently verified posting dates. No result proves that a company needs a recruitment supplier or will respond to outreach.

API and automation

Start a run through POST /v2/acts/sauliusautomatesit~naukri-hiring-monitor/runs with your input and maxTotalChargeUsd query parameter. Read the returned run ID until it completes, then download its default dataset and COMPANIES/SUMMARY/SEEN-JOB-IDS records.

For recurring research, retain SEEN-JOB-IDS and pass it as the next run's previousJobIds. Keep the same search and page limits. Set onlyNew to true if you only need additions in the Jobs dataset. The initial run establishes your baseline.

Use the Actor's API and MCP tabs for integration settings. Leave a review based on your experience, or open an issue with the run ID and input if the output is wrong; do not post API tokens.

Download the recruiter workflow

Download the Python recruitment watchlist starter. It includes a tested input, CSV export, company reports, an explicit spending cap and a saved job-ID baseline for repeat runs. Python 3.10 or newer; no extra packages.