Dice Jobs Scraper (No API Key, No Login)

Search Dice.com tech jobs with a keyword, a US city, or the remote filter. This Dice Jobs Scraper returns one structured dataset row for each listing it finds, including the job title, company, location, salary text when shown, posting date, employment type, remote flag, source URL, and skills when the public detail page exposes them. Run it once for a quick sample, schedule repeat searches, or send the dataset to your recruiting and analytics workflow. No Dice account, cookie, or customer API key is needed.

Get your first results free in under 2 minutes. Start with software engineer, set location to remote, and keep the result limit small.

Table of contents

• What this Actor does
• Who uses it
• Data fields
• How to scrape Dice jobs
• Input example
• Output example
• Coverage and accuracy
• Pricing and free-plan limit
• Search tips
• Other job and company data
• MCP and AI-agent use
• Integrations and API
• Troubleshooting
• FAQ
• Related searches
• Disclaimer
• Resources
• 中文说明

What this Actor does

• Searches public Dice job listings with one or several role or skill phrases.
• Filters by remote work or a US city when Dice supports that location filter.
• Returns the direct Dice job-detail link, employer, displayed location, and the original search phrase.
• Includes salary and employment type only when Dice provides them; it does not invent missing values.
• Adds skills from a public job detail page when they can be read. Skills are optional because not every listing exposes the same detail.
• Writes each job as one dataset item so the table, JSON, CSV, Excel, and API exports use the same record.
• Stops at the configured result cap and deduplicates repeated listings within the search.

The Actor searches Dice's US listings. It is designed for public job discovery, not for applying to jobs, contacting candidates, or accessing private accounts.

Who uses it

Recruiters can collect a small, current set of technical openings for a role and location. Talent teams can compare employers, contract types, salaries, and remote availability. Job-market researchers can create repeatable snapshots of public listings. Developers can feed the JSON dataset into a spreadsheet, a CRM, a warehouse, or an internal dashboard. Candidates can use it to organize public openings, then follow each source link to check the original listing.

This Actor does not rank candidates, infer protected characteristics, or claim that a listing is still accepting applications. Verify the source page before acting on an old record.

Data fields

Field	Type	Description
title	string	Job title shown in Dice search results. Always expected on a valid listing.
company	string	Employer or staffing company shown by Dice.
location	string or null	Location displayed by Dice; remote listings can still show a city.
salary	string or null	Salary text as displayed. Currency, period, and range are not normalized.
employmentType	string or null	Dice's employment-type label when available, such as contract.
postedDate	string or null	Posting timestamp returned by Dice.
url	URL	Direct Dice job-detail page.
isRemote	boolean or null	Dice remote-work indicator when supplied.
skills	string array	Skills extracted from the public detail page; may be empty.
summary	string or null	Summary text returned by Dice. It can be an excerpt rather than a complete description.
guid	string	Dice listing identifier used to distinguish jobs.
query	string	Search phrase that returned the listing.

The title, source URL, and listing identifier are the primary fields for joining records. Salary, skills, and employment type are populated only when Dice returns them. A null salary means the source did not provide a salary value for that listing; it does not mean the job is unpaid.

How to scrape Dice jobs

1. Open the Actor and enter one or more phrases in Job search queries. Use job titles or skills, for example software engineer, data engineer, cloud security, or Python Django.
2. Set Location to remote, a US city, or an empty string for no location filter. The remote filter is a Dice search option; a remote listing may still contain a city in its location field.
3. Choose Maximum jobs per query. The Actor caps this value at 100 for each query. A smaller limit is faster and easier to review.
4. Click Start. When the run finishes, open the Job listings table, inspect the original job links, and export the default dataset as JSON, CSV, or Excel.

For recurring research, create an Apify schedule with the same input and export only the new snapshot you need. The Actor does not apply for jobs or change any Dice account settings.

Input example

{
  "queries": ["software engineer", "data engineer"],
  "location": "remote",
  "maxPerQuery": 10
}

queries is required and accepts up to five non-empty search phrases. location accepts remote, a US city such as Austin, TX, or an empty string. maxPerQuery is an integer from 1 through 100. The prefilled form uses one broad search so a first-time run is easy to inspect.

