ClinicalTrials.gov V2 Export

Export structured study records from the public ClinicalTrials.gov v2 API. This Apify actor is designed for biotech business-development teams, CRO analysts, clinical operations researchers, competitive intelligence teams, and data vendors who need clean trial metadata without building and maintaining their own API pagination, filtering, and normalization layer.

ClinicalTrials.gov study search by condition, intervention, phase, status, and location

The actor calls only HTTP-only public ClinicalTrials.gov v2 endpoints and does not require logins, proxies, cookies, or credentials. Search by condition, intervention, general keyword, and location, then narrow results with optional recruitment statuses, study phases, study types, and first-posted date ranges. Defaults are intentionally small so a trial run completes quickly, while maxResults can be increased for larger exports. The actor uses ClinicalTrials.gov pagination and honors maxResults exactly, truncating client-side if an API page contains more records than the requested cap.

What you get in each exported study record

Each output row is a normalized study record with the NCT ID, ClinicalTrials.gov URL, brief and official titles, acronym, overall status, last known status, results availability, key study dates, lead sponsor, collaborators, responsible party, condition list, keywords, study type, phases, enrollment, design details, interventions, arm groups, primary and secondary outcomes, eligibility criteria, age/sex fields, central contacts, officials, locations, countries, and ClinicalTrials.gov browse terms when provided by the API. The parser keeps nested details where they matter, such as contacts and site locations, while also adding convenient flat fields like leadSponsorName, interventionNames, locationCount, and countries for spreadsheets and lead lists.

Use cases for biotech BD and CRO analysts

Use this actor to find recruiting studies in a therapeutic area, monitor sponsor activity around a target drug, build site and country maps for feasibility research, create competitive landscapes by condition and phase, enrich CRM accounts with trial activity, or export structured trial feeds for dashboards and downstream analytics. Because it uses the official v2 API, it avoids brittle HTML scraping and preserves modern v2 fields that older scrapers often flatten poorly or miss entirely.

How to use

Start with the default input to export a small diabetes sample. Add an intervention such as pembrolizumab, set statuses to values like RECRUITING or ACTIVE_NOT_RECRUITING, add phases such as PHASE2 or PHASE3, and optionally provide a location such as United States or France. Increase maxResults when you are ready for a larger export. If you use a broad query, keep pageSize near the default until you confirm the result shape, then increase it to reduce the number of API calls.

Pricing

This actor uses Apify pay-per-event pricing. The single paid event is study-scraped at $0.02 per exported study record. There are no extra paid events for pages, errors, or nested locations. Local, free, or non-PPE runs are capped by the built-in free-run guard.

FAQ

Does this scrape ClinicalTrials.gov web pages?

No. It only calls the official public ClinicalTrials.gov v2 API at clinicaltrials.gov/api/v2/studies.

Do I need an API key?

No. The endpoint used by this actor is public and does not require authentication.

Are contacts included?

Yes, when ClinicalTrials.gov provides them. Central contacts, overall officials, and site-level contacts are normalized into structured fields. Contact availability varies by study and sponsor.

Can I export every trial in a disease area?

Yes, within Apify run limits and the maxResults you choose. The actor paginates through API pages until it reaches your exact cap, the API runs out of results, or spending/free-run limits stop the run.