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

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.

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

## Pricing

$2.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Dice Jobs Scraper

> **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](https://www.dice.com/jobs)'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:

| field | notes |
|-------|-------|
| `id` | stable `dice:{job-uuid}` |
| `provider` | always `dice` |
| `jobId` | Dice job UUID |
| `title` | role title |
| `tags` | reserved (empty for now) |
| `company` | employer (a small fraction of Dice cards show no employer, then `null`) |
| `workplaceType` | Remote / Hybrid badge when Dice shows one on the card |
| `url` / `applyUrl` | the Dice job-detail page |
| `location` | city, region, country (or `Remote`) - from the detail page |
| `employmentType` | Full-time / Contract / Part-time etc - from the detail page |
| `salaryMin` / `salaryMax` | pay range where Dice publishes it (often `null` - Dice-optional) |
| `publishedAt` | ISO date the role was posted - from the detail page |
| `teaser` | short plain-text description excerpt - from the detail page |
| `detailFetched` | `true` 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.

### Legal

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

# Actor input Schema

## `keywords` (type: `string`):

What to search Dice for, e.g. 'software developer', 'java', 'data engineer'. This is sent to Dice's own search (?q=), so it returns the same roles the site would. Leave blank to return the newest roles across all of Dice.

## `maxResults` (type: `integer`):

Stop after this many roles. Your cost control. Dice returns 32 roles per page, so 100 walks about 4 pages. Set 0 for no cap (walks until the last result page).

## `titleOnly` (type: `boolean`):

Keep only roles whose TITLE contains all of your keywords. Dice ranks by relevance and may return loosely related roles; turn this on to keep only titles that actually name your terms.

## `excludeKeywords` (type: `string`):

Drop any role containing ANY of these words, e.g. 'senior manager clearance'. Applied to the title, company and workplace type. Useful for stripping seniority or terms you do not want.

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

Keep only roles whose location contains ALL of these words, e.g. 'remote' or 'new york'. Dice serves the full location on the job detail page, so this filter needs 'Fetch job details' on (the default). A role that was not enriched has no location and is dropped when this filter is set.

## `remoteOnly` (type: `boolean`):

Keep only remote roles. Uses the workplace-type badge on the search card plus the detail-page location, so it is most accurate with 'Fetch job details' on.

## `fetchDetails` (type: `boolean`):

Open each role's detail page to fill in location, employment type, salary (where Dice publishes it), posted date and a short description. This is a free extra page fetch per role - it makes the location filter work and the output far richer. Turn off only for a fast title/company-only listing scrape.

## `maxDetail` (type: `integer`):

Cap how many roles get their detail page fetched. 0 (the default) enriches every returned role. Set a number to enrich only the first N and keep the rest listing-only - a way to bound runtime on a very large scrape.

## `detailConcurrency` (type: `integer`):

How many detail pages to fetch in parallel. Leave the default unless a run is being rate-limited.

## `maxPages` (type: `integer`):

Hard cap on how many search pages to walk, as a safety limit for a very broad query. Dice returns 32 roles per page. Leave the default unless you know you need more.

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

Proxy configuration. Datacenter proxies are fine for Dice.

## Actor input object example

```json
{
  "keywords": "software developer",
  "maxResults": 100,
  "titleOnly": false,
  "remoteOnly": false,
  "fetchDetails": true,
  "maxDetail": 0,
  "detailConcurrency": 5,
  "maxPages": 200,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Every job returned by the run, as rows in the default dataset.

# 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": "software developer"
};

// Run the Actor and wait for it to finish
const run = await client.actor("zilicon/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": "software developer" }

# Run the Actor and wait for it to finish
run = client.actor("zilicon/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": "software developer"
}' |
apify call zilicon/dice-jobs-scraper --silent --output-dataset

```

## MCP server setup

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