A query is sent to Dice as written. More specific terms usually produce a more useful result set: compare data engineer with Snowflake data engineer rather than placing unrelated roles in one phrase. Use separate query entries when you want separate job families; each output row records the query that found it.

Output example

The following row is from a live Dice core run. Salary is null because Dice did not include it in that listing's response.

{
  "title": "Software Engineer",
  "company": "Eliassen Group",
  "location": "Almont, Colorado, USA",
  "salary": null,
  "employmentType": "Contract",
  "postedDate": "2026-09-28T21:02:37Z",
  "url": "https://www.dice.com/job-detail/2c111156-54bf-4db5-9e48-79a115e44f2b",
  "isRemote": true,
  "skills": ["Life Insurance", "Python", "Django", "Flask", "Databricks", "MySQL", "PostgreSQL", "Cloud Computing", "Amazon Web Services", "Microsoft Azure", "Docker", "Kubernetes", "Continuous Improvement", "Computer Science", "Mathematics", "Physics", "Screening", "Artificial Intelligence", "Recruiting", "Taxes", "Insurance", "Law", "Communication", "Gmail", "Routing", "Management Consulting", "Life Sciences", "SAP BASIS", "Military"],
  "guid": "2c111156-54bf-4db5-9e48-79a115e44f2b",
  "query": "software engineer"
}

The original source page is authoritative. A job can be edited, filled, paused, or removed after a dataset snapshot was collected. The Actor preserves the values returned during its run; it does not promise that an old row remains current.

Coverage and accuracy

Dice controls the listing inventory and the fields it returns. Some jobs include a salary range; others omit salary. Salary strings are preserved as source text, so values such as $90,000–$110,000, USD 135,000 per year, and 50-55 are not forced into a potentially misleading common unit. postedDate is the timestamp supplied by the listing endpoint and can differ from a site's user-facing relative label.

The search endpoint returns a bounded set of listings per query. This is not a complete export of every job on Dice, and no scraper can guarantee that every public listing is present at every moment. Use multiple focused searches if your project covers distinct roles. Keep the result cap reasonable; a single broad query is not a substitute for a carefully scoped search plan.

Skills are a best-effort enrichment from the public detail page. They may be empty even when the summary mentions a technology. The Actor does not infer a structured skill taxonomy from prose. The summary is the text Dice makes available to the search result, not a promise of the employer's complete job description.

Pricing and free-plan limit

This Actor uses pay-per-event pricing: $0.00008 per job row written to the default dataset, or $0.08 per 1,000 stored listings. A run that produces no dataset rows has no result event to charge. Apify may bill platform compute separately according to your account plan and run settings.

Free-plan users can request up to 40 results per Actor per UTC day. The quota counts requested result capacity, not only the number of rows Dice happens to return. Paid plans are not subject to this daily result limit. When the free-plan quota is exhausted, the run exits with a clear limit message and does not fetch or bill more results.

A malformed request with no usable query is rejected. A valid query that returns no listings fails cleanly instead of appearing to be a successful empty scrape. Always review maxPerQuery before scheduling repeated searches.

Search tips

• Use remote for Dice's remote filter. Do not assume every job with a city in location is on-site; check isRemote as well.
• Keep job titles and skill phrases separate. queries: ["data engineer", "AWS cloud engineer"] is easier to analyze than a compound phrase with several unrelated roles.
• Search by a specific technology when the role title is ambiguous: Kubernetes platform engineer, Python Django, or Azure security engineer.
• Use a city name when you want local listings. Dice's location filter is centered on a city and is not a custom radius control.
• Set maxPerQuery to the number of records you can inspect. Increase it only when your dataset needs more depth.
• For salary analysis, preserve the original salary string and normalize it later with a currency and pay-period rule you can audit.
• When deduplicating across scheduled runs, use guid as the listing key and store the first-seen timestamp in your own pipeline.
• Reopen url before contacting an employer. A dataset row is a snapshot, not confirmation that the vacancy is still open.

Other job and company data

Want other job sources? Browse the myagizm Actor profile for available job and company scrapers. This Dice Actor is focused on public Dice listings; use a source-specific Actor when you need a different site's coverage or fields.

Other data families on the profile include LinkedIn, Google, YouTube, Reddit, Instagram, TikTok, and other public sources. Their inputs, coverage, and limits differ; do not pass one platform's URL to another Actor unless that Actor's input schema says it accepts it.

