ClinicalTrials.gov Scraper - Trials, Sites & Sponsor Leads avatar

ClinicalTrials.gov Scraper - Trials, Sites & Sponsor Leads

Pricing

from $4.00 / 1,000 trial scrapeds

Go to Apify Store
ClinicalTrials.gov Scraper - Trials, Sites & Sponsor Leads

ClinicalTrials.gov Scraper - Trials, Sites & Sponsor Leads

Scrape ClinicalTrials.gov by condition, drug, sponsor, phase, status or location. Rich trial records, research-site & investigator contact leads, and sponsor pipeline analytics. Keyless, no browser, monitor mode. Independent tool, not affiliated with any government agency.

Pricing

from $4.00 / 1,000 trial scrapeds

Rating

0.0

(0)

Developer

Scrape Sage

Scrape Sage

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

ClinicalTrials.gov Scraper — Trials, Site Leads & Sponsor Pipeline

Disclaimer: This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by the U.S. National Library of Medicine (NIH) or any government body. All trademarks mentioned are the property of their respective owners. "ClinicalTrials.gov" is referenced only to describe the public data source this Actor collects from.

Extract complete clinical-trial data from ClinicalTrials.gov — the world's largest trial registry (500,000+ studies from 220+ countries). Search by condition, drug, sponsor, phase, status or location and get the richest dataset in the category: full study details, sponsors and collaborators, interventions, eligibility, outcome measures, every research site with investigator contact name, phone and email, and ready-made sponsor pipeline analytics.

No login, no cookies, no browser, no API key — fast JSON extraction straight from the official ClinicalTrials.gov v2 API, with a built-in monitor mode that returns only new or updated trials on each run.

Why this ClinicalTrials.gov scraper?

Most clinical-trial scrapers return a thin row — title, status, a couple of IDs — and stop. This actor flattens every protocol module into one dense record, turns each trial into contactable research-site leads, and rolls trials up into per-sponsor pipeline intelligence.

DataTypical scrapersThis actor
Title, status, phase, study type
Lead sponsor + collaborators + sponsor classpartial
Interventions (drug/device) + arms
Primary & secondary outcome measures
Full eligibility criteria, sex, age, healthy-volunteer flagpartial
Every research site: facility, city, geo (lat/lng)partial
Site contact name, role, phone & email
Principal investigator / overall official
Lead score per site (0–100)
MeSH-mapped conditions & interventions
Posted results (outcomes, adverse-event totals)✅ opt-in
Sponsor pipeline analytics (counts by phase/status, top drugs/conditions)
Monitor mode — only new/updated trials

Use cases

  • Patient recruitment & site outreach — find trials that are recruiting now in a condition and country, then export every site with its contact name, phone and email and a lead score. The fastest way to build a research-site / investigator contact list.
  • Pharma & biotech competitive intelligence — track a competitor's pipeline with the Sponsor pipeline output: how many trials they run, by phase and status, in which conditions, with which drugs, and what changed since last week.
  • CRO & clinical-vendor lead generation — sponsors and sites running active trials are in-market buyers for CRO, imaging, lab, eCOA, and recruitment services. Filter by Industry lead sponsor and recruiting status.
  • Investor & market research — monitor drug-development programs, enrollment sizes, phase transitions and completion dates across an entire indication.
  • Trial-matching & patient apps — feed structured, geo-coded trial and eligibility data into trial-finder tools.
  • Regulatory & medical-affairs monitoring — watch a condition or sponsor for newly posted or updated studies and results.

How to use

  1. Sign up for Apify — the free plan is enough to try this actor.
  2. Open the ClinicalTrials.gov Scraper, enter a condition (and optionally a drug, sponsor, phase, status or country), and pick an Output type.
  3. Click Start and watch results stream into the dataset table.
  4. Export as JSON, CSV, Excel, XML or RSS — or pull results programmatically via the Apify API.

Input

{
"outputType": "siteLeads",
"condition": "breast cancer",
"intervention": "pembrolizumab",
"status": ["RECRUITING", "NOT_YET_RECRUITING"],
"phases": ["PHASE2", "PHASE3"],
"locationCountry": "United States",
"funderTypes": ["INDUSTRY"],
"maxResults": 500
}
  • outputTypetrials (rich study records, default), siteLeads (one contactable research-site lead per site), or sponsors (per-lead-sponsor pipeline analytics).
  • condition / intervention / otherTerms / sponsor / titleSearch — search fields (condition/disease, drug or device, free-text keywords, sponsor or collaborator, title).
  • nctIds — scrape exact studies by NCT number; full detail including the results section is fetched for each.
  • searchUrls — paste clinicaltrials.gov search or study URLs; filters in the URL (cond, intr, aggFilters=status:rec,phase:2, country, …) are converted automatically.
  • status / phases / studyType / funderTypes / resultsAvailability / sex / ages / healthyVolunteersOnly — filters.
  • locationCountry / locationState / locationCity / locationTerm, or geoLatitude + geoLongitude + geoRadius — location filters.
  • studyStartDateFrom/To, lastUpdateDateFrom/To, sortBy — dates & ordering (sort by relevance, most-recently-updated, most-recently-posted, largest enrollment, start date).
  • includeResults (default false) — attach a resultsSummary (outcome measures, participant flow, adverse-event totals) for trials that have posted results.
  • includeDetailedDescription / includeEligibilityText (default true) — keep or drop the long free-text fields.
  • monitorMode (default false) + monitorKey — remember records across runs and output only new/changed ones.

