/naukri/jobs

POST /api/naukri/jobs

Price: 1 credit

Get Naukri job details by id

How to use it

Get full details of a Naukri (naukri.com) job listing by its id. Returns the job title, hiring company (id, name, logo, profile text, office address, AmbitionBox employer rating, review count and reviews URL), HTML and plain-text job description, location, required experience range, employment type, work mode (office/remote/hybrid), number of vacancies, required and preferred skill keywords, walk-in interview details, the external apply/careers URL, and the posting date.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job_id string required — Naukri job id, or a job-listing URL containing it (examples: "031025015828", "https://www.naukri.com/job-listings-sap-fico-consultant-infosys-031025015828"; minLength: 1)

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 — Job not found or expired 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.