Healthecareers Jobs Scraper avatar

Healthecareers Jobs Scraper

Pricing

Pay per usage

Go to Apify Store
Healthecareers Jobs Scraper

Healthecareers Jobs Scraper

Introducing the Healthecareers Jobs Scraper, a lightweight actor for efficiently scraping job listings from Healthecareers. Fast and simple. For best results and reliable data extraction, the use of residential proxies is strongly advised. Get the healthcare job data you need!

Pricing

Pay per usage

Rating

5.0

(2)

Developer

Shahid Irfan

Shahid Irfan

Maintained by Community

Actor stats

0

Bookmarked

20

Total users

6

Monthly active users

10 days ago

Last modified

Features

Limited permissions

Share

Collect healthcare job listings from Healthecareers into one dataset. Each record holds the job title, employer, location, classification, compensation signals, apply details, and the full description text. Use it for recruiting pipelines, market research, and employer tracking.

What it collects

  • Job identity: title, headline, job code, canonical URL, posting date, relative posting age.
  • Employer: name, profile link, logo and banner images.
  • Location: display location, city, state, country, latitude, longitude, remote flag.
  • Classification: profession, category, disciplines, specialties, and tag names.
  • Pay and apply: compensation range and unit, contract type, apply type, apply method, sponsored flag.
  • Description: the full posting converted to plain text.

Use cases

Recruiting lists. Pull open roles by specialty and region, then load them into a CRM or ATS.

Market research. Compare hiring volume, pay ranges, and role mix across states and professions.

Employer tracking. Follow a health system or staffing group and watch where it adds roles.

Job board feeds. Feed a search portal or matching tool with normalized listing data.

Input parameters

ParameterTypeRequiredDefaultDescription
startUrlStringNononeA Healthecareers search URL. When present, it drives the run and keyword and location are ignored.
keywordStringNonurseSearch keyword such as nurse, physician, or therapist. Ignored when startUrl is set.
locationStringNononeCity, state, or region filter. Ignored when startUrl is set.
results_wantedIntegerNo20Maximum number of jobs to save.
max_pagesIntegerNo20Safety cap on search result pages to read.
collect_detailsBooleanNotrueFetch each job detail for the full description, employment types, and apply metadata. Turn it off for faster listing-only runs.
proxyConfigurationObjectNo{"useApifyProxy": true}Proxy settings. Apify Proxy is on by default so runs can rotate addresses and collect full descriptions.

How the two search modes behave

startUrl wins. If you supply it, the actor reads the keyword, location, and category from that URL and uses them alone. A keyword or location sent alongside the URL is ignored.

Without a URL, the actor uses keyword and location. If all three search fields are empty, it runs the documented default keyword, nurse, which matches the input schema.

Output data

FieldTypeDescription
idStringListing identifier.
jobCodeStringNumeric job code from the source.
titleStringJob title.
headlineStringShort listing summary.
urlStringCanonical job URL.
postedDateStringPosting timestamp.
postedDatePhraseStringRelative posting age, for example 1 week ago.
companyIdStringEmployer identifier.
companyNameStringEmployer name.
companyProfileUrlStringEmployer profile URL when available.
locationTextStringDisplay location.
cityStringJob city.
stateStringState or region.
countryCodeStringCountry code.
latitudeNumberLatitude when available.
longitudeNumberLongitude when available.
professionStringProfession group.
categoryStringAssigned job category.
employmentTypesArrayEmployment type labels.
disciplinesArrayDiscipline labels.
specialtiesArraySpecialty labels.
tagsArrayTag names only.
applyTypeStringApply type label.
applyMethodStringApply method label.
contractTypeStringContract type label.
isRemoteBooleanRemote flag.
isSponsoredBooleanSponsored listing flag.
hasCompensationBooleanWhether pay information is present.
compensationMinNumberMinimum pay when available.
compensationMaxNumberMaximum pay when available.
compensationUnitStringPay unit when available.
descriptionTextStringFull posting as plain text.
imageUrlsArrayDirect image URLs.
sourceStringSource marker, healthecareers.

Fields with no value are left out of the record instead of being saved as empty strings.

Example input

{
"keyword": "nurse",
"location": "California",
"results_wanted": 20
}

Search URL

