Dice job search

GET https://api.api.sh/dice/v1/search
1 credit / call jobs & b2b try it in the playground →

Tech jobs on Dice (US) for a keyword and/or location, with the site's filters: radius, posted date, employment type, employer type, workplace (remote, on-site, hybrid), easy apply, visa sponsorship and company. total is Dice's count; 30 jobs per page. facets gives the counts per filter value. Each job: id, legacy_id, title, url, company, company_profile_id, logo, location, city, state, country, employment_type, employer_type, workplace_types, remote, salary (as listed), summary, easy_apply, willing_to_sponsor, posted_at, updated_at and raw. Pass next_page back as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
q string Keywords, e.g. python, java developer. Required unless location is given. Example: python
location string City, state or ZIP, e.g. Austin, TX. Example: New York, NY
radius integer Radius around the location.
radius_unit mi | km Unit of radius (default mi).
posted 1 | 3 | 7 Posted within this many days.
employment_type string Comma-separated: full_time, part_time, contract, third_party.
employer_type string Comma-separated: direct_hire, recruiter, other.
workplace string Comma-separated: remote, on_site, hybrid.
easy_apply boolean Only jobs with Dice Easy Apply.
willing_to_sponsor boolean Only employers willing to sponsor a visa.
company string Only jobs from this company, by its name as Dice shows it (the job's company), e.g. Capital One.
page integer Page number. Pass next_page from the previous response; null on the last page.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/dice/v1/search?q=python" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.