# Biospace Jobs Scraper (`jobsapi/biospace-jobs-search-scraper`) Actor

Bounded public-page metadata baseline for the Biospace Jobs Scraper inventory entry. Target-specific fields are not claimed without a verified target URL.

- **URL**: https://apify.com/jobsapi/biospace-jobs-search-scraper.md
- **Developed by:** [Jobs API](https://apify.com/jobsapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.99 / 1,000 biospace job records

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Biospace Jobs Scraper

CSV rank: **904**. Store listing: [belcaidsaad/biospace-jobs-scraper](https://apify.com/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](https://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

```bash
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:

```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.

# Changelog

This Actor's version history is a separate document: https://apify.com/jobsapi/biospace-jobs-search-scraper/changelog.md

# Actor input Schema

## `mode` (type: `string`):

Search the current BioSpace job inventory, fetch one public job, or fetch multiple public jobs.

## `query` (type: `string`):

Optional BioSpace Keywords query used by search mode.

## `startUrls` (type: `array`):

Optional public BioSpace search or job-detail URLs. Search pages are followed to bounded detail pages.

## `searchUrl` (type: `string`):

Optional public BioSpace search page. Use startUrls for multiple pages.

## `jobUrl` (type: `string`):

Public BioSpace job-detail URL used by single mode.

## `jobUrls` (type: `array`):

Public BioSpace job-detail URLs used by multiple mode.

## `jobId` (type: `string`):

BioSpace numeric job ID used by single mode.

## `jobIds` (type: `array`):

BioSpace numeric job IDs used by multiple mode.

## `maxItems` (type: `integer`):

Maximum unique complete job records to emit.

## `maxPages` (type: `integer`):

Maximum public search pages to inspect in search mode.

## `timeoutMs` (type: `integer`):

Maximum time allowed for each public request.

## Actor input object example

```json
{
  "mode": "search",
  "query": "software",
  "maxItems": 5,
  "maxPages": 3,
  "timeoutMs": 30000
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `runSummary` (type: `string`):

No description

## `runSummaryCopy` (type: `string`):

No description

## `diagnostics` (type: `string`):

No description

## `runHealth` (type: `string`):

No description

## `requestReceipts` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("jobsapi/biospace-jobs-search-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("jobsapi/biospace-jobs-search-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call jobsapi/biospace-jobs-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jobsapi/biospace-jobs-search-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/p23XiOvrpJ1H5ExGx/builds/ZgwddTPWCmWYBtSRg/openapi.json