/naukri/jobs/search

POST /api/naukri/jobs/search

Price: 10 credits

Search Naukri jobs by keyword and filters

How to use it

Search Naukri (naukri.com) job listings by keyword across India's largest job board. Filter by location/city, candidate experience in years, and posting freshness; order by relevance or freshness. Each result carries the job id, title, hiring company (id, name, logo, AmbitionBox employer rating, review count and reviews URL), description, location, experience range, skill keywords, walk-in interview details, the external apply/careers URL, and the posting date. Employment type, work mode, preferred skills, company profile text and office address are returned by naukri/jobs (get-by-id), not by search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search query (minLength: 1)
• count integer required — Max number of jobs to return (min: 1)
• location string nullable — City or location to filter by (e.g. bangalore, mumbai, remote). A location the source matches nowhere returns 412 rather than the unfiltered India-wide feed; a real location with no job for this keyword returns an empty list. (minLength: 1; pattern: [^\W\d_])
• experience integer nullable — Candidate work experience in years (min: 0; max: 30)
• freshness string nullable — Only jobs posted within the given period (one of: "1", "3", "7", "15", "30")
• sort string nullable — Result ordering (one of: "r", "f")

Response

• @type string (default: "NaukriJob")
• id string required
• url string required
• company object nullable
  • @type string (default: "NaukriJobCompany")
  • id string nullable
  • name string nullable
  • legal_name string nullable
  • alias string nullable
  • image string nullable
  • profile string nullable
  • address string nullable
  • rating number nullable
  • review_count integer nullable
  • reviews_url string nullable
• description string nullable
• description_text string nullable
• location string nullable
• experience_from integer nullable
• experience_to integer nullable
• employment_type string nullable
• work_mode string nullable
• vacancy_count integer nullable
• keywords array (default: [])
• preferred_keywords array (default: [])
• is_walk_in boolean nullable
• walk_in object nullable
  • @type string (default: "NaukriJobWalkIn")
  • date_from string nullable
  • date_to string nullable
  • time string nullable
  • venue string nullable
• hiring_for string nullable
• apply_url string nullable
• posted_at string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The location matches no job on the source and could not be resolved Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.