Biospace Jobs Scraper

CSV rank: 904. Store listing: belcaidsaad/biospace-jobs-scraper.

This local-only Actor extracts source-backed biotech and pharma jobs from the public BioSpace jobs board at jobs.biospace.com. Complete detail rows preserve employer links and profile context, locations, categories, education and employment fields, salary text, long-form HTML/text descriptions, structured sections, responsibilities, requirements, qualifications, benefits, application routes, stable hashes, and source-derived counts. It uses ordinary direct requests and does not bypass CAPTCHAs, IP blocks, authentication, paywalls, or robots restrictions.

Scope

The Actor supports search, single, and multiple modes. Search mode reads the public BioSpace listing pages and follows bounded job-detail URLs; single and multiple modes accept public /job/<id>/ URLs or IDs.

It emits a standardized job record only when a public detail page provides the job ID, title, company, location, URL, and a substantive description. Search cards are used to discover detail URLs and are never emitted as job rows. Diagnostics are kept in the DIAGNOSTICS key-value record rather than mixed into the job dataset.

Run summaries distinguish platform status (SUCCEEDED or FAILED) from data resultStatus (COMPLETE, LIMITED, SKIPPED, DEFERRED, NO_DATA, or FAILED). A confirmed source block stops requests, discards staged rows, and reports SUCCEEDED/SKIPPED; maintenance and other non-block access unavailability report SUCCEEDED/DEFERRED with no rows. Fatal zero-row processing or storage failures report FAILED/FAILED. If a later write or finalization error occurs after real rows are stored, those rows are preserved and the run is reported as SUCCEEDED/LIMITED. NO_DATA requires every requested search seed to return HTTP 2xx, an explicit source-reported zero, no matching BioSpace result-card containers, no parsed jobs, and no next page; unrecognized empty results are SUCCEEDED/DEFERRED.

Local run

apify validate-schema .actor/input_schema.json
npm run validate:schema

For local data validation, first choose a new actor-relative storage path that does not already exist. Set that path as APIFY_LOCAL_STORAGE_DIR, then run with --resurrect; never use the Actor's existing storage folder or --purge for validation. For example, on PowerShell:

$env:APIFY_LOCAL_STORAGE_DIR = 'storage-validation-unique'
apify run --resurrect --input-file .\INPUT.json
npm run validate -- storage-validation-unique

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.