/indeed/jobs

POST /api/indeed/jobs

Price: 20 credits

Get Indeed job posting details by job key

How to use it

Get full details of an Indeed job posting by its job key, which is the 16-hex id in a job URL and is also accepted as the whole URL. Recency is relative only — posted_age carries the age as text such as '30+ days ago' and is_expired says whether Indeed still shows the posting as open; there is no absolute posting date on this endpoint, and indeed/jobs/search is where the absolute timestamps live: created_at is the posting's creation time, posted_at Indeed's day-granular publication date, and the two are independent values. openings_count is the number of openings the employer states for the posting, as text such as '3' or '10+' (bucketed at 10+), and is not an applicant count. City, state and postal code are filled for a 'City, ST' location and a county location leaves city empty; a bare state name fills state only, and on any other shape, such as 'Remote', only formatted and country are filled. direct_apply reports whether an Indeed-Apply button is offered on the posting right now, so it reads false on an expired posting whose employer did accept Indeed Apply. description_text keeps the posting's paragraph and list breaks as newlines. requirements lists the skills, education, licenses, certifications and languages Indeed shows for the posting, with level required or preferred where Indeed marks one. street_address, latitude and longitude are filled only when Indeed shows the posting's exact address.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Indeed job key, or a job URL containing it (examples: "d820ac2435637ad2", "https://www.indeed.com/viewjob?jk=d820ac2435637ad2"; minLength: 1)

Response

• @type string (default: "IndeedJob")
• id string required
• title string required
• url string required
• description string nullable
• description_text string nullable
• company object nullable
  • @type string (default: "IndeedJobCompany")
  • name string nullable
  • alias string nullable
  • image string nullable
  • cover string nullable
  • profile_url string nullable
  • rating number nullable
  • review_count integer nullable
  • parent_name string nullable
• location object nullable
  • @type string (default: "IndeedJobLocation")
  • city string nullable
  • state string nullable
  • country string nullable
  • postal_code string nullable
  • formatted string nullable
  • street_address string nullable
  • latitude number nullable
  • longitude number nullable
• salary object nullable
  • @type string (default: "IndeedJobSalary")
  • salary_min number nullable
  • salary_max number nullable
  • currency string nullable
  • unit string nullable
  • text string nullable
  • source string nullable
• employment_types array (default: [])
• job_types array (default: [])
• benefits array (default: [])
• is_remote boolean nullable
• remote_work object nullable
  • @type string (default: "IndeedRemoteWork")
  • text string nullable
  • type string nullable
• direct_apply boolean nullable
• source string nullable
• posted_age string nullable
• openings_count string nullable
• is_expired boolean nullable
• requirements array (default: [])
  • @type string (default: "IndeedJobRequirement")
  • name string required
  • category string nullable
  • level string nullable
• occupations array (default: [])
• qualifications array (default: [])
• shifts array (default: [])
• encouraged_to_apply array (default: [])
• job_details array (default: [])
  • @type string (default: "IndeedJobDetail")
  • name string required
  • values array (default: [])
• employer_response_rate number nullable
• employer_response_days integer nullable
• language 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 posting not found or no longer available 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.