# Pharma & Biotech Pipeline Data — Clinical Trials by Sponsor (`foxlabs/clinical-trial-sponsor-data`) Actor

Pull clinical trials for any sponsor company from ClinicalTrials.gov. Returns NCT ID, study title, phase, status, conditions, interventions, enrolment, start and completion dates, lead sponsor, collaborators and study locations.

- **URL**: https://apify.com/foxlabs/clinical-trial-sponsor-data.md
- **Developed by:** [Berkan Kaplan](https://apify.com/foxlabs) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 award records

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

## Pharma & Biotech Pipeline Data — Clinical Trials by Sponsor

A company's clinical trial register is its product pipeline, published years ahead of launch. This actor turns sponsor names into their trial portfolio — phase, status, indication, enrolment and timing — which is the single best public read on where a pharma, biotech or medtech company is heading.

**No API key · Official source · Pay only for delivered rows · Same schema across the series**

### What data do you get?

| Field | Description |
|---|---|
| `companyName` | Lead sponsor |
| `awardId` | NCT identifier |
| `awardTitle` | Brief study title |
| `status` | Overall recruitment status |
| `phase` | Trial phase |
| `studyType` | Interventional or observational |
| `conditions` | Indications studied |
| `interventions` | Drugs, devices or procedures under test |
| `enrollment` | Participant count, actual or estimated |
| `startDate` | Study start |
| `endDate` | Primary completion date |
| `collaborators` | Partner organizations on the trial |
| `sponsorClass` | INDUSTRY, NIH, OTHER — tells commercial trials from academic ones |
| `leadSponsorIsQuery` | Whether your query matched the lead sponsor or only a collaborator |
| `countries` | Countries with study locations |
| `sourceUrl` | ClinicalTrials.gov study page |

Every row also carries `query` (what you asked for), `scrapedAt` (ISO timestamp) and, when a
lookup fails, `error` explaining why.

### Example output

```json
{
  "country": "US",
  "source": "ClinicalTrials.gov",
  "companyName": "Vertex Pharmaceuticals Incorporated",
  "awardId": "NCT05668741",
  "awardTitle": "A Phase 1/2 Study of VX-522 in Participants With Cystic Fibrosis",
  "status": "ACTIVE_NOT_RECRUITING",
  "phase": "PHASE1, PHASE2",
  "enrollment": 26,
  "startDate": "2023-02-27",
  "collaborators": [
    "Moderna, Inc"
  ],
  "sponsorClass": "INDUSTRY",
  "sourceUrl": "https://clinicaltrials.gov/study/NCT05668741"
}
```

### Input

```json
{
  "queries": ["Moderna","Vertex Pharmaceuticals","BioNTech"],
  "maxResultsPerQuery": 25,
  "maxConcurrency": 3,
  "includeRaw": false
}
```

| Input | What it does |
|---|---|
| `queries` | Sponsor or collaborator names (`Moderna`, `Vertex Pharmaceuticals`, `Medtronic`). |
| `maxResultsPerQuery` | Caps how many rows one query may produce. |
| `maxConcurrency` | How many queries run at once. Lower it if the source starts throttling. |
| `includeRaw` | Attaches the source's untouched record under `raw`, for fields this actor does not map. |
| `requestDelayMs` | Politeness delay between requests. |
| `proxyConfiguration` | Optional. ClinicalTrials.gov is an open federal API and rarely needs a proxy. |

### What people use it for

- **Pipeline intelligence** — see every trial a company is running, by phase and indication, before anything is announced.
- **CRO and site prospecting** — recruiting trials are active buying centres for services, supplies and software.
- **Partnership mapping** — collaborators on a trial are the company's real partners, named on the record.

### Notes and limits

- The sponsor search matches collaborators as well as lead sponsors. `leadSponsorIsQuery` tells you which happened, so you can filter to trials a company actually runs.
- Phase is a list — a Phase 1/2 trial returns both values.

### Where the data comes from

The US National Library of Medicine publishes ClinicalTrials.gov as a documented open API with no key. Source: [ClinicalTrials.gov API v2](https://clinicaltrials.gov/)

### FAQ

#### Is this ClinicalTrials.gov sponsor scraper free?

The data source is free and needs no API key — you pay only for the rows the run delivers ($0.003 each). Failed or empty lookups are never charged.

#### Do I need an API key or a login?

No. The US National Library of Medicine publishes ClinicalTrials.gov as a documented open API with no key.

#### What can I search by?

By sponsor company name (`Moderna`, `Roche`). The search covers lead sponsors and collaborators, so partnered trials show up too.

#### How current is the data?

Every run queries the source live, so results are as fresh as the source itself. The registry updates daily as sponsors file changes.

#### How fast is it, and how many queries can I run?

Queries run concurrently (3 at a time by default, tunable in the input). A prefilled run finishes in seconds; large lists scale roughly linearly and stay well inside a normal run timeout.

#### Can I export the results to CSV, Excel or JSON?

Yes. Apify datasets export to CSV, Excel, JSON, XML and HTML, and can be pulled through the API or pushed to your own storage.

#### What happens when a query returns nothing?

You still get a row, carrying your original `query` and an `error` field explaining why. Nothing is silently dropped, and you are not charged for it.

#### Is scraping this data legal?

Yes. ClinicalTrials.gov is a public registry that sponsors are legally required to publish to. It carries study data, not patient data.

***

Built by [Fox Labs](https://apify.com/foxlabs) — B2B company intelligence from public sources, as clean JSON.

# Actor input Schema

## `queries` (type: `array`):

Sponsor or collaborator names (`Moderna`, `Vertex Pharmaceuticals`, `Medtronic`).

## `maxResultsPerQuery` (type: `integer`):

How many rows a single query may produce.

## `maxConcurrency` (type: `integer`):

How many queries to run at the same time. Lower it if the source throttles you.

## `includeRaw` (type: `boolean`):

Attach the source's untouched response under `raw`. Useful when you need a field this actor does not map.

## `requestDelayMs` (type: `integer`):

Politeness delay against a public source. Raise it for large runs.

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

Optional. ClinicalTrials.gov is an open federal API and rarely needs a proxy.

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

Limit to trials in one status. Leave empty for all.

## Actor input object example

```json
{
  "queries": [
    "Moderna",
    "Vertex Pharmaceuticals",
    "BioNTech"
  ],
  "maxResultsPerQuery": 25,
  "maxConcurrency": 3,
  "includeRaw": false,
  "requestDelayMs": 0,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "status": ""
}
```

# Actor output Schema

## `dataset` (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 = {
    "queries": [
        "Moderna",
        "Vertex Pharmaceuticals",
        "BioNTech"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("foxlabs/clinical-trial-sponsor-data").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 = { "queries": [
        "Moderna",
        "Vertex Pharmaceuticals",
        "BioNTech",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("foxlabs/clinical-trial-sponsor-data").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 '{
  "queries": [
    "Moderna",
    "Vertex Pharmaceuticals",
    "BioNTech"
  ]
}' |
apify call foxlabs/clinical-trial-sponsor-data --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,foxlabs/clinical-trial-sponsor-data"
        }
    }
}

```

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/6A8ypNO7V5I8Vt0pR/builds/PK8Y0dfmhcJvjbb6P/openapi.json