MCP and AI-agent use

Apify Actors can be started by AI agents through the Apify MCP integration. Give the agent a narrow task such as “search Dice for remote data engineer jobs and return the company, salary text, posting date, and source URL.” The agent should pass a valid queries array and a small maxPerQuery, then read the resulting dataset instead of inferring fields from a run status.

Keep API credentials in the MCP client's secret store. Do not paste an Apify token into an Actor input, a shared prompt, or a public issue. The dataset contains public job data, but your saved searches and account credentials remain private.

Integrations and API

Run synchronously and receive dataset rows:

curl -X POST 'https://api.apify.com/v2/acts/myagizm~dice-jobs-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{"queries":["software engineer"],"location":"remote","maxPerQuery":10}'

Start an asynchronous run:

curl -X POST 'https://api.apify.com/v2/acts/myagizm~dice-jobs-scraper/runs?token=<YOUR_APIFY_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{"queries":["data engineer"],"location":"Austin, TX","maxPerQuery":20}'

Fetch a completed run's dataset, replacing <DATASET_ID> with the ID returned by the run API:

$curl 'https://api.apify.com/v2/datasets/<DATASET_ID>/items?clean=true&format=json&view=overview&token=<YOUR_APIFY_TOKEN>'

Use the run ID to poll status. A SUCCEEDED run is not proof that the search returned results; check the dataset item count and inspect a few rows. Each row links back to Dice for review.

Troubleshooting

The run says no jobs were returned. Try a broader role phrase such as software engineer, remove a restrictive city, or use remote. Dice inventory changes over time; a zero-row result is not a claim that no such role exists anywhere.

Salary is empty. Dice did not provide salary text for that listing. The Actor leaves it null rather than guessing a compensation range from the title or company.

Skills are empty. Skill extraction is optional and relies on the public job detail page. Use summary and open url if you need to inspect the full listing.

A job URL no longer works. The employer or Dice may have closed the job after the run. Use the latest scheduled snapshot and verify the source page before acting.

The Actor rejects the input. Supply at least one non-empty phrase in queries. maxPerQuery must be between 1 and 100; location must be a string.

The free-plan message appears. Wait until the next UTC day or use an eligible paid Apify plan. Repeating the same call does not reset the requested-result counter.

FAQ

1. Does it need my Dice username or password?

No. It searches public job listings and does not log into a Dice account.

2. Do I need a Dice API key?

No customer API key is required. Start the Actor with the input fields shown above.

3. Does it search outside the United States?

No. The current search core is scoped to US Dice listings. The location field changes the US location filter; it does not switch country.

4. How do I search for remote work?

Set location to remote. Review isRemote on each row and follow the source link, because location text can still name a city.

5. Can I search several job titles at once?

Yes. Add up to five phrases to queries. Each row records the phrase that found it, so you can separate results later.

6. What does maxPerQuery limit?

It caps the number of unique listings requested for each search phrase, up to 100 per phrase.

7. Is salary always available?

No. Salary is present only when Dice returns it. Missing salary is represented as null.

8. Are salary values normalized to annual USD?

No. The salary field preserves the source text. It can contain a range, period, currency, or no value; normalize it only with explicit rules.

9. Why is skills sometimes empty?

The public detail page does not always expose a skill list, and the enrichment is best effort. The Actor does not invent skills.

10. Is summary the complete job description?

Not necessarily. It is the summary text made available by Dice's public search data and may be an excerpt.

11. Does one dataset row equal one charge?

Yes. Pay-per-event pricing charges for each job row written to the default dataset. Empty or failed runs do not create result rows to bill.

12. What is the free-plan limit?

Free-plan users can request up to 40 results per Actor per UTC day. The counter uses requested capacity, so asking for 20 results counts 20 even if Dice returns fewer.

13. Are paid plans limited to 40 results a day?

No. This daily result quota applies to Apify free-plan users. Your run is still subject to its configured result and time limits.

14. Can I schedule this Actor?

Yes. Create an Apify schedule with the search input you want to repeat. Choose a small cap and check the output before sending records to downstream systems.

15. Can I export to CSV or Excel?

Yes. Export the default dataset from Apify Console or retrieve it through the dataset API in JSON, CSV, Excel-compatible, or other supported formats.

