Meddra · Authentication Profile

Meddra Authentication

Authentication

Meddra secures its APIs with oauth2 and openIdConnect across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the implicit flow(s).

Medical TerminologyPharmacovigilanceDrug SafetyAdverse EventsRegulatoryClinical TrialsHealthcareLife SciencesStandardsOntology
Methods: oauth2, openIdConnect Schemes: 1 OAuth flows: implicit API key in:

Security Schemes

oauth2 oauth2
· flows: implicit

Source

Authentication Profile

Raw ↑ 
generated: '2026-09-17'
method: searched
source: https://mid.meddra.org/.well-known/openid-configuration
docs: https://www.meddra.org/meddra-apis
note: Derived from the harvested OpenAPI securityScheme and then upgraded from the provider's own OpenID Connect discovery
  document at mid.meddra.org, which is the authorization server the spec names. Every operation except GET /api/status
  requires a bearer token; /api/status is explicitly documented by the MSSO as not requiring authentication. A MedDRA
  user ID and an active MSSO subscription are prerequisites for obtaining credentials - the detailed programmer guides
  sit behind the subscriber login at https://www.meddra.org/private/api-info.
summary:
  types:
  - oauth2
  - openIdConnect
  oauth2_flows:
  - implicit
  anonymous_operations:
  - GET /api/status
schemes:
- name: oauth2
  type: oauth2
  flows:
  - flow: implicit
    authorizationUrl: https://mid.meddra.org/connect/authorize
    tokenUrl: https://mid.meddra.org/connect/token
    scopes: 1
  sources:
  - openapi/meddra-api-openapi.yml
identity_provider:
  issuer: https://mid.meddra.org/
  product: Duende/IdentityServer (ASP.NET)
  discovery: https://mid.meddra.org/.well-known/openid-configuration
  discovery_status: 200
  jwks_uri: https://mid.meddra.org/.well-known/openid-configuration/jwks
  authorization_endpoint: https://mid.meddra.org/connect/authorize
  token_endpoint: https://mid.meddra.org/connect/token
  introspection_endpoint: https://mid.meddra.org/connect/introspect
  revocation_endpoint: https://mid.meddra.org/connect/revocation
  device_authorization_endpoint: https://mid.meddra.org/connect/deviceauthorization
  userinfo_endpoint: https://mid.meddra.org/connect/userinfo
  offline_access: true
runtime_evidence:
- url: https://mapisbx.meddra.org/api/status
  status: 200
  note: anonymous; body "API is Running"
- url: https://mapisbx.meddra.org/api/rel
  status: 401
  note: 'WWW-Authenticate: Bearer'
- url: https://mapisbx.meddra.org/api/lang/E
  status: 401
  note: 'WWW-Authenticate: Bearer'

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • 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 security artifact 
curl "https://apis.io/api/v1/security/meddra-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

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.