Naukri Jobs Scraper
Pricing
from $4.99 / 1,000 results
Naukri Jobs Scraper
Scrape job listings from Naukri.com based on keywords, location, and experience with anti-bot detection. Supports deep search for comprehensive job details including company reviews, salaries, and benefits.
Pricing
from $4.99 / 1,000 results
Rating
0.0
(0)
Developer
Coding Frontned
Maintained by CommunityActor stats
0
Bookmarked
30
Total users
1
Monthly active users
7 days ago
Last modified
Categories
Share
Scrapes public job-search result cards from Naukri.com in a real Chromium browser. Each normal dataset item includes job and company identifiers, profile links, logo, company rating and review count, experience range, salary when published, locations, description snippet, skills, posting age, job type, source context, and extraction metadata.
The Actor uses a bounded, ordinary Chromium render with an optional user-agent override and client-rendering wait. It deduplicates jobs by ID and removes null, blank, and empty values before storage. It does not bypass access controls or human-verification pages. If the runtime has no usable browser, it stores one compact BROWSER_UNAVAILABLE diagnostic instead of inventing job data.
Input
keyword— job title, company, or skill. Defaults tosoftware developer.location— optional city, state, or region.maxItems— number of jobs to save (1–500).maxPages— maximum search pages to visit.pageLoadWaitMs— wait for client-rendered results.renderTimeoutSecs— per-render timeout, 30–180 seconds.requestDelayMs— optional delay between pages, 0–10,000 milliseconds.maxRenderRetries— additional attempts for an empty or failed render, 0–3.maxHtmlBytes— maximum captured HTML size.browserExecutablePath— optional Chromium-compatible executable path.fixturePath— optional path underfixtures,.actor/fixtures,test/fixtures, orqa-inputsfor deterministic QA.includeDiagnostics— store compact diagnostics when extraction is blocked or unavailable.userAgent— optional explicit user-agent override.
Normal records retain the legacy fields. Diagnostic records use exactly { url, error, errorCode, scrapedAt } and are emitted for browser/runtime boundaries such as BROWSER_UNAVAILABLE, ACCESS_BOUNDARY, NO_RESULTS, and RENDER_ERROR.
Run locally
npm installapify run --purge
Results are written to storage/datasets/default; the run summary is stored as OUTPUT_SUMMARY.
For a deterministic local contract check:
apify run --purge --input-file qa-inputs/fixture-input.jsonnpm run validate