Dice Jobs Scraper — Tech Jobs, Salaries & Descriptions

Scrape public Dice technology job listings by keyword, location, search URL, or job-detail URL. The Actor returns normalized hiring data for recruiting research, job alerts, salary analysis, talent-market mapping, and AI workflows without requiring a Dice login.

What the Dice Jobs Scraper extracts

Each dataset item represents one globally deduplicated public Dice job.

Field group	Included data
Job identity	Dice job ID, title, canonical job URL
Employer	Company name, Dice company URL, public logo URL
Location	Display location, city, state/region, postal code, country
Work terms	Remote/hybrid/on-site, normalized employment types, original employment label
Compensation	Displayed salary, numeric minimum/maximum, currency, original pay period
Content	Cleaned description up to 20,000 characters and public skill labels
Dates	Posted date, valid-through date, scrape timestamp
Application	Easy Apply flag and the public Dice apply/redirect URL
Provenance	Search keyword, search location, and source page

The Actor writes run diagnostics to the OUTPUT key-value-store record instead of mixing warnings into the job dataset. OUTPUT includes page counts, discovered links, duplicates, filtered jobs, invalid records, event-cost estimates, and bounded warnings.

When to use it

Use this Actor to:

• build current lists of US technology openings;
• monitor roles, companies, locations, remote work, and salary ranges;
• feed structured job data into a database, spreadsheet, ATS research workflow, or AI agent;
• schedule recurring Dice searches and compare newly posted jobs;
• retrieve one or more known public Dice job-detail URLs.

Do not use it for candidate profiles, résumé databases, account-only pages, automated applications, login workflows, or private employer data. It does not convert hourly salary to annual salary, because doing so would require assumptions about working hours.

Input

Input	Default	Purpose
searches	Software engineer in New York	Up to 10 keyword/location searches. Set [] when using only start URLs.
startUrls	[]	Up to 100 public Dice search or job-detail URLs.
maxResults	50	Global unique-job cap across all sources, 1–1,000.
maxPagesPerSearch	5	Pagination cap per search URL, 1–20.
includeDescription	true	Keep the cleaned full public description.
datePostedDays	0	Keep jobs posted within 1–30 days; 0 disables the filter.
workplaceTypes	[]	Optional remote, hybrid, or on-site filter.
employmentTypes	[]	Optional full-time, part-time, contract, temporary, or internship filter.
minimumSalary	0	Require a disclosed salary maximum in its original pay period.
proxyConfiguration	No proxy	Standard Apify proxy configuration for networks where direct Dice access is restricted.

Search example

{
  "searches": [
    { "keyword": "data engineer", "location": "Austin, TX" },
    { "keyword": "Kubernetes", "location": "" }
  ],
  "maxResults": 100,
  "maxPagesPerSearch": 5,
  "workplaceTypes": ["remote", "hybrid"],
  "datePostedDays": 7,
  "includeDescription": true
}

Direct URL example

Input-schema defaults are applied by API runs, so explicitly send "searches": [] for URL-only work.

{
  "searches": [],
  "startUrls": [
    { "url": "https://www.dice.com/jobs?q=python&location=Boston%2C%20MA" },
    { "url": "https://www.dice.com/job-detail/5e054867-0c05-4336-9769-7f57b57bc261" }
  ],
  "maxResults": 25
}

Run through the Apify API with your own token in an authorization header:

curl -X POST "https://api.apify.com/v2/acts/YOUR_USERNAME~dice-jobs-scraper/runs?waitForFinish=120" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searches":[{"keyword":"cloud engineer","location":"Seattle, WA"}],"maxResults":10}'

Output example

{
  "jobId": "db1dbf9e-ad2b-4ba6-a49f-9b1a51e4c28f",
  "title": "Software Engineer / Developer - Ruby on Rails",
  "companyName": "Tandym Tech",
  "companyUrl": "https://www.dice.com/company-profile/dedfdf09-35e7-5124-b13c-7469202490be",
  "companyLogoUrl": "https://d3qscgr6xsioh.cloudfront.net/example.png?format=webp",
  "location": "Queens, NY, 11415, US",
  "locationCity": "Queens",
  "locationRegion": "NY",
  "postalCode": "11415",
  "countryCode": "US",
  "workplaceType": "on-site",
  "employmentTypes": ["contract"],
  "employmentTypeText": "CONTRACTOR",
  "salaryText": "$70 - $70 per hour",
  "salaryMin": 70,
  "salaryMax": 70,
  "salaryCurrency": "USD",
  "salaryUnit": "hour",
  "description": "A services organization is seeking a Full Stack Developer...",
  "skills": ["Ruby on Rails"],
  "datePosted": "2026-08-28T16:13:25.000Z",
  "validThrough": "2026-09-28T16:13:25.000Z",
  "easyApply": true,
  "applyUrl": "https://www.dice.com/dashboard/login?redirectUrl=%2Fjob-applications%2Fexample%2Fwizard",
  "jobUrl": "https://www.dice.com/job-detail/db1dbf9e-ad2b-4ba6-a49f-9b1a51e4c28f",
  "searchKeyword": "software engineer",
  "searchLocation": "New York, NY",
  "sourcePage": 1,
  "scrapedAt": "2026-08-29T12:00:00.000Z"
}

Pay-per-event pricing

Event	Price
Actor start	$0.00005 per run
Dice job result	$0.002 per unique dataset item

The result event is Apify's synthetic default-dataset-item event. It is charged automatically only after a schema-valid job is written, so the Actor does not manually double-charge records. A 50-job run costs about $0.10005 in Actor events; a one-job run costs about $0.00205. Platform usage is intended to be included rather than passed through separately. Your run's maximum-charge setting can stop delivery earlier.

Reliability and limits

Dice currently serves search cards and JobPosting JSON-LD in public server-rendered HTML, so the Actor uses direct HTTP with a coherent browser identity. This is faster and less expensive than a headless browser. It retries transient failures, uses consistent sessions, deduplicates job IDs before dataset writes, persists progress during migration, and stops at result or charge limits.

If Dice returns a challenge, rate limit, or changed page shape, the Actor preserves valid partial results and writes a classified warning to OUTPUT. A valid search with no matches returns an empty dataset and a truthful EMPTY summary. Configure Apify Proxy only when direct access from your run is restricted; proxy traffic can add platform cost.

Search results and job fields can change after posting. Some employers omit salary, work mode, postal code, application URL, skills, or expiration dates; those fields are returned as null or empty arrays rather than guessed. Filters that require missing data exclude that job.

Legal and responsible use

Only public Dice pages are accessed. Use the data in accordance with Dice's terms, robots directives, applicable law, and your contractual obligations. Do not use the Actor to discriminate unlawfully, spam employers, automate applications, reidentify people, or collect account-only information. Job descriptions may contain employer-provided text; respect copyright and retain only what your use case requires.

For support, open an issue from the Actor page with the run ID, a redacted input example, the expected outcome, and the OUTPUT warning. Never include an Apify token, proxy password, cookie, or private applicant data.