# Dice.com Jobs Scraper: US Tech Jobs, Salaries & New-Job Alerts (`datasmithlab/dice-jobs-scraper`) Actor

Scrape Dice.com tech jobs by keyword and location: title, company, location, parsed salary, remote/hybrid, employment type, post date, optional skills. Goes past Dice's 500-job limit, plus new-job alerts.

- **URL**: https://apify.com/datasmithlab/dice-jobs-scraper.md
- **Developed by:** [Datasmithlab](https://apify.com/datasmithlab) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.48 / 1,000 jobs

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Dice.com Jobs Scraper: US Tech Jobs, Salaries & New-Job Alerts

Export tech jobs from [Dice.com](https://www.dice.com) by **keyword and location**. Every row has the title, company, location, **salary as numbers** (min, max, currency, per hour / year), **remote / hybrid / on-site**, employment type (full-time, contract, third party), post date and the job link. Optional: the job's **skills list**.

- **Goes past Dice's 500-job limit.** Dice shows at most 25 pages × 20 jobs for one search. When a search is bigger, the Actor splits it by employment type, work location type and posting date and merges the slices, so broad searches like `Python` or `Data Engineer` return far more than 500 jobs. The `SEARCHES` report tells you how many jobs Dice lists and how many you got.
- **Salary you can sort.** Dice writes pay as free text (`USD 75.00 - 85.00 per hour`, `$$40 - $50`, `Depends on Experience`). You get `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod` plus the original `salaryText`. When Dice gives no unit (`$$40 - $50`), the period is estimated and `salaryPeriodInferred` is `true`.
- **New-job alerts.** Turn on **Only new jobs** and schedule the Actor: each run returns only jobs not seen before. Jobs already seen are **not returned and not charged**.
- **Many searches in one run.** Every keyword × location pair is searched; duplicates across searches are written once.

No login, no browser, no proxy needed. The Actor follows Dice's `robots.txt` (it never uses `?q=` search URLs; it reads the path-style search pages and job pages). **Recruiter or hiring-manager names, e-mail addresses and phone numbers are not collected**; e-mails and phone numbers inside the short text preview are removed.

### What you get

- **Job.** `title`, `url`, `id`, `postedAt`, `updatedAt`, `snippet` (short preview), `employmentTypes` (list), `easyApply`, `employerType` (Direct Hire / Recruiter / Other).
- **Company.** `company`, `companyId`.
- **Where.** `location`, `city`, `state`, `country`, `workplaceTypes` (`Remote`, `Hybrid`, `On-Site`), `isRemote`.
- **Salary.** `salaryText`, `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod`, `salaryPeriodInferred`.
- **With skills (optional).** `skills` (list) and `validThrough` (end date of the posting).
- **Search.** `searchKeyword`, `searchLocation`, `scrapedAt`; `changeType` and `firstSeenAt` in monitoring mode.
- **Reports** in the run's key-value store: `SEARCHES` (per search: jobs on Dice, jobs read, coverage, whether it hit the 500 cap) and `HEALTH`.

### How to search

| You want | Set |
|---|---|
| Python jobs in Austin | **Job titles or skills** `Python`, **Locations** `Austin, TX` |
| A title in many places | one keyword, a list of locations (`Austin, TX`, `Texas`, ...) |
| A title anywhere | a keyword, no location |
| Remote contract jobs | **Work location type** `Remote`, **Employment types** `Contract` |
| Only jobs with pay shown | **Only jobs with a stated salary** |
| Everything for a broad search | keep **Go beyond 500 jobs per search** on and raise **Max jobs** |
| A daily new-job feed | **Only new jobs** on, schedule the Actor daily |
| A Dice page you have open | paste it in **Dice search URLs** (path style, e.g. `https://www.dice.com/jobs/q-python-l-Austin,_TX-jobs`) |

Keywords are matched as a phrase: `Data Engineer` finds that title, not every job that mentions "data" or "engineer".

### Pricing

Pay per event: a small start fee, then **one charge per job row**. Jobs that do not match your filters, duplicates, and (in monitoring mode) jobs already seen are free. With **Add skills** on, each row is billed at the higher "job with skills" price, because every job page has to be opened (slower). If skills cannot be read for a job, that row is billed at the normal job price.

### Limits and honest notes

- Dice's sort order cannot be chosen; searches use Dice's own relevance order.
- On very large searches `SEARCHES.coverage` (the share of Dice's reported count you received) can stay below 1 because overlapping slices are de-duplicated; use more specific keywords or locations to reach the rest.
- Some remote jobs have no location (`location: null`).
- Full job descriptions are not included: free text often contains contact details of people.
- This Actor is not affiliated with Dice. Use it in line with Dice's terms and the law where you live.

# Actor input Schema

## `keywords` (type: `array`):

One per line, e.g. 'Python', 'Data Engineer', 'DevOps'. Words are matched as a phrase. Each keyword is searched in each location below.

## `locations` (type: `array`):

One per line: a city like 'Austin, TX' or a state like 'Texas'. Leave empty to search all of the US (and Canada). Every keyword x location pair is its own search.

## `startUrls` (type: `array`):

Or paste Dice search pages such as https://www.dice.com/jobs/q-python-l-Austin,\_TX-jobs. Dice's robots.txt does not allow '?q=' search URLs; only the path form (plus filters.\* and page) works.

## `maxItems` (type: `integer`):

Stop after this many job rows (you pay per row). Dice shows at most 500 jobs per search; large searches are split by filters automatically.

## `workplace` (type: `string`):

Filters are applied by Dice and double-checked by the scraper; jobs that don't match are not charged.

## `employmentTypes` (type: `array`):

Keep only these employment types. Leave empty for all.

## `postedWithinDays` (type: `integer`):

Only jobs posted in the last N days (1, 3 and 7 are filtered by Dice; other values are checked by the scraper). Leave empty for any date.

## `onlyWithSalary` (type: `boolean`):

Skip jobs that say 'Depends on experience' or show no pay. Skipped jobs are not charged.

## `visaSponsorshipOnly` (type: `boolean`):

Uses Dice's own sponsorship filter.

## `easyApplyOnly` (type: `boolean`):

Only jobs that can be applied to directly on Dice.

## `splitLargeSearches` (type: `boolean`):

Dice shows 500 jobs per search at most. When a search has more, it is split by employment type, work location type and posting date (one extra page request per slice, free for you). Check the SEARCHES report for coverage.

## `includeSkills` (type: `boolean`):

Adds the skills list and the posting's end date by opening every job's page (slower; billed at the higher 'job with skills' price per row).

## `onlyNewJobs` (type: `boolean`):

For scheduled runs: each run returns only jobs not seen in an earlier run with the same settings (changeType NEW). Jobs already seen are not returned and not charged. The first run returns everything as NEW.

## `proxyConfiguration` (type: `object`):

Dice answers Apify's IPs directly, so no proxy is used by default. Turn on Apify Proxy only if you see blocked searches: it is then used when a request is refused (up to 3 new IPs).

## Actor input object example

```json
{
  "keywords": [
    "Python"
  ],
  "locations": [
    "Austin, TX"
  ],
  "maxItems": 200,
  "workplace": "any",
  "onlyWithSalary": false,
  "visaSponsorshipOnly": false,
  "easyApplyOnly": false,
  "splitLargeSearches": true,
  "includeSkills": false,
  "onlyNewJobs": false
}
```

# Actor output Schema

## `jobs` (type: `string`):

Jobs table (JSON/CSV/Excel export).

## `allFields` (type: `string`):

Every field, including salary parsing, skills and the search each job came from.

## `searches` (type: `string`):

For each keyword x location: jobs Dice lists, jobs read, coverage, status.

## `health` (type: `string`):

Empty-field ratios, proxy use, blocked and failed searches.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "Python"
    ],
    "locations": [
        "Austin, TX"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("datasmithlab/dice-jobs-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": ["Python"],
    "locations": ["Austin, TX"],
}

# Run the Actor and wait for it to finish
run = client.actor("datasmithlab/dice-jobs-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "Python"
  ],
  "locations": [
    "Austin, TX"
  ]
}' |
apify call datasmithlab/dice-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,datasmithlab/dice-jobs-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/VcE5ui1uPMqViz1Ny/builds/0J3CFexRmo84u9fGs/openapi.json