# Biotech & Pharma Clinical Trials Leads Scraper (NIH API) (`grimbles/biotech-clinical-trials-leads`) Actor

Extract active biotech, pharma, and medtech clinical trial sponsors from the official NIH ClinicalTrials.gov v2 API. Enriches lead sponsor company, trial phase (Phase 1-4), drug/device interventions, central contact emails/phones, principal investigators, and priority score.

- **URL**: https://apify.com/grimbles/biotech-clinical-trials-leads.md
- **Developed by:** [Grimbles Data Labs](https://apify.com/grimbles) (community)
- **Categories:** Lead generation, Automation, AI
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.35 / 1,000 clinical trial sponsor lead extracteds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Biotech & Pharma Clinical Trials Leads Scraper (NIH ClinicalTrials.gov v2 API)

**Extract active biotech, pharmaceutical, and medtech clinical trial sponsor leads directly from the official US National Institutes of Health (NIH) `ClinicalTrials.gov` REST API v2.**

Built for **CROs (Contract Research Organizations), clinical staffing agencies, lab equipment suppliers, life-sciences SaaS teams, and healthcare B2B growth workflows**, this Actor identifies newly posted or updated clinical trials, resolves the **Lead Sponsor (`INDUSTRY` / Biotech / Pharma)**, extracts **direct Central Contact & Site Contact emails/phones, Study Directors / Principal Investigators**, trial phases (`PHASE1`–`PHASE4`), drug/biologic interventions, and computes a **Commercial Priority Score (`0–100`)**.

***

### Key Features

- **100% Official NIH Open Data API v2 (`clinicaltrials.gov/api/v2/studies`)**: Zero anti-bot blocks, zero proxies needed, built-in rate limiting and `429` retry handling.
- **Commercial Biotech & Pharma Filtering (`onlyIndustrySponsors`)**: Instantly isolate commercial `INDUSTRY` sponsors (biotech startups, mid-size biopharma, medical device manufacturers) or include academic/NIH research centers.
- **Direct Study Contacts & Principal Investigators**:
  - Extracts `primaryContactName`, `primaryContactEmail`, and `primaryContactPhone` from `centralContacts` and falls back to trial facility `locations[].contacts` when central contacts are omitted.
  - Extracts `principalInvestigator` (`Study Director` / `Principal Investigator` + affiliation) from `overallOfficials`.
- **Actionable `commercialPriorityScore` (`0–100`)**: Ranks clinical trial leads based on `INDUSTRY` sponsorship, active `RECRUITING` / `NOT_YET_RECRUITING` status, Phase 1–3 commercial value, enrollment size, and verified email/phone availability.

***

### Sample Output JSON

```json
{
  "nctId": "NCT06684210",
  "briefTitle": "A Phase 2 Study of NEX-404 in Patients With Advanced Solid Tumors",
  "officialTitle": "An Open-Label, Multicenter Phase 2 Clinical Trial Evaluating NEX-404 Monotherapy",
  "overallStatus": "RECRUITING",
  "studyType": "INTERVENTIONAL",
  "phases": ["PHASE2"],
  "leadSponsorName": "NexaBio Therapeutics Inc.",
  "leadSponsorClass": "INDUSTRY",
  "collaborators": ["Memorial Sloan Kettering Cancer Center"],
  "conditions": ["Non-Small Cell Lung Cancer", "Solid Tumors"],
  "interventions": ["DRUG: NEX-404"],
  "enrollmentCount": 140,
  "startDate": "2026-10-01",
  "lastUpdateDate": "2026-11-16",
  "primaryContactName": "Dr. Sarah Jenkins, MD",
  "primaryContactRole": "CONTACT",
  "primaryContactEmail": "clinicaltrials@nexabio.com",
  "primaryContactPhone": "617-555-0189",
  "principalInvestigator": "David Chen, MD, PhD (STUDY_DIRECTOR — NexaBio Therapeutics Inc.)",
  "countries": ["United States", "France"],
  "commercialPriorityScore": 95,
  "studyUrl": "https://clinicaltrials.gov/study/NCT06684210"
}
```

***

### AI Agent (MCP) & n8n Integration

Connect this Actor directly to **Claude Desktop**, **Cursor**, or any MCP-compatible AI agent using the Apify MCP Server:

```json
{
  "mcpServers": {
    "biotech-clinical-trials-leads": {
      "url": "https://mcp.apify.com/?tools=grimbles/biotech-clinical-trials-leads",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_API_TOKEN>"
      }
    }
  }
}
```

For **n8n**, call `POST https://api.apify.com/v2/acts/grimbles~biotech-clinical-trials-leads/run-sync-get-dataset-items?token=<YOUR_APIFY_API_TOKEN>` with your desired JSON filter payload on a weekday cron schedule.

# Actor input Schema

## `conditions` (type: `array`):

Filter clinical trials by disease, therapeutic area, or condition (e.g. \['oncology', 'immunotherapy']). Leave empty for all conditions.

## `keywords` (type: `array`):

Optional keywords to search across interventions, drugs, biologics, or devices (e.g. \['mRNA', 'CAR-T', 'AI']).

## `statuses` (type: `array`):

Trial recruitment statuses to include (e.g. RECRUITING, NOT_YET_RECRUITING, ACTIVE_NOT_RECRUITING).

## `onlyIndustrySponsors` (type: `boolean`):

When enabled, filters results to commercial INDUSTRY lead sponsors (excluding academic-only trials).

## `onlyWithEmail` (type: `boolean`):

When enabled, only returns clinical trials that disclose a direct central or site contact email address.

## `country` (type: `string`):

Optional country name to filter clinical trial facility locations.

## `maxResults` (type: `integer`):

Maximum number of clinical trial sponsor leads to extract.

## Actor input object example

```json
{
  "conditions": [],
  "keywords": [],
  "statuses": [
    "RECRUITING",
    "NOT_YET_RECRUITING"
  ],
  "onlyIndustrySponsors": true,
  "onlyWithEmail": false,
  "country": "",
  "maxResults": 25
}
```

# Actor output Schema

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

Dataset containing extracted ClinicalTrials.gov sponsor leads, contacts, interventions, and commercial priority scores.

# 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 = {
    "statuses": [
        "RECRUITING",
        "NOT_YET_RECRUITING"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("grimbles/biotech-clinical-trials-leads").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 = { "statuses": [
        "RECRUITING",
        "NOT_YET_RECRUITING",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("grimbles/biotech-clinical-trials-leads").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 '{
  "statuses": [
    "RECRUITING",
    "NOT_YET_RECRUITING"
  ]
}' |
apify call grimbles/biotech-clinical-trials-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,grimbles/biotech-clinical-trials-leads"
        }
    }
}
```

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/NJb9AqpBRuWAJkU52/builds/lNYcDLHU4SAejQjXH/openapi.json
