ClinicalTrials.gov Monitor - Studies, Status, Phases
Pricing
from $1.20 / 1,000 results
ClinicalTrials.gov Monitor - Studies, Status, Phases
Search and monitor ClinicalTrials.gov studies via the official v2 API. Filter by condition, status, phase or keyword. One clean row per study. No API key.
Pricing
from $1.20 / 1,000 results
Rating
0.0
(0)
Developer
Brandt May
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share

Study records for a focused cohort
Create a structured starting point for clinical research or biopharma intelligence from the official ClinicalTrials.gov v2 API. Each row is a registered study, with its identifier and official page link.
Open this Actor in Console · First run · Results · Cost · Full guide
Try this Actor
- Choose a small scope. Use the existing
diabetesquery prefill and maximum of twenty-five studies for the initial sample. Add condition, status or phase filters only when you want to narrow that query. - Run and review. Open the dataset's study table and the run's key-value-store
SUMMARY. Check source coverage and limits before treating a sample as a complete cohort. - Use the results. Export CSV for a study list or JSON for phase and condition arrays. Retain the NCT ID and official study link for follow-up review.
Read this before using the data: These are registry records, not an assessment of treatment effectiveness or individual eligibility. Phase and date fields may be absent. This version does not interpret eligibility criteria or results modules.
Result preview
The dataset view highlights these columns:
- NCT ID ·
nctId - Study title ·
briefTitle - Published study status ·
overallStatus - Phases ·
phases - Conditions ·
conditions - Study start date ·
startDate
Use the original source links and the field definitions below when interpreting the results. CSV works well for flat columns; JSON preserves nested values.
Usage and pricing
Base result rate on the FREE tier: $2 per 1,000 results. The Pricing tab shows your plan's result rate and any Actor Start charge. Set a small result limit for the first run; the requested limit is not a guarantee of that many results.
Full guide
Search and monitor ClinicalTrials.gov studies through the official API v2. No API key required.
What it does
Queries https://clinicaltrials.gov/api/v2/studies and returns one normalized row per study: NCT id, titles, overall status, phases, conditions, key dates, organization, and a source link.
Who it's for
- Clinical / medical affairs teams tracking competing trials
- Biopharma BD and competitive-intelligence analysts
- Researchers building trial cohorts by condition or phase
- Developers who want structured CT.gov data without maintaining query plumbing
Output
| Field | Description |
|---|---|
nctId | ClinicalTrials.gov identifier |
briefTitle / officialTitle | Study titles |
overallStatus | e.g. RECRUITING, COMPLETED |
phases | Phase list when present |
conditions | Condition list |
startDate / lastUpdatePostDate | Key dates |
organization | Lead organization name |
sourceUrl | Official study page |
Input
- Search query - free text (default demo:
diabeteswhen empty) - Condition - optional
query.cond - Statuses / Phases - optional filters
- Max results - default 25 (fast sample)
- Max run seconds - wall-clock budget (default 240)
Pricing note
Runs are billed per dataset row on Apify. New accounts can usually cover small default runs with monthly free credits.
Limitations
- Uses only the public v2 API; does not scrape the website HTML.
- Some studies omit phase or dates; those fields are null when absent.
- Does not interpret eligibility criteria or results modules in this version.
Result accounting
Only real source records are written to the dataset. SUMMARY.total counts saved rows. A dataset spending cap stops further writes and sets SUMMARY.stoppedOnChargeLimit and SUMMARY.incomplete. Source failures and time limits are reported in the summary; they do not generate substitute result rows.
Help with your run
Open the Issues tab on this Actor with the run URL, the input field that caused trouble and what you expected to receive. Remove API keys and private information before posting.
Understand your run
Open Run report in the run’s Output tab for saved-record counts, reported source issues and limits, and suggested next steps. Use CSV export to take the saved results into a spreadsheet. The existing JSON results and detailed machine-readable summary remain available.
The report reflects this run’s recorded coverage. A successful run or a saved result does not establish that every possible source record was collected.