Extract Dice tech postings as JSON: job title, employer, location, contract type, required skills, and pay rate from the leading US board for software, IT, and engineering roles.
Dice specializes in technology hiring, indexing software, infrastructure, security, and data roles that often list explicit skill requirements and hourly or contract rates. The Dice Scraper API returns each posting as JSON with title, company, location, employment type, the technology stack mentioned, and compensation.
Tech-recruiting platforms and skills-demand analytics use it to track which languages, frameworks, and certifications employers are hiring for. Contract-versus-permanent flags and rate data are parsed out so labor-market models can segment the tech workforce precisely.
# POST a target — get validated JSON back
curl https://api.crawlzo.com/v4/scrape \
-H "Authorization: Bearer $CRAWLZO_KEY" \
-d '{
"url": "https://www.dice.com/jobs",
"type": "search",
"geo": "us"
}'
// ← response
{
"status": "ok",
"data": {
"title": "...",
"company": "...",
"location": "Remote, US",
"salary": { "min": 120000, "max": 160000, "currency": "USD" },
"posted": "2026-05-28",
"work_type": "full_time"
}
}Dice data parsed into clean, validated JSON. Pull any group below on its own, or combine them in a single request.
Tech skills-demand analytics
Contract-vs-permanent rate tracking
IT and engineering talent sourcing
Technology stack trend monitoring
Yes — Dice listings frequently enumerate languages, frameworks, and certifications, and those are parsed into the structured response alongside contract type and rate where available.
Structured JSON straight from the API, or pushed to your stack natively — S3, BigQuery, Snowflake, Postgres, Kafka, or any HTTPS webhook. Call it from Python, Node, Go, Rust, or any HTTP client. The data lands where your pipeline already lives.
No. You pay for valid, schema-passing rows only. Retries, blocks, CAPTCHAs, and 5xxs are on us. If a run doesn't return data that conforms to the schema, it isn't billed.
Every request routes through the same engine behind our Web Unblocker API: compliant residential IPs, real browser fingerprints, TLS-level evasion, behaviour modelling, and built-in CAPTCHA solving. Hard targets become routine.
Yes. We respect robots policies, rate budgets, and ToS-aware allow/deny lists. We deliver and move on — no row-level retention beyond your replay window. GDPR DPA, PII redaction, and custom data residency available on request.