Clinical Trial Multi-Source Scraper
Pricing
$21.00 / 1,000 result items
Clinical Trial Multi-Source Scraper
Scrapes clinical trial records from ClinicalTrials.gov, WHO ICTRP, OpenFDA, and ClinVar. Returns each trial as a flat row with registry ID, phase, status, enrollment, and eligibility criteria.
Pricing
$21.00 / 1,000 result items
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Share
Clinical Trial Multi-Source Scraper
Scrape clinical trials from ClinicalTrials.gov, WHO ICTRP, OpenFDA, and ClinVar in one run. Every trial comes with its registry ID, phase, status, enrollment, and full eligibility criteria. No API keys or logins. Export to CSV, JSON, Excel, or XML.
Clinical trial data is scattered across registries, each with its own search interface and export limits. This Actor queries ClinicalTrials.gov, WHO ICTRP, OpenFDA, and ClinVar in parallel for any condition, drug, or keyword, and returns every matching trial in one flat schema. It is built for researchers, pharma analysts, and anyone who needs a clean, deduplicated view of global trial activity.
| Who uses it | What they scrape ClinicalTrials.gov, WHO ICTRP, OpenFDA, and ClinVar for |
|---|---|
| Pharma competitive intelligence teams | Track competitor pipelines and trial milestones across registries |
| Academic researchers | Build systematic review datasets from multiple trial sources |
| Patient advocacy groups | Find recruiting trials for a specific condition |
| Regulatory consultants | Monitor trial status changes and safety signals |
What it does
This Actor collects clinical trial records from four public registries and returns each trial as a flat row with registry ID, phase, status, enrollment, and eligibility criteria.
- ๐ Multi-source search: query ClinicalTrials.gov, WHO ICTRP, OpenFDA, and ClinVar with one keyword
- ๐ Flat schema: every trial is returned as a single row with consistent fields
- โก Parallel fetching: all sources are queried at once, not one after another
- ๐ฆ Bulk export: download up to 1,000,000 trials per run as CSV, JSON, Excel, or XML
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with ClinicalTrials.gov, WHO ICTRP, OpenFDA, and ClinVar data
๐ Track competitor pipelines.
A pharma analyst runs the Actor weekly with a competitor's drug name to see new trial registrations, phase changes, and status updates across all four sources.
๐ฌ Build systematic review datasets.
A university researcher queries a condition like 'BRCA1' and exports all matching trials from ClinicalTrials.gov and WHO ICTRP into a single CSV for screening.
๐งช Monitor safety signals.
A regulatory consultant runs the Actor with a drug name and reviews OpenFDA adverse event data alongside trial records to spot emerging safety concerns.
๐ Find global trials for patients.
A patient advocacy group searches for 'ebola' and gets recruiting trials from WHO ICTRP and ClinicalTrials.gov, including sites in low-income countries.
Why choose this scraper
| What you get | |
|---|---|
| One query, four registries | Search ClinicalTrials.gov, WHO ICTRP, OpenFDA, and ClinVar at the same time |
| No API keys or logins | The Actor reads public registry data directly, no registration needed |
| Consistent output | Every trial is returned in the same flat schema, regardless of source |
| Scalable | Collect up to 1,000,000 trials per run |
How it compares
This Actor covers four registries in one run, while the Clinical Trials FDA Scraper focuses on ClinicalTrials.gov and OpenFDA with additional FDA data types.
| Feature | ParseForge | Clinical Trials FDA Scraper |
|---|---|---|
| Searches ClinicalTrials.gov | Yes | Yes |
| Searches WHO ICTRP | Yes | Not listed |
| Searches ClinVar | Yes | Not listed |
| Adverse event data from OpenFDA | Yes | Yes |
| Search by NCT ID | Not listed | Yes |
| Drug labels and recalls | Not listed | Yes |
Configure the run
Drive the Actor with a condition, drug, or keyword, choose which of the four sources to query, and set a maximum number of trials per run. The Input tab lists every parameter.
A first run with the defaults:
{"maxItems": 10}
A larger pull:
{"maxItems": 200}
Pricing
Pay-per-result: $0.021 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $2.10 |
| 1,000 results | $21.00 |
| 10,000 results | $210.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the Clinical Trial Multi-Source Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to ClinicalTrials.gov, WHO ICTRP, OpenFDA, and ClinVar through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/clinical-trial-multi-source-scraper"
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Check that your query is spelled correctly and that at least one source is selected. Some sources may not support certain keywords. Try a broader term like 'cancer' to test.
Why is the run slow?
The Actor queries multiple sources in parallel, but some registries have rate limits. Reduce the number of sources or lower maxItems to speed up the run.
Why are some fields empty?
Not all registries provide the same level of detail. For example, WHO ICTRP may not include adverse events. Empty fields mean the source did not have that data.
Can I get more than 1,000,000 trials?
The maximum is 1,000,000 per run. If you need more, split your query into smaller chunks or run the Actor multiple times with different keywords.
FAQ
| Question | Answer |
|---|---|
| Which registries does this Actor search? | It queries ClinicalTrials.gov, WHO ICTRP, OpenFDA, and ClinVar. You can select any subset of these sources in the input. |
| Do I need an API key or login? | No. The Actor reads public registry data directly, so no API keys or authentication are required. |
| What is the maximum number of trials I can collect? | You can set maxItems up to 1,000,000 trials per run. The default is 10. |
| Can I search by NCT ID? | The Actor searches by keyword, condition, or drug. If you enter an NCT ID as the query, it will match trials that contain that ID in their metadata. |
| What output formats are supported? | You can export results as CSV, JSON, Excel, or XML from the Apify dataset. |
| How are duplicate trials handled? | The Actor does not deduplicate across sources. If the same trial appears in multiple registries, it will be returned once per source. |
| Can I schedule this Actor to run automatically? | Yes, you can set up a schedule in Apify to run the Actor daily, weekly, or at any interval. |
| Does this Actor include adverse event data? | Yes, when you select OpenFDA as a source, the Actor returns adverse event reports associated with the query. |
| Is the data updated in real time? | The Actor fetches data live from each registry at the time of the run, so you get the most current records available. |
| Can I filter by trial phase or status? | The input schema does not include phase or status filters. You can filter the results after export using the phase and status fields in the dataset. |
Related actors
Browse the full ParseForge collection for more scrapers.
๐ Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
โ ๏ธ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by U.S. National Library of Medicine, World Health Organization, U.S. Food and Drug Administration, and National Center for Biotechnology Information. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
