1. List MedDRA versions
version identifier, optional releaseDate, aggregated counts/changes, and an isLatest flag. If you do nothing else, every endpoint will use the latest release.
Want to pin to a specific MedDRA version? Pass?version=28.1(or the release you need) or addX-MedDRA-Version: 28.1to the request headers.
2. Search MedDRA codes
soc, hlgt, hlt, llt), restrict to a particular level (level=PT), or zero in on release deltas (changeType=ADDED). The response includes an _meta block with pagination data plus hierarchy context for each match so you can link straight to detail pages in the app.
3. View a MedDRA code
?version=28.1 to see the same code in an older release.
4. Predict a MedDRA code with an event description
assessments object. If you omit the version, the service uses the latest release (or respects the X-MedDRA-Version header). Calls without the X-API-Key header will be rejected with 401 Unauthorized.
5. Focus on release changes
changeType with hierarchy filters to highlight additions, updates, or retirements in a specific slice of the terminology between releases.
Next steps
- Review version selection guidance for deeper control over releases and precedence rules.
- Browse the API reference for every endpoint, schema, and rate-limit note.
- Prototype UI flows with the public web app at meddra.co and reuse the same endpoints server-side.