Medrio API
Medrio exposes three REST surfaces: the Connect API with public Swagger docs, the mSource API (v1 and v2) for eCOA capture, and a legacy export API behind the customer portal. Auth is OAuth 2.0, but production access requires customer or partner enablement rather than self serve signup.
Frequently asked questions
Medrio scores D+ on the API Report Card. Medrio exposes three REST surfaces: the Connect API with public Swagger docs, the mSource API (v1 and v2) for eCOA capture, and a legacy export API behind the customer portal. Auth is OAuth 2.0, but production access requires customer or partner enablement rather than self serve signup.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
Medrio is a cloud-based eClinical software vendor that sells a modular suite for running clinical trials end-to-end.
Primary vertical: Healthcare. Closest Supergood sub-vertical: Healthcare/EHR (specifically eClinical / EDC, the regulated system of record for clinical-trial source data and case report forms). A small biotech or device sponsor licenses Medrio CDMS/EDC for a Phase I/II or pivotal study and uses the no-code study builder to design case report forms (CRFs), edit checks, and visit schedules; site coordinators and CRAs log into the web app to enter, query, and source-data-verify subject data; data managers run cleaning queries and lock the database at study end for the Statistical Analysis Plan and the eCTD submission.
6/10 within US clinical trials, lower outside life sciences. Medrio is one of the most-named EDC platforms for small-to-mid biotech and device trials and is regularly listed alongside Castor, Veeva Vault EDC, Medidata Rave, and Oracle Clinical One in 2026 EDC buyer's guides.
Yes, Medrio is the regulated system of record for clinical-trial source data during a study and is the source of the database lock that feeds the Statistical Analysis Plan and the FDA/EMA submission.
Medrio was founded in 2005 by Mike Novotny, who built the original product in his San Francisco apartment to give small CROs and sponsors an affordable, web-based alternative to legacy enterprise EDCs (Medidata Rave, Oracle InForm).
API access is gated through partner / Professional Services enablement; there is no fully self-serve public developer signup at the level of Castor or open SaaS APIs. The mSource API requires the X-Medrio-ClientInfo header (with app name, build version, install ID) on every call; missing/malformed headers reject the request and clients must implement install-ID generation and persistence. Full sourced list under Sources below.
Common alternatives include Medidata Rave (Dassault Systemes), Veeva Vault EDC / CDMS, Oracle Clinical One / Siebel / InForm, Castor EDC, Clario (eCOA/imaging + EDC), Viedoc. Graded alternatives appear under "More from the report card" below.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.