16. Will it apply to jobs or contact employers?

No. It only collects public listing data. Open the Dice page and follow Dice's own application process.

17. Why do results change between runs?

Employers add, edit, pause, and close listings. Each run is a snapshot of what Dice returned at that time.

18. Can I use the dataset for automated hiring decisions?

This Actor provides public listing information, not candidate data or a hiring recommendation. Review applicable laws and make employment decisions through a compliant process.

19. What happens when the search matches nothing?

The Actor fails with a clear empty-result message and does not create billable result rows. Try a broader phrase or a less restrictive location.

20. Where do I report an issue?

Use the Actor's Apify Issues tab. Include the run ID, sanitized input, and the field or behavior that needs attention. Never include your API token.

Related searches

Dice jobs scraper · Dice.com job search scraper · Dice tech jobs API · Dice remote jobs scraper · US technology jobs data · software engineer jobs search · remote software engineer openings · data engineer job listings · cybersecurity analyst jobs · cloud engineer openings · Python developer jobs · Kubernetes engineer roles · AWS jobs in the United States · contract software engineer jobs · Dice salary listings · Dice company job data · current US tech vacancies · remote IT contract listings · data analyst jobs on Dice · cloud security jobs · backend engineer openings · DevOps jobs in the US · Dice job posting export · tech recruiter job dataset · public Dice job search API · Dice listing CSV export · US remote tech role search · salary text from Dice jobs · Dice job detail links · automated job market research

Disclaimer

This independent Actor is not affiliated with, endorsed by, or sponsored by Dice or its parent companies. It collects public listing information for research and workflow automation. Use the source links to verify current availability, follow Dice's terms and applicable privacy, employment, and data-protection laws, and avoid republishing information in ways that violate the rights of job posters or applicants.

Resources

• Apify API documentation
• Apify Actor documentation
• Dataset export options
• Apify schedules
• Apify integrations
• myagizm Actor profile

中文说明

Dice 职位抓取器（无需 API 密钥或登录）

按职位关键词、美国城市或远程条件搜索 Dice.com 技术岗位。 Dice 职位抓取器会把找到的每个公开职位保存为一条数据，字段包括职位名称、公司、地点、Dice 提供的薪资文本、雇佣类型、发布日期、远程标记、技能（页面可读时）和原始职位链接。你可以先做一次小规模检查，也可以定期运行并把数据交给招聘、分析或报表流程。无需 Dice 账户、Cookie 或客户自己的 API 密钥。

两分钟内可查看第一批结果。先搜索 software engineer，将 location 设为 remote，并使用较小的结果上限。

目录

• 功能说明
• 适用对象
• 数据字段
• 抓取步骤
• 输入示例
• 输出示例
• 覆盖范围与准确性
• 价格与免费套餐限制
• 搜索建议
• 其他职位和公司数据
• MCP 与 AI 智能体
• 集成与 API
• 常见问题
• 相关搜索
• 免责声明
• 资源

功能说明

• 使用一个或多个职位名称、技能或技术短语搜索 Dice 的公开职位。
• 需要时按远程岗位或美国城市筛选。
• 为每条记录提供 Dice 职位详情页、雇主、显示地点和命中该职位的搜索短语。
• 只有 Dice 实际提供薪资和雇佣类型时才填写，不会猜测缺失值。
• 如果公开详情页包含技能列表，就尽力补充技能；不同职位的详情结构可能不同。
• 每条职位保存为一个数据集项目，便于在表格、JSON、CSV、Excel 和 API 中重复使用。
• 按输入上限停止，并在一次搜索中去重重复职位。

当前搜索范围是 Dice 的美国职位。该 Actor 只用于发现公开职位，不会申请工作、联系候选人或登录私人账户。

适用对象

招聘人员可以按职位和地点收集一组近期技术岗位；人才团队可以比较雇主、合同类型、薪资和远程情况；市场研究人员可以定期保存公开职位快照；开发人员可以把 JSON 数据集接入电子表格、CRM、数据仓库或内部仪表盘。求职者也可以整理公开岗位，再打开来源链接查看原始页面。

该 Actor 不会评估候选人、推断受保护特征或保证职位仍接受申请。采取行动前，请查看原始职位页面。

数据字段

