Radiopaedia APIradiopaedia.org ↗
Access Radiopaedia medical cases, imaging study metadata, and recent article updates via API. Search by keyword, retrieve modality data, and track edits.
What is the Radiopaedia API?
The Radiopaedia API exposes 3 endpoints covering medical case search, radiology imaging study metadata, and recently edited articles from radiopaedia.org. The search_cases endpoint accepts a keyword and returns matching case titles, URLs, and authors. The get_case_images endpoint returns study-level data including modality, description, and viewer URL for any given case page. Together the endpoints give developers structured access to one of the largest open-access radiology reference libraries.
curl -X GET 'https://api.parse.bot/scraper/73b333fc-7ade-446b-9a3e-c655cdc815dd/search_cases?query=brain' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace radiopaedia-org-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.radiopaedia_api import Radiopaedia, Case, CaseDetail, Study, Article
radio = Radiopaedia()
# Search for brain-related cases
for case in radio.cases.search(query="brain"):
print(case.title, case.url, case.author)
# Get detailed imaging studies for a specific case
detail = radio.case(url="https://radiopaedia.org/cases/cerebral-infarction-3?lang=us").images()
print(detail.title, detail.url)
for study in detail.images:
print(study.study_id, study.modality, study.description, study.url)
# List recently updated articles
for article in radio.articles.list_recent():
print(article.title, article.url, article.update_date)
Full-text search over Radiopaedia medical cases by keyword. Returns matching cases with title, URL, and author. Results are limited to the first page (up to 20 cases). Scope is restricted to cases only.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search term for medical cases (e.g. 'brain', 'glioma', 'fracture'). |
{
"type": "object",
"fields": {
"results": "array of case objects with title, url, and author"
},
"sample": {
"data": {
"results": [
{
"url": "https://radiopaedia.org/cases/traumatic-brain-injury-resulting-in-brain-death",
"title": "Traumatic brain injury resulting in brain death",
"author": "Andrew Murphy"
},
{
"url": "https://radiopaedia.org/cases/brain-death-2",
"title": "Brain death",
"author": "Bruno Di Muzio"
}
]
},
"status": "success"
}
}About the Radiopaedia API
Endpoints and Response Data
The search_cases endpoint takes a single required query string — terms like glioma, fracture, or pulmonary embolism — and returns an array of case objects. Each object includes a title, a direct url to the Radiopaedia case page, and the author credited for the case. This makes it straightforward to build keyword-driven lookups into the case library.
The get_case_images endpoint accepts the full URL of a Radiopaedia case page and returns the case title, the canonical url, and an images array. Each entry in that array is a study object containing a study_id, modality (e.g., CT, MRI, X-ray), a text description, and a viewer url pointing to the image viewer for that study. This is the primary way to retrieve structured imaging metadata tied to a specific case.
Recent Article Tracking
The get_recent_articles endpoint requires no inputs and returns up to 50 articles from Radiopaedia's Recent Edits page. Each article object includes a title, url, and update_date expressed as a relative timestamp. This is useful for monitoring which reference articles have been revised recently, which matters in clinical or educational contexts where content currency is important.
Coverage and Scope
All three endpoints reflect publicly accessible content on radiopaedia.org. Case and article data is scoped to what appears on public-facing pages; content behind institutional login walls is not included. The search endpoint mirrors keyword-based case discovery, while imaging metadata is scoped to study-level entries rather than individual DICOM frames.
The Radiopaedia API is a managed, monitored endpoint for radiopaedia.org — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when radiopaedia.org changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official radiopaedia.org API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a radiology reference search tool that maps clinical keywords to Radiopaedia case titles and authors via
search_cases. - Populate a medical education platform with curated case lists filtered by imaging modality using
get_case_imagesresponse fields. - Monitor the
get_recent_articlesfeed to surface newly edited radiology articles in a daily digest or newsletter. - Aggregate study metadata (modality, description, viewer URL) from multiple cases to compile structured radiology training datasets.
- Cross-reference case author fields from
search_casesto identify prolific contributors by topic area. - Embed Radiopaedia viewer links from
get_case_imagesinto third-party clinical learning management systems. - Track recent edits to specific condition-related articles by filtering
get_recent_articlesoutput by title keywords.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Radiopaedia have an official developer API?+
What does `get_case_images` actually return — are full images included?+
study_id, modality, description, and a url to the Radiopaedia image viewer for each study attached to the case. It does not return raw image files or DICOM data, only the structured metadata and viewer links.Does `search_cases` support filtering by modality or specialty?+
search_cases endpoint accepts a free-text query string and returns matching cases with title, url, and author. It does not currently expose modality or specialty filters as discrete parameters. You can fork this API on Parse and revise it to add filtered search parameters if your workflow requires narrower result sets.