# ClinicalTrials.gov Search (flat JSON for agents) (`jovian_explorer/clinicaltrials-gov`) Actor

Search ClinicalTrials.gov by condition, intervention, sponsor, status, phase and country. One flat JSON row per study: NCT id, title, status, phase, sponsor, conditions, interventions, enrollment, dates, locations, link. For AI agents and research tracking.

- **URL**: https://apify.com/jovian\_explorer/clinicaltrials-gov.md
- **Developed by:** [Quiet Kits](https://apify.com/jovian_explorer) (community)
- **Categories:** AI, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## ClinicalTrials.gov Search, flat JSON for agents and analysts

Search the U.S. National Library of Medicine registry [ClinicalTrials.gov](https://clinicaltrials.gov) (500,000+ studies worldwide) by **condition, intervention, sponsor, status, phase, country and last update**, and get **one flat row per study** ready for a spreadsheet, a database or an AI agent.

The official v2 API returns deeply nested records. This Actor flattens the fields people actually use: NCT id, titles, recruitment status, phases, lead sponsor and class (industry, NIH, academic), collaborators, conditions, interventions, enrollment, eligibility (sex, age range, healthy volunteers), key dates, number of sites, countries, the first 50 locations and the study URL.

### What it is for

- **Patients and advocates**: recruiting trials for a condition in a country.
- **Pharma and biotech intelligence**: every Phase 3 a competitor started this year.
- **Research and journalism**: trials by sponsor, status changes, terminated studies.
- **AI agents**: one call through the Apify MCP server, structured rows back.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `condition` | string | – | disease or condition, e.g. `melanoma` |
| `intervention` | string | – | drug, device or procedure, e.g. `pembrolizumab` |
| `sponsor` | string | – | sponsor or collaborator name |
| `term` | string | – | free text across the record |
| `status` | array | `RECRUITING`, `NOT_YET_RECRUITING` | recruitment statuses; empty = all |
| `phase` | array | – | `PHASE1`…`PHASE4`, `EARLY_PHASE1`, `NA` |
| `country` | string | – | location country |
| `updatedSinceDays` | integer | 0 | studies updated in the last N days |
| `maxItems` | integer | 200 | 0 = all matching studies |

Example, recruiting Phase 3 trials for type 2 diabetes in Italy:

```json
{ "condition": "type 2 diabetes", "phase": ["PHASE3"], "country": "Italy", "status": ["RECRUITING"] }
```

### Output

```json
{
  "nctId": "NCT05123456",
  "title": "…",
  "status": "RECRUITING",
  "phases": ["PHASE3"],
  "leadSponsor": "Novo Nordisk A/S",
  "leadSponsorClass": "INDUSTRY",
  "conditions": ["Diabetes Mellitus, Type 2"],
  "interventions": [{ "type": "DRUG", "name": "Semaglutide" }],
  "enrollment": 1200,
  "startDate": "2025-03",
  "primaryCompletionDate": "2027-06",
  "countries": ["Italy", "Spain"],
  "locationsCount": 42,
  "url": "https://clinicaltrials.gov/study/NCT05123456"
}
```

### Pricing

Pay per study returned. A typical query returns 50-500 rows in a few seconds.

### Notes

Data come from the public ClinicalTrials.gov API v2 and are in the public domain. Dates are as published (year-month or full date). The `locations` field is capped at 50 sites per study to keep rows light; `locationsCount` has the full number.

# Actor input Schema

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

e.g. "type 2 diabetes", "melanoma". Supports the ClinicalTrials.gov query syntax.

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

e.g. "semaglutide", "CAR-T".

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

e.g. "Novo Nordisk".

## `term` (type: `string`):

Free text searched across the study record.

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

Leave empty for all.

## `phase` (type: `array`):

Leave empty for all.

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

Location country, e.g. "Italy" or "United States".

## `updatedSinceDays` (type: `integer`):

0 = no filter.

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

0 = all matching studies (can be tens of thousands).

## Actor input object example

```json
{
  "condition": "type 2 diabetes",
  "status": [
    "RECRUITING",
    "NOT_YET_RECRUITING"
  ],
  "updatedSinceDays": 0,
  "maxItems": 200
}
```

# Actor output Schema

## `results` (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 = {
    "condition": "type 2 diabetes"
};

// Run the Actor and wait for it to finish
const run = await client.actor("jovian_explorer/clinicaltrials-gov").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": "type 2 diabetes" }

# Run the Actor and wait for it to finish
run = client.actor("jovian_explorer/clinicaltrials-gov").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": "type 2 diabetes"
}' |
apify call jovian_explorer/clinicaltrials-gov --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jovian_explorer/clinicaltrials-gov"
        }
    }
}

```

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/k1oPqqwV0oDyX4nDp/builds/QThwxJzxxfm3dNxwW/openapi.json