A working Naukri API request and its response

657 words ~3 min read Updated 2026-08-24

There is no public Naukri API. Naukri publishes the data on its pages and nowhere else. Anyone who needs that data in bulk must write a scraper, maintain it, and monitor it for breakages.

Here is what our own Naukri Actor returns, how much it costs, and where its limits are.

Calling it as an API

Start a run and wait for the dataset with a single call:

curl -X POST "https://api.apify.com/v2/acts/blackfalcondata~naukri-jobs-feed/run-sync-get-dataset-items?token=YOUR_TOKEN" \
 -H 'Content-Type: application/json' \
 -d '{"keyword": "..."}'

The same request in Python:

from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")
run = client.actor("blackfalcondata~naukri-jobs-feed").call(run_input={"keyword": "..."})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
 print(item)

What comes back

Each record contains 96 fields, organized into several groups:

company — companyName, companyId, companyWebsite, companyApplyJob, companyApplyUrl, companyDescription, +3 more
salary — salary, salaryMin, salaryMax, salaryCurrency, salaryVariablePercent, salaryMinPerMonth, +2 more
description — descriptionSnippet, description, descriptionHtml, descriptionMarkdown
job — jobId, jobRole, jobType
apply — applyByTime, applyCount, applyRedirectUrl

Here is one real record taken directly from a run and trimmed to its first fields:

{
 "jobId": "180826501393",
 "title": "Developer III - Apigee, JSON, JavaScript, XML",
 "companyName": "UST",
 "companyId": 5987420,
 "experienceText": "3-5 Yrs",
 "minimumExperience": 3,
 "maximumExperience": 5,
 "salary": "Not disclosed",
 "salaryMin": null,
 "salaryMax": null,
 "salaryCurrency": null,
 "salaryVariablePercent": null,
 "salaryMinPerMonth": null,
 "salaryMaxPerMonth": null
}

What you give it

The input accepts 57 options, including keyword, searchQueries, skills, jobIds, startUrls, ignoreUrlFailures, location, experience, experienceMin, experienceMax, and more.

Filters run server-side. You pay for the records you requested instead of collecting extra records and filtering them afterwards.

These figures come from a measured run, not an estimate:

30 records in 8.9 seconds
cost: $0.00101 — about $0.03 per 1,000 records

Where it stops

No endpoint stays stable forever. This one belongs to us, not Naukri, so it changes when we change it — not silently.
The source controls the rate, not the API. A larger run takes longer; it does not fail faster.
Anything behind a Naukri login is out of scope. No amount of authentication on our side can reach it.

Questions people ask

Is there an official Naukri API?

No. Naukri publishes this data on its pages but does not provide a public API for it. Every option here therefore involves reading those pages.

How do I authenticate?

Use an Apify API token, passed as ?token= or through an Authorization: Bearer header. The token belongs to you, not us, and it is the only credential involved — there is no separate account on the source site.

How long does one call take?

The measured run returned 30 records in 8.9 seconds. run-sync-get-dataset-items keeps the connection open for the full duration. For large runs, start the run and poll the dataset instead.

Can I page through results?

The run is bounded by experienceMax, not by paging through responses. You request a number of records and receive one dataset. To read that dataset in chunks, use the dataset endpoint's offset and limit parameters.

What format does it return?

JSON is the default. The dataset endpoint also serves CSV, XLSX and JSONL from the same run when you change the format parameter, with no separate export step.

Try it

run the Naukri API on Apify runs on Apify. The endpoint above is the entire integration. New accounts receive $5 of free platform credit each month, enough to cover a real run of this size several times over.

Disclosure: we build and maintain this Actor, and the link above is an affiliate link.