ClinicalTrials.gov Study Feed
Pricing
from $20.00 / 1,000 study rows
ClinicalTrials.gov Study Feed
Queries the public ClinicalTrials.gov studies API by condition, intervention, or sponsor and emits one normalized row per study, with status, phase, sponsor, enrollment, and update dates.
Pricing
from $20.00 / 1,000 study rows
Rating
0.0
(0)
Developer
Jason Ramirez
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Features
Share
Export ClinicalTrials.gov data as clean, normalized rows. Search by condition, intervention or sponsor, filter by status and update window, and get one row per study with NCT ID, status, phase, sponsor and conditions.
An Apify Actor that queries the public ClinicalTrials.gov v2 studies API and emits one normalized dataset item per study. Intended for biotech and pharma intelligence teams, CROs, academic researchers, and recruiters sourcing trial sites.
At least one nonblank condition, intervention, or sponsor is required. Status and update windows further narrow the query. The default limit is 200 and the maximum is 5000. Pages request up to 1000 records.
Example input:
{"condition": "breast cancer","intervention": "pembrolizumab","statuses": ["RECRUITING", "NOT_YET_RECRUITING"],"updatedSinceDays": 30,"limit": 200}
Sponsor-only example: {"sponsor":"National Cancer Institute","limit":100}.
Omit updatedSinceDays or set it to null for no update window. Zero means today in UTC.
| Output field | Meaning |
|---|---|
| nctId | Registry identifier or null |
| title, officialTitle | Registry brief and official titles or null |
| sponsor | Lead sponsor name or null |
| collaborators | Collaborator names, possibly empty |
| status | Overall registry status or null |
| phase | Phases joined with comma and space, or null |
| conditions | Condition strings, possibly empty |
| interventions | Objects with name and type, each nullable |
| enrollment | Registry count or null; zero is preserved |
| startDate, completionDate, lastUpdatePosted | Registry date strings or null; partial dates retained |
| locationsSummary | Location count and up to five distinct country names |
| url | Study page URL or null if identifier absent |
| retrievedAt | Run timestamp in UTC |
| source | ClinicalTrials.gov |
LAST_RUN_SUMMARY contains runAt, filtersUsed, totalReportedByApi (nullable), emitted, complete, and notes. Zero matches is a successful empty run with a note. A later page failure preserves collected rows with complete false. An initial failure stores the summary then fails the Actor. Reaching the limit completes the requested bounded run, not necessarily the registry's full matching set.
Data is the registry's own and updates on its schedule. No missing values are inferred, no clinical interpretation is provided, and no patient eligibility or site recruiting accuracy is guaranteed. Location summaries do not include contact details. Dates retain the precision supplied by the registry. No retries or cross-run deduplication are implemented. Rows are buffered up to the limit before writing to the dataset. Storage failures propagate from the SDK.
The update window uses filter.advanced=AREA[LastUpdatePostDate]RANGE[YYYY-MM-DD,MAX]. Its live acceptance has not been verified in this offline build. Other query fields are query.cond, query.intr, query.spons, and filter.overallStatus. Synthetic fixtures exercise the v2 protocolSection shape; they are not live registry records.
Local run
Requires Node.js 20 or later. From this directory run npm install, put input JSON in storage/key_value_stores/default/INPUT.json, then run npm start. Installation and live runs need network access; the public API requires no key. Run npm test for offline tests, which inject fake fetch and require no installed SDK.
The Dockerfile installs the SDK and starts the Actor. Publication, live API verification, and pay-per-event per-row pricing configuration are owner steps. This build defines no prices and does not configure billing events. No publication or deployment is performed here.