# Clinical Trials Monitor — Updates, Results & Pipelines (`brick_joey_yto/clinical-trials-monitor`) Actor

Track clinical trials via the official ClinicalTrials.gov API — watch sponsors, conditions and drugs for new studies, status changes and posted results.

- **URL**: https://apify.com/brick\_joey\_yto/clinical-trials-monitor.md
- **Developed by:** [William Billings](https://apify.com/brick_joey_yto) (community)
- **Categories:** Lead generation, Business, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 result rows

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

## Clinical Trials Monitor

Track **clinical trials** via the official ClinicalTrials.gov API v2 — new studies, record updates, results postings and sponsor pipelines across ~500k registered trials. No login, no API key.

Built for **monitoring**: watch a drug, condition or sponsor and pull only what changed since your last run.

### Modes

| Mode | What it returns |
|---|---|
| **Search studies** | Trials by term, condition, sponsor, intervention, status and phase — full structured records |
| **Monitor record updates** | Studies whose records changed in a date window — status flips, enrollment updates, protocol amendments, new postings |
| **New results posted** | Studies with results first posted in a window — the trial-readout tracker investors and BD teams watch |
| **Sponsor pipeline** | A sponsor's entire trial portfolio with statuses, phases and timelines |

### Example inputs

**Watch a drug class** — schedule daily, get only changed records:

```json
{ "mode": "updates", "query": "semaglutide", "updatedAfter": "2026-09-22" }
```

**Trial readouts this quarter** (investor tracking):

```json
{ "mode": "results", "resultsAfter": "2026-07-01", "sponsor": "Pfizer" }
```

**Recruiting Phase 3 trials in a disease**:

```json
{ "mode": "studies", "condition": "lung cancer", "status": "RECRUITING", "phase": "PHASE3" }
```

**Competitor pipeline**:

```json
{ "mode": "sponsor", "sponsor": "Novartis", "status": "RECRUITING" }
```

### Output fields

`nctId`, `title`, `status`, `whyStopped`, `hasResults`, `phases`, `studyType`, `enrollment`, `sponsor`, `sponsorClass`, `collaborators`, `conditions`, `interventions`, `interventionTypes`, `primaryOutcomes`, `startDate`, `primaryCompletion`, `completionDate`, `firstPosted`, `resultsFirstPosted`, `lastUpdatePosted`, `briefSummary`, `eligibilitySex`, `eligibilityAge`, `healthyVolunteers`, `locations`, `locationCount`, `url`

### Who uses this

- **Pharma/biotech competitive intelligence** — track rivals' trial status, completions and readouts
- **Investors** — results postings and status changes are market-moving events
- **Business development** — find partner/acquisition targets via pipeline views
- **CROs & site networks** — recruiting trials by geography and phase
- **Researchers & patient advocacy** — trial availability and eligibility monitoring

### Scheduling

Records update constantly — new registrations, status changes, enrollment updates, results. Set an Apify schedule with `updatedAfter` = yesterday (daily) or last week (weekly) to emit only what changed. Same for `resultsAfter` to catch every readout.

### Honest notes

- Data is the official ClinicalTrials.gov record — authoritative for registered trials. Sponsors self-report, so enrollment/completion dates are estimates until finalized.
- `updates` mode tracks *record changes*, not just status changes — a row means "something in this record changed since the date" (could be a status flip, new site, amended outcome, or minor edit). `lastUpdatePosted` tells you when.
- `results` mode uses `ResultsFirstPostDate` — the moment a readout goes public. Follow-up results post under the same NCT ID without resetting this date.
- Results-mode yields are slower than search yields — few trials post results.

### Pricing

Pay per result — **$1.00 per 1,000 rows**, scaling down to **$0.40 per 1,000** at volume tiers. No per-run fee. Free Apify plan covers ~5,000 rows/month.

# Actor input Schema

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

What to pull from ClinicalTrials.gov

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

Free-text terms — e.g. 'KRAS inhibitor', 'semaglutide', 'CAR-T'

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

Disease/condition filter — e.g. 'lung cancer', 'alzheimer', 'obesity'

## `sponsor` (type: `string`):

Sponsor/organization name — e.g. 'Pfizer', 'Novartis'. Required for sponsor mode.

## `intervention` (type: `string`):

Drug/device/procedure name — e.g. 'pembrolizumab'

## `status` (type: `string`):

Overall status filter — e.g. RECRUITING, ACTIVE\_NOT\_RECRUITING, COMPLETED, TERMINATED

## `phase` (type: `string`):

Phase filter — e.g. PHASE1, PHASE2, PHASE3, PHASE4

## `updatedAfter` (type: `string`):

Updates mode: only records last updated after this date (YYYY-MM-DD) — use for scheduled monitoring

## `updatedBefore` (type: `string`):

Updates mode: only records last updated before this date (YYYY-MM-DD)

## `resultsAfter` (type: `string`):

Results mode: only studies with first results posted after this date (YYYY-MM-DD) — trial readout tracking

## `resultsBefore` (type: `string`):

Results mode: only studies with first results posted before this date (YYYY-MM-DD)

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

Maximum rows to return

## `proxyConfiguration` (type: `object`):

Optional — not needed normally; useful if you hit rate limits

## Actor input object example

```json
{
  "mode": "studies",
  "maxResults": 50
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset containing lobbying disclosure records

# 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 = {
    "mode": "studies",
    "query": "",
    "condition": "",
    "sponsor": "",
    "intervention": "",
    "status": "",
    "phase": "",
    "updatedAfter": "",
    "updatedBefore": "",
    "resultsAfter": "",
    "resultsBefore": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("brick_joey_yto/clinical-trials-monitor").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 = {
    "mode": "studies",
    "query": "",
    "condition": "",
    "sponsor": "",
    "intervention": "",
    "status": "",
    "phase": "",
    "updatedAfter": "",
    "updatedBefore": "",
    "resultsAfter": "",
    "resultsBefore": "",
}

# Run the Actor and wait for it to finish
run = client.actor("brick_joey_yto/clinical-trials-monitor").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 '{
  "mode": "studies",
  "query": "",
  "condition": "",
  "sponsor": "",
  "intervention": "",
  "status": "",
  "phase": "",
  "updatedAfter": "",
  "updatedBefore": "",
  "resultsAfter": "",
  "resultsBefore": ""
}' |
apify call brick_joey_yto/clinical-trials-monitor --silent --output-dataset

```

## MCP server setup

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

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/ZNNT4o5pG3uVNIXRn/builds/nOOnMAndliKIVVUdb/openapi.json