# Dice Jobs Pro (`red.cars/dice-jobs-pro`) Actor

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

## Pricing

from $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/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 Pro

Scrape **Dice.com** tech job listings: clean rows with **title, company, location, posted date, salary, employment type, summary and direct job links**, plus optional **full descriptions** from detail pages.

Search by keyword and location, paginate up to 20 pages per query. No proxy needed.

### Quick start

Set:

- `queries`: keywords to search, e.g. `["python", "DevOps engineer"]`
- `locations` (optional): e.g. `["New York, NY", "Remote"]`; paired with queries in order, extra queries run everywhere
- `pages`: result pages per query (about 30 jobs per page), default 1, max 20
- `includeDetails`: `true` to also fetch the full description for every job
- `maxItems`: stop after this many jobs, default 100

Output dataset: one row per job.

```json
{
  "queries": ["python", "data engineer"],
  "locations": ["New York, NY"],
  "pages": 2,
  "includeDetails": false,
  "maxItems": 200
}
```

### Output

| Field | Meaning |
|---|---|
| `guid` | Dice job GUID |
| `title` | Job title |
| `company` | Hiring company |
| `location` | City, region, country |
| `postedDate` | ISO timestamp Dice posted the job |
| `salary` | Salary text when Dice shows it |
| `employmentType` | Full-time / contract etc. |
| `employerType` | Direct hire / agency |
| `summary` | Short description from the listing |
| `description` | Full cleaned description (when `includeDetails: true`) |
| `url` | Direct job link on dice.com |

### Pricing

Pay per event: **$0.005 per run + $2.00 per 1,000 results**.

### Why Dice Jobs Pro

Dice is the dedicated tech-jobs board: senior engineering, security-clearance, and federal-adjacent tech roles that rarely appear on Indeed. Every row links straight to the live job page.

| | Dice Jobs Pro | Other Dice scrapers |
|---|---|---|
| Salary, employer type, posted date | Included in every row | varies |
| Full descriptions from detail pages | Optional one switch | not offered |
| Multiple queries and locations | Paired lists | one at a time |
| Pagination | Up to 20 pages per query | varies |
| Direct job URLs | Always | varies |

### FAQ

**How many jobs per page?** About 30; use `pages` to go deeper.

**Does it need a proxy?** No, plain requests work.

**Why is `description` empty?** Set `includeDetails: true`.

**Can I search without a location?** Yes, leave `locations` empty.

**Is Dice scraping allowed?** Use responsibly: moderate page counts, respect Dice's terms of service.

### Pair it with

**[ATS Job Scraper API - Greenhouse, Lever, Ashby, SmartRecruiters](https://apify.com/red.cars/multi-ats-jobs-aggregator)** pulls postings straight from the ATS public feeds, and **[Indeed Jobs Scraper Pro](https://apify.com/red.cars/indeed-jobs-scraper-pro)** covers the generalist boards.

# Actor input Schema

## `queries` (type: `array`):

Job search keywords, e.g. "python", "DevOps engineer". Each query is run as its own search.

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

Optional location filter, e.g. "New York, NY" or "Remote". Leave empty to search everywhere. Paired with queries in order: query 1 with location 1, etc.; extra queries run without a location.

## `pages` (type: `integer`):

How many result pages to fetch per query (about 30 jobs per page). Default 1, max 20.

## `includeDetails` (type: `boolean`):

Also visit each job's detail page for the full description and posting details. Slower and costs more requests.

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

Stop after collecting this many jobs in total.

## Actor input object example

```json
{
  "queries": [
    "python"
  ],
  "locations": [],
  "pages": 1,
  "includeDetails": false,
  "maxItems": 100
}
```

# Actor output Schema

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

Default dataset of job rows: job guid, title, company, location, posted date, salary, employment type, summary and direct dice.com job link; description when full descriptions are on.

# 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 = {
    "queries": [
        "python"
    ],
    "locations": [],
    "pages": 1,
    "includeDetails": false,
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("red.cars/dice-jobs-pro").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 = {
    "queries": ["python"],
    "locations": [],
    "pages": 1,
    "includeDetails": False,
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("red.cars/dice-jobs-pro").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 '{
  "queries": [
    "python"
  ],
  "locations": [],
  "pages": 1,
  "includeDetails": false,
  "maxItems": 100
}' |
apify call red.cars/dice-jobs-pro --silent --output-dataset

```

## MCP server setup

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

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/jxELIkf1rZlZqUB8F/builds/yKTKO2e3CmT4DnV28/openapi.json