Dice Jobs Scraper

Export public Dice job listings by keyword, location or Dice search URL with Dice Jobs Scraper. Get titles, companies, locations, salary text when available, job links and optional descriptions for recruiting research, hiring-market analysis and CSV, JSON or Excel exports.

Start with a small search: available fields vary by listing, and full descriptions are optional rather than guaranteed.

Quick start

1. Open the input form, clear the example Dice search URLs if you want keyword search, and enter a job title and location.
2. Set maxItems to a small total such as 5 and run the Actor. Leave includeDetails off unless you need fuller descriptions.
3. Open the dataset to inspect results, export them or retrieve them through the Dataset API.

{
  "query": "software engineer",
  "location": "Remote",
  "maxItems": 5,
  "includeDetails": false,
  "proxyConfiguration": { "useApifyProxy": false }
}

Nonempty startUrls take precedence over keyword, location and radius inputs. Results follow the source order. There is no guaranteed newest-first ordering or complete inventory.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Get Dice software engineer jobs with descriptions
• Scrape Java developer jobs in New York on Dice
• Find remote software engineer jobs on Dice

What you get

One row per saved public job listing, with its source link and available title, company, location, work-model and salary text. Optional detail requests can add fuller descriptions. Recognized skills are a limited set of terms, not a complete requirements list, and unknown remote status remains null.

Who is it for?

• Recruiters: Compare public job requirements and hiring companies by technology or location.
• Market researchers: Analyze available salary text, employment types and work models without assuming every listing contains them.
• Data teams: Collect repeatable job-search exports for your own reporting or enrichment.
• AI agents: Retrieve a bounded dataset and summarize the returned records, rather than assuming exhaustive market coverage.

How you can use the data

• Prepare a remote software-engineer shortlist. Clear the example search URLs and use the existing keyword and location inputs with a small total cap. Keep id, detailsPageUrl, companyName, location and isRemote together, leaving unknown remote status distinct from false.
• Review Java requirements in New York. Use the public Java developer example and request descriptions when needed. Compare recognized skills with the available description, then open source links rather than treating the skill array as the complete requirements.
• Reuse a filtered data-engineer search. Supply the exact public Dice search URL shown below. Nonempty URLs override keyword, location and radius settings, so save searchUrl with each row to explain the export's scope.
• Compare your own job exports. Join separate datasets by id or detailsPageUrl to review visible changes in company, salary text or description. These comparisons happen downstream, and missing salary text is not a normalized salary value or proof of no salary.

Input settings

Setting	JSON key	Meaning
Job keywords	query	Job title or technology. Defaults to software engineer.
Location	location	Location text. Defaults to Remote.
Search radius	radius	Search distance. Defaults to 20.
Radius unit	radiusUnit	mi or km. Defaults to mi.
Maximum jobs	maxItems	Total saved jobs across searches, 1–1000. Defaults to 20.
Open detail pages	includeDetails	Attempt fuller descriptions. Defaults to false.
Dice search URLs	startUrls	Optional search URLs that override keyword search. Form example only, no API default.
Page size (unused)	pageSize	Accepted but does not change Dice's page size.
Proxy configuration	proxyConfiguration	Optional SDK settings. Form prefill is no proxy. Omission is not the same. See field help.

For an existing filtered search, copy its public Dice /jobs URL:

{
  "startUrls": [
    { "url": "https://www.dice.com/jobs?q=data%20engineer&location=Remote&radius=20&radiusUnit=mi&page=1" }
  ],
  "maxItems": 5,
  "includeDetails": true,
  "proxyConfiguration": { "useApifyProxy": false }
}

Output data

Each dataset row represents a saved job listing. Nullable fields may be missing from Dice, and skills is a limited set of recognized terms, not a complete requirements list.

Fields	Meaning
id, title	Source job identifier and job title. Nullable.
companyName, companyLogoUrl	Hiring company and available logo URL. Nullable.
location, isRemote, workplaceTypes	Location and source work-model information. Unknown remote status is null.
employmentType, employerType	Available employment and employer classifications. Nullable.
postedAt, modifiedAt	Source posting and modification values. Nullable.
salary, easyApply	Available salary text and easy-apply flag. Nullable.
detailsPageUrl, summary	Source job link and listing summary. Nullable.
skills	Recognized skills from the summary or available detail description. An array, possibly empty.
description	Optional fuller description when requested and available. Otherwise null.
searchUrl, scrapedAt	Search associated with the row and collection timestamp.

Synthetic shape-only example, not a collected job (other fields omitted for brevity):

