# ClinicalTrials.gov New Trial & Sponsor Leads (`open-data-tools-hq/clinicaltrials-new-trial-leads`) Actor

Newly posted or updated clinical studies from the official ClinicalTrials.gov v2 API: NCT ID, title, lead sponsor, sponsor class, phase, conditions, interventions, central contacts (when listed), and sample locations. Filter by status, condition, phase; monitor mode for CRO and recruitment leads.

- **URL**: https://apify.com/open-data-tools-hq/clinicaltrials-new-trial-leads.md
- **Developed by:** [Open Data Tools](https://apify.com/open-data-tools-hq) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 results

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 New Trial & Sponsor Leads

New trial registrations are a classic signal for **CRO outreach, patient-recruitment vendors, site networks, labs, and pharma BD**. This actor returns newly posted (or recently updated) studies from the official ClinicalTrials.gov v2 API with sponsor, phase, conditions, interventions, and central contacts when the sponsor listed them.

### Who uses this

- CROs and clinical operations vendors
- Patient recruitment / retention platforms
- Central labs, imaging, and eCOA vendors
- Site networks and investigator databases
- Competitive intelligence and BD teams

### Why this actor

- **Official source**: ClinicalTrials.gov API v2 (NLM/NIH). No key.
- **Lead angle**: filter by first-post date (new trials) or last update; sponsor class (e.g. INDUSTRY); phase; condition.
- **Contacts when present**: centralContacts email/phone from the public record.
- **Monitor mode**: `onlyNewSinceLastRun`.
- **Pay per result**.

### Input examples

**Newly posted recruiting industry trials, last 14 days:**

```json
{ "daysBack": 14, "dateField": "firstPost", "sponsorClasses": ["INDUSTRY"], "statuses": ["RECRUITING", "NOT_YET_RECRUITING"] }
```

**Oncology interventional updates:**

```json
{ "daysBack": 7, "dateField": "lastUpdate", "condition": "cancer", "onlyInterventional": true }
```

### Legal

ClinicalTrials.gov data is public. Follow NLM API terms and rate expectations. Use for lawful research and B2B outreach only; do not misrepresent NIH/NLM affiliation.

# Actor input Schema

## `daysBack` (type: `integer`):

Trials whose first-post or last-update date falls in the last N days.

## `postedFrom` (type: `string`):

Optional start of first-post / last-update date range (YYYY-MM-DD).

## `postedTo` (type: `string`):

Optional end date. Defaults to today.

## `dateField` (type: `string`):

firstPost = newly registered trials; lastUpdate = recently updated listings.

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

Optional free-text query across ClinicalTrials.gov.

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

Optional condition/disease filter (e.g. diabetes, NSCLC).

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

Optional intervention/treatment filter.

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

Overall status filters such as RECRUITING, NOT_YET_RECRUITING.

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

Optional phases: PHASE1, PHASE2, PHASE3, PHASE4, EARLY_PHASE1, NA.

## `sponsorClasses` (type: `array`):

Optional lead sponsor classes: INDUSTRY, NIH, OTHER_GOV, OTHER, NETWORK, INDIV.

## `onlyInterventional` (type: `boolean`):

When true, keep interventional studies only.

## `onlyNewSinceLastRun` (type: `boolean`):

Monitor mode: skip NCT IDs already delivered to this buyer.

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

Maximum number of trials to return in this run.

## Actor input object example

```json
{
  "daysBack": 14,
  "dateField": "firstPost",
  "statuses": [
    "RECRUITING",
    "NOT_YET_RECRUITING"
  ],
  "onlyInterventional": false,
  "onlyNewSinceLastRun": false,
  "maxResults": 200
}
```

# Actor output Schema

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

Default dataset items (overview view in Console).

# 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("open-data-tools-hq/clinicaltrials-new-trial-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("open-data-tools-hq/clinicaltrials-new-trial-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 '{}' |
apify call open-data-tools-hq/clinicaltrials-new-trial-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,open-data-tools-hq/clinicaltrials-new-trial-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/MChFO7mot7RagXfYX/builds/aJv7DiUdnwPFOgdn6/openapi.json