字段	类型	说明
title	字符串	Dice 搜索结果中的职位名称。有效职位通常会提供。
company	字符串	Dice 显示的雇主或招聘公司。
location	字符串或空值	Dice 展示的地点；远程职位也可能显示城市。
salary	字符串或空值	Dice 提供的薪资原文，不会标准化币种或周期。
employmentType	字符串或空值	Dice 提供的雇佣类型，例如合同职位。
postedDate	字符串或空值	Dice 返回的发布时间。
url	URL	Dice 职位详情页链接。
isRemote	布尔值或空值	Dice 提供的远程标记。
skills	字符串数组	从公开详情页提取的技能；可能为空。
summary	字符串或空值	Dice 返回的职位摘要，可能只是摘要而非完整描述。
guid	字符串	Dice 职位标识符。
query	字符串	找到该职位的搜索短语。

职位名称、来源 URL 和标识符适合用作数据关联字段。薪资、技能和雇佣类型仅在 Dice 返回时填写。salary 为 null 表示来源没有提供薪资数据，不代表职位没有报酬。

抓取步骤

1. 打开 Actor，在 Job search queries 中填写一个或多个短语，例如 software engineer、data engineer、cloud security 或 Python Django。
2. 在 Location 中填 remote、美国城市，或空字符串（不加地点过滤）。远程筛选是 Dice 的搜索选项；职位地点字段仍可能显示城市。
3. 设置 Maximum jobs per query。每个短语最多请求 100 条；先用较小的值检查结果。
4. 点击 Start。运行完成后，打开 Job listings 表格，检查原始链接，并将默认数据集导出为 JSON、CSV 或 Excel。

如果需要重复研究，可以创建 Apify schedule，并重复使用同一输入。该 Actor 不会申请职位或更改 Dice 账户设置。

输入示例

{
  "queries": ["software engineer", "data engineer"],
  "location": "remote",
  "maxPerQuery": 10
}

queries 为必填数组，最多包含五个搜索短语。location 可设为 remote、美国城市（如 Austin, TX）或空字符串。maxPerQuery 必须是 1 到 100 的整数。预填表单使用单个常见职位，方便首次检查。

Dice 会按原样处理搜索词。较具体的短语通常更容易分析，例如使用 Snowflake data engineer 而不是把不相关的职位拼成一个查询。需要比较不同职位类别时，请分成多个查询；每条结果都会记录对应的 query。

输出示例

以下记录来自一次真实 Dice 核心运行。Dice 未返回该职位薪资，因此 salary 为 null。

{
  "title": "Software Engineer",
  "company": "Eliassen Group",
  "location": "Almont, Colorado, USA",
  "salary": null,
  "employmentType": "Contract",
  "postedDate": "2026-09-28T21:02:37Z",
  "url": "https://www.dice.com/job-detail/2c111156-54bf-4db5-9e48-79a115e44f2b",
  "isRemote": true,
  "skills": ["Life Insurance", "Python", "Django", "Flask", "Databricks", "MySQL", "PostgreSQL", "Cloud Computing", "Amazon Web Services", "Microsoft Azure", "Docker", "Kubernetes", "Continuous Improvement", "Computer Science", "Mathematics", "Physics", "Screening", "Artificial Intelligence", "Recruiting", "Taxes", "Insurance", "Law", "Communication", "Gmail", "Routing", "Management Consulting", "Life Sciences", "SAP BASIS", "Military"],
  "guid": "2c111156-54bf-4db5-9e48-79a115e44f2b",
  "query": "software engineer"
}

原始页面才是最终依据。职位可能在数据集快照之后被编辑、暂停、填满或删除。Actor 保存运行时 Dice 返回的内容，不保证旧记录仍然有效。

覆盖范围与准确性

Dice 决定职位库存和返回字段。有些职位提供薪资范围，有些不提供。薪资文本保持原样，例如 $90,000–$110,000、USD 135,000 per year 和 50-55 不会被强行转换为可能有误的统一单位。postedDate 是 Dice 提供的时间戳，可能与网站上“几天前”的展示不同。

每个查询只请求有限数量的职位。这不是 Dice 全站职位的完整导出，也无法保证每个公开岗位在每个时刻都被返回。如果研究覆盖多个岗位类别，请使用多个明确的短语。宽泛关键词不能替代精心设计的搜索范围。

