Meddra

MedDRA (Medical Dictionary for Regulatory Activities) is the clinically validated international medical terminology developed under the auspices of the International Council for Harmonisation (ICH) and used by regulatory authorities and the regulated biopharmaceutical industry for adverse event coding, drug safety reporting and pharmacovigilance. It is maintained by the MedDRA Maintenance and Support Services Organization (MSSO), which publishes a new version twice a year in English and more than a dozen translations. The MSSO operates a REST API programme so subscribers can embed MedDRA term search, hierarchy navigation (SOC, HLGT, HLT, PT, LLT), SMQ analysis, version-impact reporting and subscription validation in their own pharmacovigilance and clinical systems. Two API environments are operated: a GxP-assessed one carrying four APIs for validated systems, and a wider non-GxP environment carrying sixteen. Access requires an MSSO subscription.

Meddra publishes 1 API on the APIs.io network. Tagged areas include Medical Terminology, Pharmacovigilance, Drug Safety, Adverse Events, and Regulatory.

The Meddra catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Meddra’s developer surface includes developer portal, documentation, API reference, support, pricing, signup flow, developer console, and 28 more developer resources.

🌐 Visit website 📡 Source on GitHub

40.4/100 developing ▬ flat Agent 28/100 agent aware Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0

1 APIs

Medical TerminologyPharmacovigilance Drug Safety Adverse Events Regulatory Clinical Trials Healthcare Life Sciences Standards Ontology

Kin Score

Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0

Composite quality — 40.4/100 · developing

Contract Quality 8.5 / 19

Developer Ergonomics 4.2 / 15

Access Clarity 7.1 / 15

Operational Transparency 1.5 / 10

Contract Governance 2.5 / 9

Discoverability 5.0 / 8

Regulatory Posture 4.6 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 28/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 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 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

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

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 github.com/api-evangelist/meddra: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

MedDRA API

The MedDRA API published by the MSSO — term and SMQ search, term/SMQ detail, hierarchy navigation and analysis, parent/child type lookup, term history, SMQ analysis, data-file d...

Pricing Plans 1

Published pricing tiers and plan structures.

Meddra Plans Pricing

11 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Meddra Rate Limits

0 limits

RATE LIMITS

FinOps 1

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

Meddra Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Meddra Context

2 classes · 13 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Meddra API Rules

5 rules · 3 warnings 2 info

SPECTRAL

JSON Schema 1

Standalone JSON Schema definitions for this provider's data models.

MedDRA Term

9 properties

JSON SCHEMA

Security Posture 2

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

Meddra Authentication

oauth2/openIdConnect · 1 scheme

SECURITY

Meddra Domain Security

TLSv1.3

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Meddra Scopes

3 scopes · implicit

3 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Meddra Agentic Access

16 operations

16 operations · 0 acting

AGENTIC

Resources

Get Started 5

Portal, sign-up, and the first successful call

Portal

DeveloperPortal

SignUp

Console

Sandbox

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

JSONSchema

JSONSchema

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

X-MCPServerCandidate

X-MCPServerCandidate

AgenticAccess

AgenticAccess

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Rules

JSONLDContext

Scroll for all 7

Build 1

SDKs, sample code, and the tooling you integrate with

Packages

Packages

Access & Security 4

Authentication, authorization, and security posture

Authentication

OAuthScopes

DomainSecurity

Compliance

Operate 3

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

Plans

Plans

FinOps

FinOps

Company 2

The organization behind the API

Website

Website

LinkedIn

Other 2

Properties that don't map to a standard resource type

X-Downloads

X-Downloads

Overlay

Overlay

Source (apis.yml)

name: Meddra
aid: meddra
specificationVersion: '0.23'
deliveryModel:
  model: licensed
  open_source: false
  commercial: true
  callable_host: true
  label: Licensed terminology - annual MSSO subscription; API access included with the subscription
  confidence: high
  source:
  - plans
  - openapi
  generated: '2026-09-17'
  method: searched
accessModel:
  pricing: subscription
  onboarding: application
  trial: false
  try_now: false
  public: false
  label: Annual subscription - free for regulatory authorities and non-profits, sliding-scale fee for commercial
  confidence: high
  try_now_blocked_by: subscription-required
  source:
  - plans
  - authentication
  generated: '2026-09-17'
  method: searched
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/meddra.png
url: https://raw.githubusercontent.com/api-evangelist/meddra/refs/heads/main/apis.yml
description: 'MedDRA (Medical Dictionary for Regulatory Activities) is the clinically validated international medical terminology
  developed under the auspices of the International Council for Harmonisation (ICH) and used by regulatory authorities and
  the regulated biopharmaceutical industry for adverse event coding, drug safety reporting and pharmacovigilance. It is maintained
  by the MedDRA Maintenance and Support Services Organization (MSSO), which publishes a new version twice a year in English
  and more than a dozen translations. The MSSO operates a REST API programme so subscribers can embed MedDRA term search,
  hierarchy navigation (SOC, HLGT, HLT, PT, LLT), SMQ analysis, version-impact reporting and subscription validation in their
  own pharmacovigilance and clinical systems. Two API environments are operated: a GxP-assessed one carrying four APIs for
  validated systems, and a wider non-GxP environment carrying sixteen. Access requires an MSSO subscription.'
