/indeed/jobs/search

POST /api/indeed/jobs/search

Price: 20 credits

Search Indeed job postings by keyword and filters

How to use it

Search Indeed job postings by keyword or employer name, narrowed by location and radius, posting recency, employment type, no-experience-required postings, remote or hybrid work, and a minimum yearly pay. One query pages through up to roughly 1,500 distinct postings for a dense query and fewer when the feed is shallower, however high count is set; to cover a larger market, split it by city, employer or posting recency. X-Total-Matches is the number of postings Indeed reports for the query, which can be far above what one query pages through. The postings of Indeed's first results page lead the list and carry snippet (15 to 42 rows in the calls measured); snippet is null on the rows after them. Sponsored postings that do not match a remote or hybrid filter are left out. indeed/companies/jobs lists one employer's postings in a location. apply_count and hires_count are null when Indeed does not state them; hires_count repeats across one employer's postings and differs from indeed/jobs openings_count, the openings of a single posting. created_at is the posting's creation time and agrees with posted_age; posted_at is Indeed's publication date, at day granularity, and is an independent value: it is usually earlier than created_at, on a reposted posting far earlier, and on about 1 row in 100 it is later. All timestamps are unix seconds.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string — Search keyword; left empty, every posting matching the other filters (default: "")
• count integer required — Max number of results to return (min: 1; max: 1500)
• company string nullable — Only postings by this employer, by its name on Indeed (minLength: 1)
• location string nullable — City, state, or ZIP code
• radius string nullable — Search radius in miles around the location (one of: "exact", "miles_5", "miles_10", "miles_15", "miles_25", "miles_50", "miles_100")
• date_posted string nullable — Only jobs posted within this period (one of: "last_24_hours", "last_3_days", "last_7_days", "last_14_days")
• job_type string nullable — Employment type (one of: "fulltime", "parttime", "contract", "temporary", "internship")
• experience_level string nullable — Only postings that require no prior experience (one of: "no_experience_required")
• remote string nullable — Work setting (one of: "remote", "hybrid")
• salary string nullable — Minimum yearly pay (one of: "above_75000", "above_100000", "above_125000", "above_150000", "above_175000")

Response

• @type string (default: "IndeedSearchItem")
• id string required
• title 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 — Indeed did not recognise the location, or the source could not be fetched 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.