Dice Jobs Scraper avatar

Dice Jobs Scraper

Pricing

$2.00 / 1,000 results

Go to Apify Store
Dice Jobs Scraper

Dice Jobs Scraper

Scrape open tech roles from Dice.com's public job search: title, employer, location, employment type, salary (where posted), posted date and apply URL. Give it a keyword query. No login, no account.

Pricing

$2.00 / 1,000 results

Rating

0.0

(0)

Developer

Zilicon

Zilicon

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Unofficial. This is an independent, community-built actor. It is not affiliated with, endorsed by, or connected to Dice.com or DHI Group, Inc. in any way. "Dice" is a trademark of its respective owner and is used here only to describe what the actor reads.

Scrape open tech roles straight from Dice.com's public job search. Give it a keyword query ("software developer", "java", "data engineer") and it returns every matching role across the result pages, as clean structured rows. No login, no account, no API key.

What you get

One row per open role:

fieldnotes
idstable dice:{job-uuid}
provideralways dice
jobIdDice job UUID
titlerole title
tagsreserved (empty for now)
companyemployer (a small fraction of Dice cards show no employer, then null)
workplaceTypeRemote / Hybrid badge when Dice shows one on the card
url / applyUrlthe Dice job-detail page
locationcity, region, country (or Remote) - from the detail page
employmentTypeFull-time / Contract / Part-time etc - from the detail page
salaryMin / salaryMaxpay range where Dice publishes it (often null - Dice-optional)
publishedAtISO date the role was posted - from the detail page
teasershort plain-text description excerpt - from the detail page
detailFetchedtrue if the detail page enriched this row

Input

  • keywords - what to search Dice for. Sent to Dice's own search (?q=), so results match the site. Blank returns the newest roles across Dice.
  • maxResults - stop after N roles (32 per page). Your cost control. 0 = no cap.
  • titleOnly - keep only roles whose title contains all your keywords.
  • excludeKeywords - drop roles containing any of these words.
  • location - keep only roles whose location contains all these words (needs fetchDetails on, since location lives on the detail page).
  • remoteOnly - keep only remote roles (card badge + detail location).
  • fetchDetails - open each role's detail page to fill location, employment type, salary, posted date and description. On by default; a free extra page fetch per role.
  • maxDetail - cap how many roles get their detail page fetched (0 = all).
  • detailConcurrency - parallel detail fetches (default 5).
  • maxPages - safety cap on pages walked for a very broad query.

How it works

Dice serves its search as a server-rendered HTML page (no login, no anti-bot challenge, verified first-hand). This actor fetches dice.com/jobs?q={keywords}&page={n}, parses the 32 job cards per page off the rendered HTML, and walks pages until maxResults is reached or the last result page is hit. The keyword query runs on Dice's side; titleOnly and excludeKeywords are applied locally.

When fetchDetails is on (the default), each kept role's /job-detail/{uuid} page is fetched and its schema.org JobPosting JSON-LD parsed for the full location, employment type, salary (where published), posted date and description - a plain public page fetch, same as the search page. location and remoteOnly filter on those enriched fields.

Reads only Dice's public, unauthenticated job search - no login, no credential, no paywall. Standard public-web collection.