Medrio

Medrio is an eClinical / electronic data capture (EDC) platform built for small and scaling life sciences teams, spanning EDC, ePRO/eCOA, eConsent, and RTSM for clinical trials across pharma, biotech, medtech, and diagnostics. Medrio exposes documented REST APIs for integration and data exchange. Medrio API Connect (connectapi.medrio.com) covers study configuration, subject enrollment and identifiers, eCRF form data entry, user and membership administration, reference data (sites, roles, groups, subject statuses), and event subscriptions; it ships a live OpenAPI 3.0 description and Swagger UI. The mSource API (esource.medrio.com) backs the mPRO and mCapture eCOA/ePRO applications for subject-, form-, and approval-level source data capture, including offline access. Both surfaces are request/response REST over HTTPS secured with OAuth 2.0; actual use is gated to Medrio customers with study credentials, and commercial pricing is per-study / contact-sales.

Medrio is listed with 6 APIs on the APIs.io network, including Studies API, Subjects API, Data Entry API, and 3 more. Tagged areas include Clinical Trials, Electronic Data Capture, EDC, eClinical, and ePRO.

Medrio’s developer surface includes engineering blog, documentation, API reference, signup flow, and 8 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

16.9/100 emerging ▬ flat Agent 14/100 agent aware Front door AI 3/6 light Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessPaid

6 APIs

Clinical Trials Electronic Data Capture EDC eClinicalePROeCOAClinical Data Life Sciences Healthcare

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 16.9/100 · emerging

Contract Quality 5.1 / 21

Developer Ergonomics 3.2 / 17

Access Clarity 0.7 / 17

Operational Transparency 0.8 / 11

Contract Governance 0.0 / 10

Discoverability 6.1 / 9

Regulatory Posture 0.0 / 15

Agent readiness — 14/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/medrio/"><img src="https://apis.io/badge/medrio/card.svg" alt="Medrio on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey) Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →

11 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 4.3 — up to +19.1 composite points Ask about this →
Contract Quality scores 24.0 — up to +19.0 composite points Ask about this →
Developer Ergonomics scores 19.0 — up to +16.2 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/medrio/apis.yml: open an issue on github.com/api-evangelist/medrio to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

Medrio Studies API

List the studies available to your account and read their configuration - domains, enabled features, reason-for-data-change options, and the reference data a study is built from...

Medrio Subjects API

Create, list, and update clinical trial subjects within a study; manage Medrio and study subject identifiers (including their ePRO variants), activate or deactivate subjects, an...

Medrio Data Entry API

Read and write electronic case report form (eCRF) data - list a subject's visits, create subject visits from a template, submit and update data entry at the study or form/visit ...

Medrio Users and Memberships API

Administer the account user profile and per-study memberships - read and update your user, change password, list study users, add users to a study, assign or remove roles and si...

Medrio Subscriptions API

Configure event subscriptions for a study - read the available events configuration, then create, list, update, and delete subscriptions so downstream systems are notified of st...

Medrio mSource API

The V2 REST API behind Medrio's mSource eCOA/ePRO applications (mPRO and mCapture) - read study configuration, files, and users; read and write subject, form, and approval data ...

Medrio API pricing

Not yet checked against Medrio's own pricing page. Compiled by API Evangelist on 2026-07-05 from medrio.com; confirm before you rely on a figure.

Plan	Price
Medrio Study Subscription (Contact Sales) enterprise	—

Plan details, limits and sources →

Rate limits

API Connect Requests: not published requests
mSource API Requests: not published requests
Study Scope: per subscription access

Compiled by API Evangelist, not yet checked against Medrio's documentation. Rate-limit details →

Pricing Plans 1

Published pricing tiers and plan structures.

Medrio Plans Pricing

1 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Medrio Rate Limits

3 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Medrio Finops

FINOPS

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Medrio Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp

SignUp

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

OpenAPI

OpenAPI

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 4

The organization behind the API

Blog

Blog

BlogRSS

BlogRSS

Website

Website

LinkedIn

Source (apis.yml)

aid: medrio
url: https://raw.githubusercontent.com/api-evangelist/medrio/refs/heads/main/apis.yml
name: Medrio
kind: company
description: Medrio is an eClinical / electronic data capture (EDC) platform built for small and scaling life sciences teams,
  spanning EDC, ePRO/eCOA, eConsent, and RTSM for clinical trials across pharma, biotech, medtech, and diagnostics. Medrio
  exposes documented REST APIs for integration and data exchange. Medrio API Connect (connectapi.medrio.com) covers study
  configuration, subject enrollment and identifiers, eCRF form data entry, user and membership administration, reference data
  (sites, roles, groups, subject statuses), and event subscriptions; it ships a live OpenAPI 3.0 description and Swagger UI.
  The mSource API (esource.medrio.com) backs the mPRO and mCapture eCOA/ePRO applications for subject-, form-, and approval-level
  source data capture, including offline access. Both surfaces are request/response REST over HTTPS secured with OAuth 2.0;
  actual use is gated to Medrio customers with study credentials, and commercial pricing is per-study / contact-sales.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: low
  source:
  - plans
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/medrio.png
tags:
- Clinical Trials
- Electronic Data Capture
- EDC
- eClinical
- ePRO
- eCOA
- Clinical Data
- Life Sciences
- Healthcare
created: '2026-07-05'
modified: '2026-10-06'
specificationVersion: '0.23'
apis:
- aid: medrio:medrio-studies-api
  name: Medrio Studies API
  tags:
  - Studies
  - Configuration
  - Sites
  - Roles
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://connectapi.medrio.com/swagger/index.html
  baseURL: https://connectapi.medrio.com
  properties:
  - url: https://connectapi.medrio.com/swagger/index.html
    type: APIReference
  - url: https://connectapi.medrio.com/swagger/v1/swagger.json
    type: OpenAPI
  description: List the studies available to your account and read their configuration - domains, enabled features, reason-for-data-change
    options, and the reference data a study is built from (sites, roles, groups, and subject statuses). The read surface that
    integrations use to understand a study before writing subjects or data.
