Dice Jobs Scraper — US tech jobs, no login

$0.90 per 1,000 jobs ($0.0009 each), plus $0.001 each time a run starts. Flat rate — no volume tiers, no plan gates — and you are charged only for jobs actually returned. That is under the $1.00 per 1,000 charged by the most-used Dice scraper on the Store, though it is not the cheapest Dice listing there.

Pull thousands of US tech jobs in minutes — titles, companies, locations, posting dates, direct apply URLs and full descriptions. No login, no cookies, no API key, no rate-limit headaches. Point it at a keyword, hit start, get data.

Who uses this

• Recruiters building a talent pipeline overnight instead of paging through Dice by hand.
• Job boards aggregating tech roles to fill their own listings.
• Market-intelligence teams tracking who is hiring, for which roles, across the entire US tech market.
• Founders watching which stacks and titles competitors are staffing up on.

Why this one

	This Actor	Typical alternative
Price per job	$0.0009 + $0.001 run start	Ranges from $0.00007 to $0.05
Login or cookies	Never	Often required
Company + apply URL	On every row	Frequently missing
Charged on failure	No	Varies

Prices for alternatives were resolved live on 2026-08-10 across every Dice-focused Actor on the Store with at least 15 monthly users, read at each one's lowest volume tier.

Features

• No Dice account, cookies, or API key required.
• Company, location, posting date and direct apply URL on every row.
• Search multiple keywords and locations with bounded pagination.
• Fetch direct job details by /job-detail/{id} URL or UUID.
• Filter by posted date, workplace type, employment type, and Easy Apply.
• Deduplicate by Dice job ID across queries, locations, and pages.
• Empty input returns one labeled sample row and does not charge.
• Invalid input, no results, blocks, parse failures, and network errors are explicit uncharged diagnostics.

Frequently asked questions

Do I need a Dice account or API key? No. Supply a keyword and nothing else.

How much does a typical run cost? 100 jobs is $0.09. 1,000 jobs is $0.90.

Am I charged for failed or empty runs? No per-result charges apply - only the $0.001 run-start fee. Blocks, parse failures and no-result runs are returned as labeled diagnostics and cost nothing.

Can I get the full job description? Yes — set includeDetails: true.

Can I filter to remote roles only? Yes, via workplaceType, plus filters for posted date and employment type.

Input examples

Search:

{
  "searchQueries": ["software engineer", "data scientist"],
  "locations": ["Remote", "Toronto, ON"],
  "postedDate": "7d",
  "maxItems": 100,
  "maxPagesPerSearch": 3,
  "includeDetails": true
}

Direct details:

{
  "jobUrls": ["https://www.dice.com/job-detail/22d98626-8e02-4bf5-9a7e-5aa9729489cb"],
  "includeDetails": true
}

Output

Real rows include jobId, title, company, location, workplaceType, employmentType, postedAt, description, url, and search context. Detail fields are populated when includeDetails is enabled.

Sample rows have _sample: true, charged: false. Diagnostics have _diagnostic: true, ok: false, and charged: false.

Billing and cost controls

Two charges apply: $0.001 each time a run starts, and $0.0009 per job ($0.90 per 1,000). The job event fires only after a valid, real job row is written — samples, diagnostics, duplicate listings and no-result searches are never charged.

Blocked requests retry on rotating datacenter addresses; this actor never uses metered (residential) proxy groups, and a RESIDENTIAL group requested in proxyConfiguration is replaced with datacenter and reported back in a diagnostic row. Your own proxyUrls are used verbatim. Keep maxProxyRetries, maxPagesPerSearch and maxItems bounded so a heavily blocked search cannot run long; the actor returns diagnostics rather than silently charging rows it did not deliver.

Endpoint and maintenance risks

Dice does not expose a documented public search API for this workflow. The actor parses server-rendered Dice HTML and uses the public /jobs/q-{query}-jobs and /job-detail/{id} routes. Dice may change selectors, route parameters, anti-bot controls, or response rendering. A selector change surfaces as PARSE_ERROR diagnostics, which are uncharged, so you find out from an empty billed total rather than from a bill for junk rows.

Diagnostic codes

BAD_INPUT, NO_RESULTS, BLOCKED, RATE_LIMITED, SERVER_ERROR, TIMEOUT, NETWORK, and PARSE_ERROR are uncharged. Each diagnostic includes the stage and a short reason where available.