# ClinicalTrials.gov Scraper (`foo121/clinical-trials-scraper`) Actor

Export clinical trials by condition, status and phase from ClinicalTrials.gov: NCT ID, title, sponsor, phase, enrollment, locations, interventions, dates. For pharma, CRO and research. Pay per result.

- **URL**: https://apify.com/foo121/clinical-trials-scraper.md
- **Developed by:** [ziv shay](https://apify.com/foo121) (community)
- **Categories:** Business
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 result items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## ClinicalTrials.gov Scraper

**Clinical trials scraper** for **ClinicalTrials.gov data** — pull structured **clinical trial data by condition**, status, phase, sponsor, and location in one run.

Built for **pharma and biotech business development, CROs, and medical researchers** who need a current, structured view of the trial landscape for a disease area or competitor. This **clinical trials scraper** reads the **official ClinicalTrials.gov API v2**, so every study comes straight from the NIH-maintained registry of record.

No API key required. Give it a condition (and optionally a drug, sponsor, or keyword) and filter by recruitment status — get back NCT IDs, titles, conditions, phase, study type, lead sponsor, enrollment, dates, and location counts as clean **ClinicalTrials.gov data**.

### What you get

| Field | Description |
|---|---|
| `nctId` | ClinicalTrials.gov registry identifier (NCT number) |
| `title` | Study title |
| `conditions` | Array of conditions / diseases studied |
| `overallStatus` | Overall recruitment status (e.g. RECRUITING, COMPLETED) |
| `phase` | Trial phase (e.g. PHASE2, PHASE3) |
| `studyType` | Study type (e.g. INTERVENTIONAL, OBSERVATIONAL) |
| `leadSponsor` | Lead sponsor organization |
| `enrollmentCount` | Target or actual enrollment count |
| `startDate` | Study start date |
| `completionDate` | Study completion (or estimated completion) date |
| `locationCount` | Number of study locations |
| `leadLocationCountry` | Country of the primary study location |
| `url` | Direct link to the study page on ClinicalTrials.gov |

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `condition` | string | `"diabetes"` | **Required.** Condition / disease to search |
| `terms` | string | — | Optional free-text term (drug, sponsor, keyword) |
| `status` | array of enums | `["RECRUITING"]` | One or more of: `RECRUITING`, `NOT_YET_RECRUITING`, `ENROLLING_BY_INVITATION`, `ACTIVE_NOT_RECRUITING`, `SUSPENDED`, `TERMINATED`, `COMPLETED`, `WITHDRAWN` |
| `maxItems` | integer | `500` | Max studies to return |

#### Example input

```json
{
  "condition": "diabetes",
  "terms": "semaglutide",
  "status": ["RECRUITING", "NOT_YET_RECRUITING"],
  "maxItems": 500
}
```

### Example run output

```json
{
  "nctId": "NCT05731674",
  "title": "A Study of Semaglutide in Adults With Type 2 Diabetes and Obesity",
  "conditions": ["Type 2 Diabetes Mellitus", "Obesity"],
  "overallStatus": "RECRUITING",
  "phase": "PHASE3",
  "studyType": "INTERVENTIONAL",
  "leadSponsor": "Novo Nordisk A/S",
  "enrollmentCount": 1240,
  "startDate": "2023-04-18",
  "completionDate": "2026-09-30",
  "locationCount": 86,
  "leadLocationCountry": "United States",
  "url": "https://clinicaltrials.gov/study/NCT05731674"
}
```

### Use cases

- **Pharma and biotech BD teams** tracking competitor pipelines and recruiting trials in a disease area.
- **CROs** sizing the trial landscape and identifying active sponsors for partnership outreach.
- **Biotech market intelligence** monitoring phase, enrollment, and status shifts across a condition.
- **Medical researchers** assembling a structured dataset of trials by condition for review or analysis.

### vs Citeline / Informa trial-intelligence

Citeline and Informa trial-intelligence products are enterprise-priced subscriptions. This **clinical trials scraper** pulls the same **official ClinicalTrials.gov registry data** the registry publishes — pay per result, no subscription.

Honest caveat: this is **registry data only**, not Citeline's curated analyst overlay (de-duplicated drug programs, competitive read-throughs, hand-coded outcomes). If you need the analyst layer, that's a paid product. If you need accurate, current registry facts at scale, this is it.

### Pricing

Pay per result — billed only for the studies returned, no subscription.

### Keywords

clinical trials scraper, ClinicalTrials.gov data, clinical trial data by condition, clinical trials API, trial pipeline data, recruiting clinical trials, clinical trial sponsor data, NCT data scraper, biotech trial intelligence, clinical trial dataset

# Actor input Schema

## `condition` (type: `string`):

Medical condition or disease to search for (e.g. "diabetes", "breast cancer", "Alzheimer").

## `terms` (type: `string`):

Free-text terms to further filter studies — drug name, sponsor, intervention, keyword, etc.

## `status` (type: `array`):

Overall study status(es) to include.

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

Maximum number of trials to output.

## Actor input object example

```json
{
  "condition": "diabetes",
  "status": [
    "RECRUITING"
  ],
  "maxItems": 500
}
```

# 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 = {
    "condition": "diabetes"
};

// Run the Actor and wait for it to finish
const run = await client.actor("foo121/clinical-trials-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 = { "condition": "diabetes" }

# Run the Actor and wait for it to finish
run = client.actor("foo121/clinical-trials-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 '{
  "condition": "diabetes"
}' |
apify call foo121/clinical-trials-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,foo121/clinical-trials-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/F4bkRY2N8sZwn2PLU/builds/ZfAVUPUUfed7aP7bg/openapi.json