{
"startUrl": "https://www.healthecareers.com/search-jobs/pharmacist",
"results_wanted": 50
}

Larger run with the default proxy

{
"keyword": "physical therapist",
"results_wanted": 300,
"max_pages": 10,
"collect_details": true,
"proxyConfiguration": {
"useApifyProxy": true
}
}

useApifyProxy: true is already the default, so the line can be omitted.

Sample output

{
"id": "a9b8e8ed-dddf-42c4-9757-e74beda822bb",
"jobCode": "13638641",
"title": "NURSE ANETHETIST",
"headline": "STRENGTHEN YOUR SKILLS AS A CRNA IN ARMY MEDICINE",
"url": "https://www.healthecareers.com/job/nurse-anethetist/13638641",
"postedDate": "2026-10-31T07:11:56.427",
"postedDatePhrase": "1 week ago",
"companyId": "9d681a9d-4532-e111-9386-0050569c0075",
"companyName": "U.S. Army Medical Recruiting Brigade",
"companyProfileUrl": "https://www.healthecareers.com/healthcare-employers/us-army-medical-recruiting-brigade/80200",
"locationText": "Nationwide",
"city": "Washington",
"state": "DC",
"countryCode": "USA",
"latitude": 38.9047,
"longitude": -77.0163,
"profession": "Certified Registered Nurse Anesthetist (CRNA)",
"category": "Certified Registered Nurse Anesthetist (CRNA)",
"employmentTypes": ["Full-Time"],
"disciplines": ["Certified Registered Nurse Anesthetist (CRNA)"],
"specialties": ["Certified Registered Nurse Anesthetist (CRNA)"],
"tags": ["Loan Assistance", "Paid Time Off", "Full-Time"],
"applyType": "Resume",
"applyMethod": "Resume",
"contractType": "VALUE_BASED",
"isRemote": false,
"isSponsored": true,
"hasCompensation": false,
"compensationMin": 0,
"compensationMax": 0,
"descriptionText": "STRENGTHEN YOUR SKILLS AS A CRNA IN ARMY MEDICINE If you are looking to pursue a career in nursing that combines science with patient care...",
"imageUrls": [
"https://media.healthecareers.com/wp-content/uploads/2023/11/30221144/US-army-new-logo.png",
"https://media.healthecareers.com/wp-content/uploads/2023/11/30221143/us-army-new-banner.png.webp"
],
"source": "healthecareers"
}

Large runs and full descriptions

Full descriptions come from one request per job. The site limits how many requests one address can make before it asks for a captcha, so the actor handles volume in two ways:

  • Apify Proxy is on by default. The actor switches address every 35 requests, and a 200 job run collected 200 descriptions with zero skips.
  • If you set proxyConfiguration to {}, it enriches the first 40 jobs and saves the rest with listing data. The run still finishes and returns every job it found.

There is no bulk description endpoint. The list API omits descriptions, the search cards carry short snippets, and the RSS feed carries only company and location. Each full description needs its own detail request.

Export formats

  • JSON for APIs and internal tools
  • CSV for spreadsheets
  • Excel for reporting

Integrations

Send the dataset to Google Sheets for recruiter dashboards, Airtable for searchable hiring tables, Make or Zapier for automated follow-up, or a webhook for your own systems.

FAQ

Does a start URL override keyword and location?

Yes. A supplied startUrl runs alone. Keyword and location are read from the URL and any separate keyword or location values are ignored.

Why are some descriptions missing on a large run?

The site throttles detail requests per address. Enable a rotating proxy to collect descriptions for more jobs. The listing fields are still complete.

Is duplicate data removed?

Yes. Jobs are deduplicated by identifier within a run.

Are empty fields included?

No. Fields with no value are omitted, so the output stays readable.

Can I run without a proxy?

Yes. Set proxyConfiguration to {}. Runs under a few dozen jobs complete without one. Above that, full descriptions stop at about 40 jobs and the rest are saved with listing data.

Is INPUT.json used in production?

No. Local runs read storage/key_value_stores/default/INPUT.json. Platform runs use the input submitted through the Apify Console or API.

Support

For issues or feature requests, use the Apify Console support channels.

Resources

Use this actor in line with the website terms and applicable law. You are responsible for how you collect and use the data.