# Dice Jobs Scraper (`neuro-scraper/dice-jobs-scraper`) Actor

Dice Jobs Scraper SD - Dice Jobs Scraper is a job data tool that extracts dice.com tech job listings by keyword and location: title, company, salary, employment type, remote or on-site, Easy Apply, employer type and full description. No login.

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

## Pricing

from $2.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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 Jobs Scraper — dice.com tech jobs with full descriptions

The Dice Jobs Scraper searches dice.com by keyword and location and returns one row per tech job: title, company, location, salary text and parsed range, employment type, workplace types, Easy Apply, recruiter or direct hire, posting and update dates, summary and, from each job page, the full description and validity date.

It works logged out with no API key.

#### Input

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | list | `python developer` (prefill) | One Dice search per line |
| `location` | text | `New York, NY` (prefill) | City and state; empty = anywhere |
| `startUrls` | URLs | – | Dice search URLs; their `filters.*` are kept |
| `postedDate` | select | `any` | Today, last 3 days, last 7 days |
| `employmentTypes` | multi-select | – | Full-time, Part-time, Contract, Third Party |
| `workplaceTypes` | multi-select | – | Remote, On-Site, Hybrid |
| `employerType` | select | `any` | Direct hire or recruiter |
| `easyApplyOnly`, `willingToSponsorOnly` | boolean | `false` | Dice's own filters |
| `scrapeDetails` | boolean | `true` | Open each job page (one extra request per job) |
| `maxItems` | integer | `50` | Stop after this many jobs |
| `proxyConfiguration` | proxy | Apify RESIDENTIAL | Proxy |

Filter values are read from Dice's own filter list on every run.

#### Output

| Field | Meaning |
|---|---|
| `jobId`, `jobUrl`, `title` | Job and its page |
| `companyName`, `companyId`, `companyLogo` | Company |
| `location`, `city`, `state`, `country`, `address` | Location (`address` from the job page) |
| `salary`, `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod` | Dice's salary text and numbers parsed from it; currency and period only when the text names them |
| `employmentType`, `workplaceTypes`, `isRemote`, `easyApply`, `employerType` | Job flags |
| `postedAt`, `updatedAt`, `validThrough` | Dates |
| `summary`, `descriptionText`, `descriptionHtml` | Summary from search, full text from the job page |
| `searchKeywords`, `searchLocation`, `searchUrl`, `scrapedAt` | The search that produced the row |

#### Measured (2026-10-03, one residential IP, no proxy)

| Test | Result |
|---|---|
| `python developer` / New York, NY, 40 and 50 with job pages | 40 rows in 67 s and 50 rows in 82 s; every job page read |
| `java developer`, anywhere, 800 asked, no job pages | 745 rows in 53 s from 25 pages, then Dice served page 25 again |
| `devops engineer` / Austin, full-time + contract, remote, 7 days | 20 rows: all Full-time or Contract, 20/20 Remote, all within 7 days; 1 job page answered HTTP 410 |
| Wrong URLs, empty input | Clean stop with an error line |

#### Limits (measured)

- Dice serves at most 25 pages of 30 jobs per search (asking for page 26 returned page 25). Split by location or filters for more.
- The job page's structured salary is weaker than the list text (e.g. `55` for "USD55 - USD65", or "Depends on Experience"), so salary numbers are parsed from the list text. In the 50-job test: salary text 43/50, numbers 29/50, period stated 13/50.

#### Example input

```json
{"keywords": ["devops engineer"], "location": "Austin, TX", "workplaceTypes": ["remote"], "postedDate": "last7Days", "maxItems": 100}
```

# Actor input Schema

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

One Dice search per line, e.g. "python developer", "devops engineer".

## `location` (type: `string`):

City and state as on Dice, e.g. "New York, NY", "Austin, TX". Empty = anywhere.

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

Dice job search URLs such as https://www.dice.com/jobs?q=java\&location=Chicago,%20IL\&filters.employmentType=CONTRACTS - the filters in the URL are kept.

## `postedDate` (type: `string`):

Dice's posted-date filter (values read from Dice's filter list on every run).

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

Dice's employment-type filter.

## `workplaceTypes` (type: `array`):

Dice's workplace-type filter.

## `employerType` (type: `string`):

Dice's employer-type filter.

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

Only jobs with Dice Easy Apply.

## `willingToSponsorOnly` (type: `boolean`):

Only jobs whose employer is willing to sponsor a visa (Dice's filter).

## `scrapeDetails` (type: `boolean`):

Read each job page for the full description, structured salary and validity date (one extra request per job).

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

Stop after this many jobs. Dice serves at most 25 pages (750 jobs) per search.

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

Residential proxy is recommended and is the default.

## Actor input object example

```json
{
  "keywords": [
    "python developer"
  ],
  "location": "New York, NY",
  "postedDate": "any",
  "employerType": "any",
  "easyApplyOnly": false,
  "willingToSponsorOnly": false,
  "scrapeDetails": true,
  "maxItems": 50,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# 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 developer"
    ],
    "location": "New York, NY",
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-scraper/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 developer"],
    "location": "New York, NY",
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("neuro-scraper/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 developer"
  ],
  "location": "New York, NY",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call neuro-scraper/dice-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neuro-scraper/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/7gN4z0nINX7rGfmLW/builds/dk5a4ZEAGVvvOpIKa/openapi.json