Naukri Jobs Scraper
Pricing
from $0.70 / 1,000 item processeds
Go to Apify Store
Naukri Jobs Scraper
Scrape public Naukri job listings by keyword, location, and start URLs.
Naukri Jobs Scraper
Pricing
from $0.70 / 1,000 item processeds
Scrape public Naukri job listings by keyword, location, and start URLs.
Scrape verified Naukri India public listings. NaukriGulf coverage is deferred until a representative non-empty route is verified.
Enter one or more job titles, skills, or roles as a list. The form prefills software engineer; API calls without keywords do not inherit this prefill.
Location for generated Naukri India searches, for example Bangalore or Mumbai. The form/schema default is Bangalore. A location without keywords searches for jobs generally. For a URL-only run, clear location and keywords explicitly.
Public Naukri keyword/location path search URLs or job URLs. Processed before and in addition to generated searches; arbitrary browser query filters are not preserved. For URL-only input, set keywords to [] and location to an empty string. NaukriGulf URLs are not processed.
Maximum saved jobs across all inputs, default 20 and maximum 5000. Fewer may be available. The maxJobs API alias takes precedence when supplied. This is not a request or time limit.
Save public job descriptions when they are available in search/detail page data.
Legacy advanced field. Added to generated search URLs, but not enforced by the current search extraction. Do not rely on it to filter results by experience.
Legacy advanced field. Added to generated search URLs, but not enforced by the current search extraction. Do not rely on it to filter results by experience.
API alias for maxItems. When provided, maxJobs takes precedence over maxItems, including the form/schema default.
Legacy checkpoint field; does not currently remove unchanged or older jobs because emitted rows are classified as new. Compare datasets by jobId or jobUrl outside the Actor; this is not incremental monitoring.
Proxy settings used from the first request; there is no automatic direct-first fallback or connection selector. The existing form/schema default uses Apify RESIDENTIAL in IN. Explicit proxyConfiguration is passed to the Apify SDK unchanged: custom proxy URLs, managed settings and useApifyProxy:false remain supported. An omitted configuration uses the existing SDK/environment behavior, not a new fallback. Use valid SDK settings, including a boolean useApifyProxy and valid proxy URLs. No Actor-level fallback replaces invalid custom URLs. Proxy availability can affect results.
{ "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ], "apifyProxyCountry": "IN"}