Output

One record per trial (type: "trial"), per site lead (type: "siteLead"), or per sponsor (type: "sponsor").

A trial record (abridged):

{
"type": "trial",
"nctId": "NCT06970288",
"url": "https://clinicaltrials.gov/study/NCT06970288",
"briefTitle": "A Study of Drug X in Patients With Advanced Breast Cancer",
"overallStatus": "Recruiting",
"phase": "Phase 2/Phase 3",
"studyType": "Interventional",
"leadSponsor": "Acme Therapeutics",
"leadSponsorClass": "Industry",
"collaboratorNames": ["University Cancer Center"],
"conditions": ["Breast Cancer", "HER2-positive Breast Cancer"],
"interventionNames": ["Drug X", "Trastuzumab"],
"enrollmentCount": 320,
"startDate": "2026-01-15",
"primaryCompletionDate": "2027-12-01",
"lastUpdatePostDate": "2026-06-17",
"minimumAge": "18 Years",
"sex": "All",
"primaryOutcomes": [{ "measure": "Progression-free survival", "timeFrame": "24 months" }],
"locationCount": 18,
"countries": ["United States", "Canada"],
"primaryContactName": "Jane Doe, RN",
"primaryContactEmail": "trials@acmetx.com",
"primaryContactPhone": "+1 617 555 0199",
"hasResults": false,
"scrapedAt": "2026-06-17T13:00:00.000Z"
}

A siteLead record:

{
"type": "siteLead",
"nctId": "NCT06970288",
"briefTitle": "A Study of Drug X in Patients With Advanced Breast Cancer",
"overallStatus": "Recruiting",
"phase": "Phase 2/Phase 3",
"leadSponsor": "Acme Therapeutics",
"facility": "Memorial Cancer Institute",
"city": "Boston",
"state": "Massachusetts",
"country": "United States",
"latitude": 42.3601,
"longitude": -71.0589,
"contactName": "Jane Doe, RN",
"contactRole": "Contact",
"contactPhone": "+1 617 555 0199",
"contactEmail": "jane.doe@mci.org",
"principalInvestigator": "Dr. Alan Smith",
"leadScore": 94,
"scrapedAt": "2026-06-17T13:00:00.000Z"
}

A sponsor record carries sponsorName, sponsorClass, totalTrials, recruitingCount/activeCount/completedCount, byPhase, byStatus, totalEnrollment, topConditions, topInterventions, countries, lastUpdatePostDate and a recentTrials array.

What to expect (field coverage)

ClinicalTrials.gov is sponsor-entered data, so some fields are populated only when the sponsor filled them in. Across the registry you can typically expect:

Field groupCoverage
Title, status, sponsor, conditions, study type~100%
Phase~100% of interventional trials (observational trials have no phase)
Interventions, eligibility, outcomes~90–100%
Site list with geo~95% of trials with locations
Site / central contact emailmostly on recruiting / not-yet-recruiting trials — completed trials usually drop contacts
Posted resultsonly trials that have submitted results (hasResults: true)

A blank field means the sponsor didn't publish it — never that scraping failed. Nothing is dropped, so you always get the richest record available.

How much does it cost to scrape ClinicalTrials.gov?

This Actor uses Apify's pay-per-event pricing: you are charged only for the results it delivers, with no monthly rental and no start fee. The events it can charge are:

  • Trial scraped - One clinical trial record: title, status, phase, sponsor, conditions, interventions, eligibility, outcomes, sites and contacts.
  • Site / investigator lead scraped - One contactable research-site lead: facility, location, contact name/role/phone/email, principal investigator, sponsor, trial context and lead score.
  • Sponsor pipeline record scraped - One lead-sponsor analytics record: trial counts by phase & status, total enrollment, top conditions/interventions, countries and recent trials.

The current price of each event is shown on the Pricing tab of this page. Set a maximum total charge on the run if you want a hard cap on spend, and use the input limits to control how much the Actor fetches.

Automate & schedule