tags:
- Medical Terminology
- Pharmacovigilance
- Drug Safety
- Adverse Events
- Regulatory
- Clinical Trials
- Healthcare
- Life Sciences
- Standards
- Ontology
created: '2026-05-03'
modified: '2026-09-17'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
apis:
- aid: meddra:meddra-api
  name: MedDRA API
  description: The MedDRA API published by the MSSO — term and SMQ search, term/SMQ detail, hierarchy navigation and analysis,
    parent/child type lookup, term history, SMQ analysis, data-file download, search export, language and release listings,
    version and data-impact reports, subscription validation, and an unauthenticated status check. Sixteen operations in the
    non-GxP "Production" (formerly Sandbox) environment; four of them (Details, Search, Status, Type) are also offered in
    the GxP-assessed environment. Every operation but Status requires an OAuth 2.0 bearer token issued by the MedDRA identity
    provider against a MedDRA subscription.
  humanURL: https://www.meddra.org/meddra-apis
  baseURL: https://mapisbx.meddra.org
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/meddra.png
  tags:
  - Medical Terminology
  - Pharmacovigilance
  - Adverse Events
  - Search
  - Hierarchy
  properties:
  - type: OpenAPI
    url: openapi/meddra-api-openapi.yml
  - type: OpenAPI
    name: OpenAPI (provider-hosted)
    url: https://mapisbx.meddra.org/swagger/v1/swagger.json
  - type: Documentation
    url: https://www.meddra.org/meddra-apis
  - type: APIReference
    url: https://mapisbx.meddra.org/index.html
  - type: Authentication
    url: authentication/meddra-authentication.yml
  - type: OAuthScopes
    url: scopes/meddra-scopes.yml
  - type: ErrorCatalog
    url: errors/meddra-problem-types.yml
  - type: Overlay
    url: overlays/meddra-api-overlay.yaml
  - type: DataModel
    url: data-model/meddra-data-model.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/meddra/refs/heads/main/json-schema/meddra-term-schema.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/meddra/refs/heads/main/json-ld/meddra-context.jsonld
common:
- type: Website
  url: https://www.meddra.org/
- type: Portal
  url: https://www.meddra.org/meddra-apis
- type: DeveloperPortal
  url: https://www.meddra.org/meddra-apis
- type: Documentation
  url: https://www.meddra.org/meddra-apis
- type: APIReference
  url: https://mapisbx.meddra.org/index.html
- type: Support
  url: https://www.meddra.org/contact
- type: Pricing
  url: https://www.meddra.org/subscription-rates
- type: SignUp
  url: https://www.meddra.org/subscription/subscription-form
- type: LinkedIn
  url: https://www.linkedin.com/company/meddra-msso
- type: X-Downloads
  url: https://www.meddra.org/software-packages
- type: Console
  name: Swagger console
  url: https://mapisbx.meddra.org/index.html
- type: Authentication
  url: authentication/meddra-authentication.yml
- type: OAuthScopes
  url: scopes/meddra-scopes.yml
- type: WellKnown
  url: well-known/meddra-well-known.yml
- type: DomainSecurity
  url: security/meddra-domain-security.yml
- type: Conventions
  url: conventions/meddra-conventions.yml
- type: ErrorCatalog
  url: errors/meddra-problem-types.yml
- type: Lifecycle
  url: lifecycle/meddra-lifecycle.yml
- type: ChangeLog
  url: changelog/meddra-changelog.yml
- type: Conformance
  url: conformance/meddra-conformance.yml
- type: Compliance
  url: conformance/meddra-conformance.yml
- type: Sandbox
  url: sandbox/meddra-sandbox.yml
- type: DataModel
  url: data-model/meddra-data-model.yml
- type: Packages
  url: packages/meddra-packages.yml
- type: LLMsTxt
  url: llms/meddra-llms.txt
- type: Overlay
  url: overlays/meddra-api-overlay.yaml
- type: AgentSkill
  url: skills/_index.yml
- type: X-MCPServerCandidate
  url: mcp/meddra-mcp.yml
- type: AgenticAccess
  url: agentic-access/meddra-agentic-access.yml
- type: Plans
  url: plans/meddra-plans-pricing.yml
- type: RateLimits
  url: rate-limits/meddra-rate-limits.yml
- type: FinOps
  url: finops/meddra-finops.yml
- type: Rules
  url: rules/meddra-jsonschema-spectral-rules.yml
- type: JSONSchema
  url: https://raw.githubusercontent.com/api-evangelist/meddra/refs/heads/main/json-schema/meddra-term-schema.json
- type: JSONLDContext
  url: https://raw.githubusercontent.com/api-evangelist/meddra/refs/heads/main/json-ld/meddra-context.jsonld
x-enrichment:
  date: '2026-09-17'
  status: enriched
  artifacts_added: 21
  pass: local-v3

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/meddra"

All providers

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

Every operation they expose

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

How their score was established

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

Discovery needs no key. Ratings and market analysis are Pro.

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.