{
  "id": null,
  "title": null,
  "companyName": null,
  "location": null,
  "isRemote": null,
  "workplaceTypes": [],
  "salary": null,
  "skills": [],
  "description": null,
  "searchUrl": "https://www.dice.com/jobs?q=software%20engineer&location=Remote&page=1",
  "scrapedAt": "2026-10-24T00:00:00.000Z"
}

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

Pay-per-event pricing uses a start event once when extraction starts and an item event for each job listing saved to the dataset. See the live Pricing tab for current rates and applicable discounts.

Check your account's run details for any additional platform usage.

Tips for best results

• Clear example search URLs before keyword research. Nonempty URL inputs override keyword, location and radius controls.
• Start with a small total cap. The cap is shared across searches, and requesting detail pages adds requests.
• Choose descriptions only when you need them. Inspect missing descriptions and other optional fields before drawing conclusions from a shortlist.
• Keep identifiers when combining exports. Use id or detailsPageUrl to remove repeated jobs, especially after continuing unfinished searches.
• Set connection preferences explicitly. The form's no-proxy prefill is not the same as omitting the proxy input.

Limits and caveats

The total item cap is an upper bound rather than a promise of that many jobs. Results follow Dice's order, with no guaranteed newest-first order or complete inventory. The accepted pageSize field does not change Dice's page size.

Salary text, remote status, employer information and descriptions can be absent. A detail-page failure can leave a usable listing without its description. Recognized skills are limited terms extracted from available text, not every requirement. No login-only or private content is supported, and this independent tool is not an official Dice API.

A completed supported search with no matches can succeed with an empty dataset. Access challenges, missing job-list data and execution failures are not evidence of no matches and can fail the run.

Near the request deadline, the Actor may save PENDING_SEARCH_URLS in the key-value store. Use those URLs as startUrls in a new run. That record is not guaranteed for every failure or partial run. Continuing can repeat jobs, so deduplicate combined exports by id or detailsPageUrl.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~dice-jobs-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "query": "software engineer",
  "location": "Remote",
  "maxItems": 5,
  "includeDetails": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/dice-jobs-scraper').call({
  "query": "software engineer",
  "location": "Remote",
  "maxItems": 5,
  "includeDetails": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/dice-jobs-scraper').call(run_input={'query': 'software engineer', 'location': 'Remote', 'maxItems': 5, 'includeDetails': False, 'proxyConfiguration': {'useApifyProxy': False}})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API usage notes

cURL — starts an asynchronous run. Wait for completion, then use its defaultDatasetId with the Dataset items API.

MCP and AI agents

You can ask your AI assistant to collect data with Dice Jobs Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Dice Jobs Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/dice-jobs-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Dice Jobs Scraper by Fetch Cat, or give it the identifier fetch_cat/dice-jobs-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Dice Jobs Scraper to collect up to 5 remote software-engineer jobs with the example search URLs cleared. Show job links, companies and available remote-status and salary fields, marking unknown values.”
• “Collect at most 5 Java developer jobs in New York and request their descriptions. Show source links, recognized skills and available description text without treating the skills array as every requirement.”
• “Retrieve up to 5 jobs from the public Dice data-engineer search URL I provide. Keep search URLs and job identifiers so I can deduplicate them against my earlier export, and explain any partial or empty outcome.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Is this a Dice jobs API alternative?

It provides API-style access to public Dice search exports through Apify. It is not affiliated with Dice and does not guarantee full coverage or access to restricted data.

Can I export Dice jobs to CSV or Excel?

Yes. Open the completed dataset in Apify and choose CSV, Excel or JSON, or retrieve records through the Dataset API.

How do I search remote jobs or a particular city?

Use location with Remote or the city name. Clear the form's example startUrls first, because nonempty search URLs override those fields. For source-specific filters, use a supported public Dice search URL.

Why are descriptions or skills missing?

Descriptions require includeDetails: true and readable detail content. Recognized skills can come from summaries without that option, but empty skills do not establish that a job has no skill requirements.

What if a search returns no data?

Check RUN_SUMMARY in the key-value store and confirm the search on Dice. A valid no-match search can succeed empty. A failed run or access challenge needs separate investigation. Start with a small, specific search rather than increasing the limit blindly.

Related Actors

• Ashby Jobs Scraper — Search another public hiring source.
• ATS Jobs Scraper for 6 ATS Sources — Collect listings across supported applicant-tracking systems.
• Built In Jobs Scraper — Explore technology hiring listings.
• Freelancer Jobs Scraper — Research project and freelance opportunities.
• Greenhouse Jobs Scraper — Export supported public Greenhouse listings.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