Run this actor on autopilot and pull results into your own stack:

  • Apify API — start runs, fetch datasets, and manage schedules over REST.
  • apify-client for JavaScript and apify-client for Python — official SDKs.
  • Schedules — run it daily/weekly to capture newly posted or updated trials in a condition, country, or for a specific sponsor. Combine with monitor mode so each run returns only what changed.
  • Webhooks — trigger downstream actions (CRM import, Slack alert, email sequence) the moment a run finishes.
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });
const run = await client.actor('scrapesage/clinical-trials-scraper').call({
outputType: 'siteLeads',
condition: 'breast cancer',
status: ['RECRUITING'],
locationCountry: 'United States',
maxResults: 500,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} research-site leads`);

Integrate with any app

Connect the dataset to 5,000+ apps — no code required:

  • Make — multi-step automation scenarios.
  • Zapier — push new site leads straight into your CRM.
  • Slack — get notified when a monitored search finds new trials.
  • Google Drive / Sheets — auto-export every run to a spreadsheet.
  • Airbyte — pipe results into your data warehouse.
  • GitHub — trigger runs from commits or releases.

Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. Call this actor from Claude, ChatGPT, or any agent framework through the Apify MCP server — ask your assistant to "find recruiting Phase 3 oncology trials in California and list the site contacts" and let it run this scraper for you.

Agent-ready: autonomous payments (x402 & Skyfire)

This actor is agent-ready — AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:

  • x402 — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server — no account, no API key.
  • Skyfire — agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

More scrapers from scrapesage

Build a complete healthcare & life-sciences data stack:

Tips

  • Recruiting only: set status to RECRUITING (and NOT_YET_RECRUITING) for the freshest, most contactable site leads — completed trials usually have their contacts removed.
  • Pipeline intelligence: use outputType: "sponsors" with a condition or sponsor query and raise maxTrialsToScan to aggregate a fuller picture.
  • Incremental monitoring: turn on monitorMode, sort by lastUpdate, and schedule the run — you'll only get trials that are new or changed since last time.
  • Big indications: filter by phases, locationCountry or a lastUpdateDateFrom window to keep result sets focused.
  • Proxies: the default Apify datacenter proxy is plenty — the API is clean and keyless.

FAQ

Where does the data come from? The official ClinicalTrials.gov API v2 — the U.S. National Library of Medicine's public trial registry. No API key or login is required.

Can I get investigator emails and phone numbers? Yes — for trials that publish them (most recruiting trials do), each site's contact name, role, phone and email are included, along with the principal investigator. Completed trials usually have contacts removed by the sponsor.

How do I scrape trials for a specific condition and country? Put the disease in condition and the country in locationCountry (e.g. United States). Add status: ["RECRUITING"] for active trials only.

Can I export to Google Sheets, CSV or Excel? Yes — one click in the dataset view, or automatically on every run via the Google Drive integration.

How do I monitor for new trials? Turn on monitorMode, create a Schedule, and optionally add a webhook. Each run outputs only new or updated studies. Monitor mode uses its own storage and does not interfere with the schedule.

A field is empty — why? Some sponsors don't publish a detailed description, outcomes, or site contacts. Fields are blank only when the data doesn't exist in the registry, not because the scraper skipped them.

Is scraping ClinicalTrials.gov legal? This actor reads publicly available U.S. government data through the official public API. You are responsible for using the data in compliance with applicable laws (e.g. GDPR/CCPA where personal data such as investigator contacts is involved) and the ClinicalTrials.gov terms.

Data & lawful use

The source is an official public register, published so that anyone can consult it. Records can name individuals (investigators and study contacts), so the output may contain personal data even though it is public. If you are in the EU or UK you are the data controller for what you do with it: have a lawful basis, honour access and deletion requests, and respect the register's own reuse conditions, which can restrict marketing or commercial use.

Under Apify's Standard Actor Contract, which governs your use of this Actor, you are the controller of any personal data in your input and output and scrapesage acts only as your processor: that data is processed solely to run your job, written only to your own Apify storage, never used for any other purpose and never shared onward. If you need help with a data-subject request that involves this Actor's output, open an issue on the Issues tab.

Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by the U.S. National Library of Medicine (NIH) or any government body. All trademarks mentioned are the property of their respective owners.

"ClinicalTrials.gov" is referenced only in a descriptive, nominative sense - to identify the public data source this Actor collects from. This Actor is not an official product or service of the U.S. National Library of Medicine (NIH) and is not authorised or certified by it. It collects only publicly available records; you are responsible for ensuring your use of that data complies with applicable laws, regulations and the source's own terms of use or reuse conditions.

Need help?

Open an issue on the actor's Issues tab, or visit the Apify help center. Feature requests are welcome — this actor is actively maintained.