- aid: medrio:medrio-subjects-api
  name: Medrio Subjects API
  tags:
  - Subjects
  - Enrollment
  - Identifiers
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://connectapi.medrio.com/swagger/index.html
  baseURL: https://connectapi.medrio.com
  properties:
  - url: https://connectapi.medrio.com/swagger/index.html
    type: APIReference
  - url: https://connectapi.medrio.com/swagger/v1/swagger.json
    type: OpenAPI
  description: Create, list, and update clinical trial subjects within a study; manage Medrio and study subject identifiers
    (including their ePRO variants), activate or deactivate subjects, and list deleted subjects. The enrollment and participant
    roster surface of Medrio EDC.
- aid: medrio:medrio-data-entry-api
  name: Medrio Data Entry API
  tags:
  - Data Entry
  - eCRF
  - Forms
  - Records
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://connectapi.medrio.com/swagger/index.html
  baseURL: https://connectapi.medrio.com
  properties:
  - url: https://connectapi.medrio.com/swagger/index.html
    type: APIReference
  - url: https://connectapi.medrio.com/swagger/v1/swagger.json
    type: OpenAPI
  description: Read and write electronic case report form (eCRF) data - list a subject's visits, create subject visits from
    a template, submit and update data entry at the study or form/visit level, and clear a form. The clinical data capture
    core of Medrio EDC.
- aid: medrio:medrio-users-memberships-api
  name: Medrio Users and Memberships API
  tags:
  - User
  - Membership
  - Roles
  - Access
  tags_raw:
  - Users
  - Memberships
  - Roles
  - Access
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://connectapi.medrio.com/swagger/index.html
  baseURL: https://connectapi.medrio.com
  properties:
  - url: https://connectapi.medrio.com/swagger/index.html
    type: APIReference
  - url: https://connectapi.medrio.com/swagger/v1/swagger.json
    type: OpenAPI
  description: Administer the account user profile and per-study memberships - read and update your user, change password,
    list study users, add users to a study, assign or remove roles and site access, and remove a user from a study. The identity
    and access surface for study teams.
- aid: medrio:medrio-subscriptions-api
  name: Medrio Subscriptions API
  tags:
  - Subscription
  - Event
  - Webhook
  - Notification
  tags_raw:
  - Subscriptions
  - Events
  - Webhooks
  - Notifications
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://connectapi.medrio.com/swagger/index.html
  baseURL: https://connectapi.medrio.com
  properties:
  - url: https://connectapi.medrio.com/swagger/index.html
    type: APIReference
  - url: https://connectapi.medrio.com/swagger/v1/swagger.json
    type: OpenAPI
  description: Configure event subscriptions for a study - read the available events configuration, then create, list, update,
    and delete subscriptions so downstream systems are notified of study events. The push/notification surface for keeping
    integrations in sync with Medrio data.
- aid: medrio:medrio-msource-api
  name: Medrio mSource API
  tags:
  - mSource
  - ePRO
  - eCOA
  - Source Data
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://esource.medrio.com/Help
  baseURL: https://esource.medrio.com
  properties:
  - url: https://esource.medrio.com/Help
    type: APIReference
  - url: https://esource.medrio.com/Help?apiVersion=1
    type: Documentation
  description: The V2 REST API behind Medrio's mSource eCOA/ePRO applications (mPRO and mCapture) - read study configuration,
    files, and users; read and write subject, form, and approval data with an asynchronous key-based query pattern; and post
    offline access, audit trail, and diagnostic logs. Secured with OAuth 2.0 and a required X-Medrio-ClientInfo header.
common:
- url: https://medrio.com/blog/
  type: Blog
- url: https://medrio.com/feed/
  type: BlogRSS
- type: DomainSecurity
  url: security/medrio-domain-security.yml
- type: Website
  url: https://medrio.com
- type: LinkedIn
  url: https://www.linkedin.com/company/medrio
- type: Documentation
  url: https://community.medrio.com/documentation/home
- type: APIReference
  url: https://connectapi.medrio.com/swagger/index.html
- type: OpenAPI
  url: https://connectapi.medrio.com/swagger/v1/swagger.json
- type: SignUp
  url: https://medrio.com/contact/
- type: Plans
  url: plans/medrio-plans-pricing.yml
- type: RateLimits
  url: rate-limits/medrio-rate-limits.yml
- type: FinOps
  url: finops/medrio-finops.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Medrio API — frequently asked questions

Does Medrio have an API?

Yes. APIs.io lists 6 APIs from Medrio, including Medrio Studies API, Medrio Subjects API and Medrio Data Entry API, and 3 more.

Is there an OpenAPI specification for the Medrio API?

Yes. APIs.io indexes 5 OpenAPI specifications for Medrio, each linked for download from this page.

How much does the Medrio API cost?

APIs.io lists 1 pricing plan for Medrio, with each plan's price, limits and inclusions under Pricing on this page.

Is the Medrio API ready for AI agents?

Medrio has a Kin Score of 16.9 out of 100 (emerging) and an Agent Readiness score of 13.6 (agent-aware), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/medrio"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/medrio/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/medrio/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.