技能属于尽力补充字段，来源是公开职位详情页。即使摘要提到了某项技术，技能数组也可能为空。Actor 不会把自然语言强行归类为标准技能体系。summary 是 Dice 搜索数据中可获得的摘要文本，不保证包含雇主的完整职位描述。

价格与免费套餐限制

本 Actor 按事件计费：每写入默认数据集的一条职位记录收费 $0.00008，即每 1,000 条约 $0.08。没有数据集行的运行不会产生结果事件费用。Apify 平台计算资源可能按你的账户套餐和运行设置另行计费。

Apify 免费套餐用户每天（UTC）每个 Actor 最多可请求 40 条结果。额度按请求容量计算，而不只按 Dice 实际返回的行数计算。付费套餐不受此每日结果额度限制。免费额度用完后，Actor 会显示清楚的限额消息并停止继续抓取。

没有有效搜索词的输入会被拒绝。有效查询若没有职位匹配，也会明确失败，而不是伪装成成功的空抓取。安排定期运行前，请先检查 maxPerQuery。

搜索建议

• 搜索远程工作时将 location 设为 remote。同时检查 isRemote；远程职位的 location 仍可能写着城市。
• 将职位名称和技能短语拆开。queries: ["data engineer", "AWS cloud engineer"] 比一个混合多个不相关岗位的长查询更好分析。
• 职位名称不够明确时，增加技术词：Kubernetes platform engineer、Python Django 或 Azure security engineer。
• 只要本地岗位时，使用城市名称。Dice 的城市筛选不等同于你自定义的精确距离半径。
• maxPerQuery 设为团队真正要检查的数量；需要更多数据时再提高。
• 做薪资分析时先保留原始薪资字符串，再用可审计的币种和支付周期规则做后处理。
• 跨 schedule 去重时可用 guid 作为职位键，并在自己的流程中记录首次发现时间。
• 联系雇主前重新打开 url。数据集记录只是快照，不代表职位仍开放。

其他职位和公司数据

需要其他职位来源时，可在 myagizm Actor 主页 查看可用的职位和公司抓取器。这个 Actor 专注于 Dice 公开职位；需要另一个网站的数据或字段时，请选择对应来源的 Actor。

主页上还包含 LinkedIn、Google、YouTube、Reddit、Instagram、TikTok 等数据类型。每个 Actor 的输入、范围和限制不同；除非输入 schema 明确支持，否则不要把某个平台的 URL 传给另一个 Actor。

MCP 与 AI 智能体

AI 智能体可通过 Apify MCP 集成启动 Actor。可以给它一个范围明确的任务，例如：“搜索 Dice 上的远程 data engineer 职位，返回公司、薪资文本、发布时间和来源链接。”智能体应传入有效 queries 数组和较小的 maxPerQuery，然后检查数据集，而不是只看运行状态就推断结果。

将 API 凭证保存在 MCP 客户端的密钥管理器中。不要把 Apify token 放进 Actor 输入、共享提示词或公开 issue。数据集包含公开职位信息，但你的搜索配置和账户凭证仍应保密。

集成与 API

同步运行并直接取得数据集行：

curl -X POST 'https://api.apify.com/v2/acts/myagizm~dice-jobs-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{"queries":["software engineer"],"location":"remote","maxPerQuery":10}'

启动异步运行：

curl -X POST 'https://api.apify.com/v2/acts/myagizm~dice-jobs-scraper/runs?token=<YOUR_APIFY_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{"queries":["data engineer"],"location":"Austin, TX","maxPerQuery":20}'

用运行结果中返回的数据集 ID 下载完成后的数据集：

$curl 'https://api.apify.com/v2/datasets/<DATASET_ID>/items?clean=true&format=json&view=overview&token=<YOUR_APIFY_TOKEN>'

可以用 run ID 轮询状态。SUCCEEDED 并不能证明搜索返回了职位；请检查数据集行数并抽查结果。每条记录都带有 Dice 来源链接。

常见问题

1. 需要 Dice 用户名或密码吗？

不需要。Actor 搜索公开职位，不会登录 Dice 账户。

2. 需要 Dice API 密钥吗？

不需要客户自己的 API 密钥。按上面的输入字段启动即可。

3. 能搜索美国以外的职位吗？

当前核心范围是 Dice 美国职位。location 只调整美国地点条件，不会切换国家。

