Healthcare Jobs in the US API
Pricing
from $1.20 / 1,000 job records
Healthcare Jobs in the US API
Find US healthcare job postings by role, location, company, salary, posting age, employment type, and seniority. Built for healthcare recruiting, labor-market research, and workforce intelligence.
Pricing
from $1.20 / 1,000 job records
Rating
0.0
(0)
Developer
Aspen Technology Labs, Inc.
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
US Healthcare Jobs API - JobsIndex by Aspen Tech Labs
Access US healthcare jobs data through the JobsIndex API, built by Aspen Tech Labs. JobsIndex aggregates 6M+ active US job listings daily from 175K+ employer source sites, sourced directly from company career pages and ATS platforms, not scraped from job boards. The healthcare category covers 700K+ active US job postings, updated every day.
Healthcare job postings come directly from employer career pages and ATS platforms such as health systems, hospital networks, clinics, and specialty providers, along with recruitment agencies and staffing firms. This gives you broad market coverage across both direct-hire and agency-sourced healthcare roles.
This Actor covers a broad range of US healthcare and medical roles, including physicians, physician assistants, therapists, psychologists, dietitians, chiropractors, healthcare technicians, social workers, medical receptionists, patient care technicians, and many more.
This Actor serves two primary use cases: teams that want to publish healthcare job listings on their platform, and teams that need structured healthcare workforce data for matching algorithms, AI model training, or medical workforce intelligence.
What You Can Use It For
- Power a healthcare job board, medical staffing platform, or niche clinical careers site with fresh listings across the full spectrum of US healthcare roles
- Feed a matching platform with structured healthcare jobs data, filterable by role, subcategory, location, salary, or posting age
- Monitor healthcare hiring trends across US states, cities, and metro areas, useful for workforce planning, market research, or sales intelligence
- Analyze advertised salary and seniority signals across clinical, allied health, and administrative roles by location and specialty
- Collect structured US healthcare jobs for training datasets, research, or product development
Built-In Search Preset
This Actor is fixed internally to country=United States and category=Healthcare. The runtime always enforces those values even if different values are submitted. Users can narrow the search by specialty, location, salary, company, posting age, employment type, remote status, or seniority.
For a more focused nurse-only dataset, use the US Nursing Jobs API.
Quick Start
{"city": "Boston","size": 5}
Input Parameters
| Parameter | Description | Example |
|---|---|---|
salary | Salary amount or range filter. | 20h-30h |
what | Main job search query. Supports keywords, boolean logic, exact phrases, and field-targeted search such as @title therapist or @(title,description) (patient care). | therapist |
where | Free-text location search. Supports place names, boolean logic, and field-targeted search such as @country United States or @(city,metro_area) (Denver). Prefer structured location fields for exact filters. | Boston |
country | Fixed preset. Runtime always uses United States; changes are ignored. | United States |
region | State, province, or region. | California |
city | City filter. | New York |
postal_code | Postal or ZIP code filter. | 90210 |
metro_area | Metropolitan area filter. | Denver-Aurora-Centennial, CO |
title | Job title filter. | Registered Nurse |
company_name | Company name filter. | HCA Healthcare |
company_domain | Company website domain. | hcahealthcare.com |
category | Fixed preset. Runtime always uses Healthcare; changes are ignored. | Healthcare |
sub_category | More specific healthcare function or role. | Registered Nurse |
industry | Company industry filter. | Food Products |
posted | Relative posting age or ISO date. | 1w |
employment_type | Employment type. | Full-Time |
remote | Work arrangement filter. Supported values: remote, on-site, hybrid. | remote |
seniority | Seniority level. | Senior |
page | Page number, starting from 0. | 0 |
size | Number of results per page. Default 5, min 1, max 100. | 5 |
Salary Filter Format
Use:
NUMBER[UNIT]
or:
NUMBER[UNIT]-NUMBER[UNIT]
Supported units:
h- per hourd- per dayw- per weekm- per monthy- per year
Examples:
20h-30h- hourly rate between 20 and 3035h- fixed hourly rate20h-200000y- range from hourly to yearly comparison
Advanced Filters
what and where support plain-text search, boolean logic, and field-targeted search.
If no field is provided, the API expands the search across a default set of relevant fields.
Plain keyword examples:
what = therapist OR technicianwhere = United States
Field-specific examples:
what = @title therapist OR technicianwhere = @country United States
Multi-field examples:
what = @(title,description) (clinic)what = @(title,title_raw,description) (therapist OR technician)what = @(title,description) (patient AND care)where = @(country,region,city,metro_area,county,sub_city) (United States)where = @(city,region,metro_area) (San Francisco OR California)where = @(city,region,metro_area) (California)
When using where, avoid sending separate structured location parameters for the same request unless you want those structured parameters to take priority. For example, country, region, city, postal_code, and metro_area can override or narrow where.
Common job/content fields for what:
title,title_raw,description,referencecategory,sub_category,seniority,industry,company_typecompany_name,company_domain,company_name_rawemployment_type,remote,languageposted,posted_raw,expiredurl_source,url_applysalary_value,salary_currency,salary_unitid
Common location fields for where:
country,region,city,metro_area,county,sub_city,postal_code
Location Filtering
For precise location matching, use structured filters exposed for this Actor:
regioncitypostal_codemetro_area
Use where only as a free-text location search when the structured location filters above are not set. If where is provided together with structured location filters, the structured filters take priority and where may be ignored or deprioritized.
Limits and Pagination
This Actor uses the JobsIndex jobs API. Results are paginated with page and size.
| Parameter | Default | Min | Max |
|---|---|---|---|
page | 0 | 0 | Depends on size and the item cap |
size | 5 | 1 | 100 |
Invalid page or size values can return 400 Invalid page or size parameters.
Item Caps
The maximum number of retrievable jobs depends on the query shape:
| Query shape | Max items | Effective max size | Over-size behavior |
|---|---|---|---|
| No company filter | 1000 | 100 | Validation error; not silently capped |
| Company filter plus another keyword or filter | 20 | 20 | Silent cap with capping metadata |
A company filter means company_name, company_domain, or a company field referenced inside what. This Actor always applies the internal category=Healthcare preset, so company-filtered requests use the company-plus-keywords cap.
When a company-filtered request asks for size greater than the effective cap, the API returns up to the capped number of results instead of erroring. The response metadata includes:
size_requested- the original requestedsizesize_capped_by-"company|keywords"for the 20-item cap
On uncapped responses, size_requested and size_capped_by are not present.
No-company-filter requests are not silently capped. If the request exceeds the 1000-item retrieval window, the API can return 400 Item limit reached. Maximum of 1000 items can be retrieved.
Free-Text Query Limits
what and, where available, where support advanced matching syntax but have safety limits:
| Limit | Value | Error behavior |
|---|---|---|
| Raw URL length before decoding | 700 characters | 400 'what' or 'where' parameters exceed 700 characters |
| Decoded text length | 500 characters | 400 MATCH input exceeds length limit |
Combined operator characters: ?, +, pipe, @ | 20 | 400 Too many MATCH operators |
| Unsafe SQL-like keywords | blocked | 400 Unsafe MATCH expression |
Unsupported characters may be normalized before search. Unbalanced quotes and trailing @ characters may be stripped.
Field Validation
Invalid filter values can return 400 Invalid value for parameter: <name>. Common validation examples include malformed company domains, invalid dates or relative posted values, invalid salary format, invalid job IDs, unsupported location formats, or overly long field values.
Output
Each run stores job records in the default Apify dataset. The dataset schema includes an Overview table for the most useful fields and a Raw data (all fields) table for the complete JobsIndex record.
Example dataset item:
{"id": "3956505510037809027","title": "Registered Nurse","company_name": "Example Health System","category": "Healthcare","sub_category": "Registered Nurse","country": "United States","region": "Massachusetts","city": "Boston","salary_value": "42.00-55.00","salary_currency": "USD","salary_unit": "HOUR","employment_type": "Full-Time","remote": "remote","posted": "2026-04-20","url_apply": "https://example.com/apply"}
Field availability depends on the source job posting.
Custom Healthcare Data
For custom job data needs, bulk downloads, or tailored job feeds, contact us via our website or email. You can also explore JobMarketPulse, our next-generation labor and job market intelligence platform.