/indeed/companies/jobs

POST /api/indeed/companies/jobs

Price: 20 credits

List an Indeed company's open jobs by location

How to use it

List the open jobs one Indeed company posts in a location, optionally narrowed by keyword; snippet and benefits stay empty because a company's job list does not show them. X-Total-Matches is how many jobs Indeed counts for the company in that location, and Indeed lists only part of a large set, so to cover a large employer repeat the call per city or per keyword: sets of up to about 20 jobs come back whole. A location Indeed does not recognise is ignored, which shows as X-Total-Matches equal to the company's whole job count.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Indeed company alias or company URL (examples: "Walmart", "https://www.indeed.com/cmp/Neuberger-Berman"; minLength: 1)
• location string required — Where the jobs are located (examples: "Texas", "Austin, TX", "United States"; minLength: 1)
• count integer required — Max number of jobs to return (min: 1; max: 100)
• query string nullable — Keyword the job must match (examples: "cashier"; minLength: 1)

Response

• @type string (default: "IndeedSearchItem")
• id string required
• url string required
• company string nullable
• company_alias string nullable
• company_image string nullable
• company_cover string nullable
• company_rating number nullable
• company_review_count integer nullable
• location string nullable
• city string nullable
• state string nullable
• salary object nullable
  • @type string (default: "IndeedSearchSalary")
  • salary_min number nullable
  • salary_max number nullable
  • currency string nullable
  • unit string nullable
  • text string nullable
• job_types array (default: [])
• benefits array (default: [])
• is_remote boolean nullable
• is_sponsored boolean nullable
• is_urgently_hiring boolean nullable
• direct_apply boolean nullable
• snippet string nullable
• posted_age string nullable
• posted_at integer nullable
• created_at integer nullable
• hires_count integer nullable
• apply_count integer nullable
• ranked_benefits array (default: [])
• occupation_ranked_benefits array (default: [])
• normalized_title string nullable
• postal_code string nullable
• remote_work object nullable
  • @type string (default: "IndeedRemoteWork")
  • text string nullable
  • type string nullable
• expires_at integer nullable
• location_count integer 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 — Company not found 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.