Naukri Job Scraper (India) - Skills, Salary & Full Description
Pricing
$0.20 / 1,000 job adverts
Go to Apify Store
Naukri Job Scraper (India) - Skills, Salary & Full Description
Pricing
$0.20 / 1,000 job adverts
One Naukri search keyword per line, for example "python developer", "data analyst" or "sales manager". Every keyword is searched separately in the location below and its results are labelled with it. A job that matches several of your keywords is returned once and charged once.
A city as Naukri names it in its own search box: "Bengaluru", "Mumbai", "Delhi / NCR", "Pune", "Hyderabad", "Chennai". Leave it empty to search all of India. A spelling Naukri cannot match returns zero jobs rather than an error, and the keyword's status row shows what was searched.
Optional. Naukri's own experience filter, as a whole number of years from 0 to 30: a job is kept when the number falls inside the advert's experience range. Leave it empty to accept every experience level.
Upper bound on the rows one keyword may produce. Naukri serves 20 jobs per search page, so this rounds up to whole pages. 1000 is the deepest this Actor pages one search; a keyword that reaches it says resultDepthLimitReached, with jobsAvailable showing how many Naukri claimed. Narrow the keyword, the city or the experience to reach past it.
Also write each job's full advert body: description (the HTML Naukri serves) and descriptionText (the same text with the tags removed). Naukri sends the body with the search results, so this costs no extra request and no extra time - it only makes the rows bigger. Every row carries a short snippet either way.
Hard ceiling on the requests this run sends to Naukri: the browser warm-up that passes its bot check, every search page and every retry. At the ceiling collection stops - the keywords not reached are written with partialReason "upstream_request_cap" and the run then ends normally. Leave empty and the Actor works a ceiling out from your keywords and limits, so a run is never unbounded.
Where the requests to Naukri come from. Naukri is behind Akamai Bot Manager and refuses datacenter IPs, so the default is Apify Proxy residential with an Indian exit, which is what this Actor is measured on. Changing it to datacenter will make the run fail its bot check.
{ "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ], "apifyProxyCountry": "IN"}