The clinical trials API searches ClinicalTrials.gov — the US NIH registry — and flattens each study's deeply-nested record into a single row. One study becomes its NCT id, brief title, recruitment status, phase, study type, the conditions and interventions as lists, the lead sponsor, planned enrollment, start and completion dates, whether results are posted, and the study URL.
You filter by free-text query, by condition, by recruitment status, or any combination. The registry's v2 API returns richly nested JSON modules; the value here is that they arrive already flattened into typed columns you can load straight into a dataframe. Each search is fetched over our TLS tier through a residential exit — no browser, one uniform row shape. Sponsor and condition strings can be normalised to stable identifiers with the Wikidata API alongside it.
$0.0005 per delivered study, up to 200 studys per run. Nothing delivered means nothing charged.
You post one or more filters and the collector queries the ClinicalTrials.gov v2 endpoint, then unpacks each study's protocol modules into a flat row. There is no browser and no key in the path.
query is free text across the record — a drug, a disease, a sponsor — while condition restricts to a medical condition and status to a recruitment state such as RECRUITING or COMPLETED.phases, conditions, interventions) on one row.has_results tells you whether results are posted; the collector returns the study record and its URL, not the results tables themselves.Runs of 30 studies or fewer return inline; larger pulls up to the 200-study ceiling are queued and returned on completion.
All three filters are optional and combine: query for free text, condition for a medical condition and status for a recruitment state; max_results caps the run at up to 200 studies.
Each study is one row: nct_id, title, status, phases, study_type, conditions and interventions as lists, sponsor, enrollment, start_date, completion_date, the has_results flag and the study url.
$0.0005 per delivered study ($0.50 per 1,000). Nothing delivered means nothing charged, and the $2 monthly free credit covers roughly 4,000 studys here. Volume tiers take up to 30% off.
$0.0005 per delivered study — 50 cents per 1,000 rows. Sweeping every recruiting trial for a condition, or snapshotting a therapeutic area to track quarter over quarter, costs cents rather than a data-licence negotiation.
Searches that match nothing return no rows and cost nothing, so an over-specific filter wastes a query, not money.
ClinicalTrials.gov's v2 API is free, keyless and genuinely good — the friction is its shape, not its access. Each study is a tree of protocol modules (identification, status, design, arms, sponsor) and the fields most analyses want are scattered across them, so every consumer writes the same flattening code and handles the same pagination.
This collector is that flattening, done once and kept current, returning a stable columnar row instead of a nested document. It is not a route around anything the registry restricts — the registry restricts nothing — it is the difference between raw modules and a table you can query, delivered through rotating exits so bulk pulls stay smooth.
A first ClinicalTrials.gov integration is quick; a robust one absorbs the edge cases. Studies omit fields, phases come as arrays that are sometimes empty, interventions nest differently across study types, and the v2 pagination has to be walked correctly to avoid silent truncation. Every team that reads this registry rebuilds the same normaliser.
Using the collector means that normaliser is ours to maintain and your bill tracks delivered studies. If you would rather own the fetch and only need reliable network exits under it, our residential proxies are that layer.
Track every trial naming a drug, target or sponsor and watch new studies, status changes and phase progression across a therapeutic area over time.
Filter to RECRUITING studies for a condition to see who is enrolling, at what planned size and on what timeline, sponsor and dates included.
Pull a clean, columnar set of studies for a condition — NCT ids, phases, enrollment and result flags — as a reproducible starting corpus rather than hand-scraped records.
This returns the registry's study-level record, not trial results data: has_results is a flag, and detailed outcome measures, adverse-event tables and full protocols are not flattened into the row — follow the study url for those. Coverage and accuracy are exactly what sponsors registered with ClinicalTrials.gov, which is US-centric and self-reported; the registry does not include everything running elsewhere in the world.
One run caps at 200 studies; broader areas are more runs across narrower filters. This is public registry data for research and intelligence, and it is not medical advice.
ClinicalTrials.gov's v2 API is free and keyless. Here light use falls under the $2-a-month free allowance — about 4,000 studies at $0.0005 each — then pay-as-you-go with no subscription.
It reads the ClinicalTrials.gov v2 API and flattens each study's nested modules into one typed row, so you get the registry's data in a columnar shape without writing the module-unpacking code yourself.
Not for the registry — it is keyless — and not a second credential here. You authenticate only with your QuantumProxies key, the same key every other collector uses.
No. It returns the study record — status, phase, conditions, interventions, sponsor, enrollment, dates — and a has_results flag. Detailed outcome and adverse-event tables live on the study page at the returned url.