Naukri Jobs Scraper avatar

Naukri Jobs Scraper

Pricing

from $0.85 / 1,000 results

Go to Apify Store
Naukri Jobs Scraper

Naukri Jobs Scraper

Search Naukri.com by keyword and city, filter by experience, remote or hybrid work and posting age, and export each job with salary, skills, company rating and dates.

Pricing

from $0.85 / 1,000 results

Rating

0.0

(0)

Developer

The Netaji

The Netaji

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

16 days ago

Last modified

Features

Limited permissions

Share

The Actor searches Naukri.com, India's largest job board, by keyword and location and saves each matching job as one dataset row with its title, company, AmbitionBox rating, experience range, salary, skills, locations and posting time. Results arrive in Naukri's relevance order by default, and the experience, work mode and posting-age filters narrow a search the same way they do on Naukri itself.

{
"query": "python developer",
"location": "Bangalore",
"experienceYears": 3,
"workMode": "hybrid",
"postedWithinDays": "7",
"sort": "relevance",
"maxItems": 100
}

Accepted input

  • query is required: a job title, skill or keyword such as python developer or chartered accountant.
  • location is optional and takes a city as Naukri spells it, for example Bangalore, Mumbai or Delhi.
  • experienceYears keeps jobs open to a candidate with that many years of experience; it is empty by default, which means any experience.
  • workMode accepts any, office, remote or hybrid; the default is any.
  • postedWithinDays accepts any, 1, 3, 7, 15 or 30; the default is any.
  • sort accepts relevance (the default) or date (newest first).
  • enrichJobDescription adds each saved job's full posting to its row; it is off by default. See Full postings.
  • page is the first result page to read; it defaults to 1.
  • maxItems bounds the number of saved rows; it defaults to 100, and 0 removes the bound.

Response fields

Each row carries job_id, title, url, company (name, ID, logo, rating and reviews_count where Naukri shows them), locations, work_mode (remote or hybrid where the search row says so, otherwise empty; a full posting sets office, remote or hybrid), experience (min_years, max_years, label), salary (min, max, currency, label, disclosed), skills, description_snippet, posted_at as an ISO 8601 timestamp in India time, posted_label as Naukri prints it, vacancies and is_walk_in. Every row also records the query, location and page it was collected under, together with Naukri's own total for the search.

A salary that the employer hides is returned with disclosed set to false and min and max set to null, rather than as zero.

Full postings

A search row carries what Naukri's results page shows. With enrichJobDescription on, the Actor also reads each saved job's own posting and adds description_html, employment_type, role, role_category, department, industry, education, key_skills (preferred and other), applicants, views and the company's about, website and address, and it replaces work_mode with the posting's own value. Each posting is a further request, so a run takes longer, and each posting read is billed as a separate event. A posting that has closed since the search keeps its search row unchanged and is not billed.

Behaviour on large searches

Naukri serves 20 jobs per page and no more than 150 pages for one search, so a single search yields at most 3,000 jobs even when total reports tens of thousands. The run ends cleanly at that point. Splitting a broad search by location, experienceYears or postedWithinDays reaches further into the same pool.

Notes on the results

Why is relevance the default instead of newest first? Naukri matches a search more loosely in date order. On the first page of "python developer", relevance order had Python in the title or skills of all 20 jobs; date order had it in 9. Relevance pages can repeat a few jobs from the page before; the Actor saves each job once, so a repeat is neither saved nor charged twice.

Why did a search for an unusual term return unrelated jobs? When Naukri cannot match a query it broadens it and returns recent jobs rather than an empty result, exactly as its own search page does. Some meaningless queries return nothing; others return a large unrelated list. The rows are what Naukri itself shows for that query, so a check of title or skills against the search term is advisable when queries are generated automatically.

Is the salary always present? Only when the employer publishes it. Most postings in India show "Not disclosed", and those rows carry disclosed: false.

Use All-in-One Job Boards Scraper to run Naukri searches alongside Dice, Seek and ZipRecruiter in one Actor.