4. 如何找远程工作？

将 location 设为 remote。同时检查每行的 isRemote 并打开来源链接，因为地点文本可能仍是城市。

5. 可以同时搜索多个职位吗？

可以。在 queries 中最多添加五个短语。每行保留找到它的短语，方便后续拆分。

6. maxPerQuery 有什么作用？

它限制每个搜索短语最多请求多少个不同职位，每个短语最多 100 条。

7. 每条记录都有薪资吗？

不是。只有 Dice 返回薪资时才会有值；未提供时记录为 null。

8. 薪资会统一成年度美元吗？

不会。salary 保留来源文本，可能包含范围、币种、周期或空值。

9. 为什么 skills 有时为空？

公开详情页不一定提供技能列表，而且技能补充是尽力而为。Actor 不会编造技能。

10. summary 是完整职位描述吗？

不一定。它是 Dice 公开搜索数据提供的摘要，可能是截取内容。

11. 一条数据集记录会收费一次吗？

会。按事件价格针对写入默认数据集的每条职位记录计费。失败或空结果不会创建结果计费行。

12. 免费套餐额度是多少？

免费套餐用户每天（UTC）每个 Actor 最多请求 40 条结果。额度按请求量计算；请求 20 条即计 20 条，即使 Dice 返回较少。

13. 付费套餐也只有每天 40 条吗？

没有。每日额度只适用于 Apify 免费套餐用户；运行仍受输入和超时设置约束。

14. 可以设置 schedule 吗？

可以。用希望重复的搜索输入创建 Apify schedule。先设较小上限，并在把数据送往下游系统前检查结果。

15. 能导出 CSV 或 Excel 吗？

可以。在 Apify Console 导出默认数据集，也可通过 dataset API 获取 JSON、CSV、Excel 兼容文件及其他支持格式。

16. Actor 会替我申请职位或联系雇主吗？

不会。它只收集公开职位数据。申请请打开 Dice 页面并使用 Dice 提供的流程。

17. 为什么不同运行结果不一样？

雇主会新增、编辑、暂停或关闭职位。每次运行都是当时 Dice 返回内容的快照。

18. 数据可以用于自动化招聘决策吗？

这个 Actor 提供公开职位信息，不提供候选人数据或录用建议。请遵守相关法律，并通过合规流程作出就业决策。

19. 搜索没有结果时会怎样？

Actor 会明确报告没有职位，并以失败结束，不写入可计费结果。可以尝试更宽泛的短语或更宽松的地点。

20. 如何反馈问题？

在 Apify Actor 的 Issues 标签页提交问题。提供 run ID、脱敏输入和出错字段；不要粘贴 API token。

相关搜索

Dice职位抓取器 · Dice.com职位搜索 · Dice远程软件工程职位 · 美国技术职位数据 · 远程软件工程师招聘 · 数据工程师岗位 · 网络安全分析师职位 · 云平台工程师工作 · Python开发者职位 · Kubernetes工程师岗位 · AWS技术工作 · 合同软件工程职位 · Dice薪资数据 · Dice公司招聘信息 · 美国科技岗位检索 · 远程IT合同职位 · 数据分析师工作 · 云安全工程师职位 · 后端工程师招聘 · DevOps美国职位 · Dice职位CSV导出 · 技术招聘职位数据集 · 公开Dice职位搜索API · Dice职位详情链接 · 美国远程技术岗位 · Dice薪资文本导出 · 软件工程师职位市场研究 · 数据工程职位搜索 · Dice公司职位清单 · 定期技术招聘监测

免责声明

本独立 Actor 与 Dice 及其母公司无关联、未获其认可或赞助。它用于研究和工作流自动化中的公开职位信息收集。请通过来源链接核实职位当前状态，遵守 Dice 条款及适用的隐私、就业和数据保护法律，并尊重职位发布者及申请人的权利。

资源

• Apify API 文档
• Apify Actor 文档
• 数据集导出说明
• Apify schedules
• Apify integrations
• myagizm Actor 主页

Errors & billing

Input errors finish with status SUCCEEDED, no results and no charge; see the OUTPUT record for the reason.

错误与计费

输入错误会以 SUCCEEDED 状态结束，不产生结果且不收费；原因请查看 OUTPUT 记录。