# Recruiting Clinical Trials: Sponsors and Sites (`realai_pl/recruiting-clinical-trials`) Actor

ClinicalTrials.gov recruiting studies with sponsors and reported recruiting facilities.

- **URL**: https://apify.com/realai\_pl/recruiting-clinical-trials.md
- **Developed by:** [Dawid Mańkowski](https://apify.com/realai_pl) (community)
- **Categories:** Developer tools, Automation, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 delivered recruiting clinical studies

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

## Clinical Trials Recruiting Change Monitor

Monitor ClinicalTrials.gov for recruiting-study changes instead of repeatedly exporting the same static list.

### What it tracks

Each study includes the current sponsor, status, phase, enrollment, interventions, countries, central contacts, all reported sites and recruiting sites. Reuse the same `stateKey` on scheduled runs and the Actor compares the latest snapshot with the previous one.

Change signals include:

- `NEW_TRIAL`
- `NEW_SITE`
- `SITE_REMOVED`
- `SITE_STARTED_RECRUITING`
- `SITE_STOPPED_RECRUITING`
- `STATUS_CHANGED`
- `SPONSOR_CHANGED`
- `ENROLLMENT_CHANGED`

The row also includes `previousStatus`, `previousSponsor`, `previousEnrollment`, `firstSeenAt`, `lastSeenAt` and the affected site lists.

### Search filters

You can combine:

- up to 10 conditions
- country and state/region
- sponsor/collaborator
- intervention/treatment
- study phases
- study statuses
- up to 250 results per condition

The source is the official ClinicalTrials.gov API v2. No proxy or account is required.

### Monitoring modes

`emitMode` controls what is delivered and billed:

- `all` — all matching current studies
- `new` — only studies not seen before under the state key
- `changed` — only previously seen studies whose tracked fields changed
- `new_or_changed` — new studies plus changed studies, suppressing unchanged rows

For scheduled monitoring, `new_or_changed` is normally the useful mode. The older `onlyNew` input remains supported and maps to `new_or_changed` when `emitMode` is `all`.

Example:

```json
{
  "conditions": ["lung cancer"],
  "country": "Germany",
  "phases": ["PHASE2", "PHASE3"],
  "statuses": ["RECRUITING", "NOT_YET_RECRUITING", "ACTIVE_NOT_RECRUITING"],
  "emitMode": "new_or_changed",
  "stateKey": "lung-cancer-germany",
  "limit": 100
}
```

### Why the status list matters

The API only returns statuses you request. Keep both recruiting and nearby lifecycle statuses in the watchlist if you want to detect transitions such as `RECRUITING` to `ACTIVE_NOT_RECRUITING`. Add terminal statuses if you also want those studies returned by the query.

### Pricing

The PPE event `delivered-trial` costs **$0.0015 per delivered dataset row ($1.50 / 1,000)**. Rows suppressed by monitoring mode do not trigger the delivery event. Platform compute/storage can still be consumed by a run.

`RUN_SUMMARY` reports fetched, delivered, suppressed, new, changed and unchanged counts plus the active delivery mode.

ClinicalTrials.gov records are submitted by study sponsors/investigators and can change after retrieval. Always verify important details at the linked source record. This Actor is independent of and not endorsed by NLM or NIH and does not provide medical advice.

# Actor input Schema

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

Up to ten conditions per run.

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

Optional exact country filter, e.g. Germany or United States.

## `state` (type: `string`):

Optional exact state/region filter.

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

Optional ClinicalTrials.gov sponsor search.

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

Optional intervention or treatment search.

## `phases` (type: `array`):

Optional phase filter.

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

Statuses included in the watchlist. Include terminal statuses if you also want them returned.

## `limit` (type: `integer`):

Maximum number of matching studies to fetch for each condition in this run.

## `emitMode` (type: `string`):

Monitoring modes suppress unchanged rows before PPE billing.

## `onlyNew` (type: `boolean`):

Backward-compatible alias for new\_or\_changed when emitMode is all.

## `stateKey` (type: `string`):

Use the same key on scheduled runs to compare against the previous snapshot.

## Actor input object example

```json
{
  "conditions": [
    "diabetes"
  ],
  "country": "",
  "state": "",
  "sponsor": "",
  "intervention": "",
  "statuses": [
    "RECRUITING",
    "NOT_YET_RECRUITING",
    "ACTIVE_NOT_RECRUITING",
    "ENROLLING_BY_INVITATION",
    "SUSPENDED"
  ],
  "limit": 20,
  "emitMode": "all",
  "onlyNew": false,
  "stateKey": "default"
}
```

# Actor output Schema

## `items` (type: `string`):

No description

## `summary` (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("realai_pl/recruiting-clinical-trials").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("realai_pl/recruiting-clinical-trials").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 realai_pl/recruiting-clinical-trials --silent --output-dataset

```

## MCP server setup

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

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/33WMEiTetgu5M4c6d/builds/jHB3kbFdu4DnHiKHj/openapi.json