/dice/jobs/search

POST /api/dice/jobs/search

Price: 5 credits

Search Dice job postings by keyword and/or filters (location, posted date, employment type, workplace setting, employer type, easy apply, remote, sponsorship). Each result carries id, title, url, summary, company (name, profile URL, logo), employment and employer type, workplace types, remote/easy-apply/sponsorship flags, location and salary.

How to use it

Search Dice (US tech job board) postings. Provide a keyword (q) and/or filters: location, posted_date (ONE/THREE/SEVEN days), employment_type (FULLTIME/PARTTIME/CONTRACTS/THIRD_PARTY, multi-select), workplace_types (Remote/On-Site/Hybrid, multi-select), employer_type (Direct Hire/Recruiter), easy_apply, is_remote, willing_to_sponsor. At least a query or one filter is required; count is how many jobs to return. Each item has id (job GUID — pass it to the Dice job get-by-id endpoint), title, url, summary, company_name, company_url, company_logo, client_brand_id, employment_type, employer_type, workplace_types, is_remote, easy_apply, willing_to_sponsor, location and salary.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• q string nullable — Keyword to search jobs by (title, skills, company) (examples: "python")
• location string nullable — Location to search in (examples: "New York, NY, USA", "Remote")
• posted_date string nullable — Only jobs posted within this window (one of: "ONE", "THREE", "SEVEN")
• employment_type array nullable — Filter by one or more employment types (one of: "FULLTIME", "PARTTIME", "CONTRACTS", "THIRD_PARTY")
• workplace_types array nullable — Filter by one or more workplace settings (one of: "Remote", "On-Site", "Hybrid")
• employer_type string nullable — Filter by who is hiring (one of: "Direct Hire", "Recruiter")
• easy_apply boolean nullable — Only jobs that support quick apply
• is_remote boolean nullable — Only fully remote jobs
• willing_to_sponsor boolean nullable — Only jobs willing to sponsor work authorization
• count integer required — Max number of jobs to return (min: 1)

Response

• @type string (default: "DiceJobSearchResult")
• id string required
• url string nullable
• summary string nullable
• company_name string nullable
• company_url string nullable
• company_logo string nullable
• client_brand_id string nullable
• employment_type string nullable
• employer_type string nullable
• workplace_types array (default: [])
• is_remote boolean nullable
• easy_apply boolean nullable
• willing_to_sponsor boolean nullable
• location object nullable
  • @type string (default: "DiceJobLocation")
  • city string nullable
  • region string nullable
  • postal_code string nullable
  • country string nullable
• salary object nullable
  • @type string (default: "DiceJobSalary")
  • text string nullable
  • currency string nullable
  • min_value number nullable
  • max_value number nullable
• posted_at string nullable
• modified_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 entity was not found, or a precondition failed 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.