Overview
This advanced endpoint allows you to traverse complex relationship networks across multiple concepts, following chains of relationships with sophisticated filtering and path-finding capabilities. Essential for advanced medical terminology analysis and complex queries.Request Body
Array of starting concept IDs for traversal
Rules defining how to traverse relationships
Optional criteria for target concepts
Query Parameters
Specific vocabulary release version (e.g., “2024.1”)
Response
Indicates whether the request was successful
Results for each starting concept
Overall traversal statistics
Request metadata and response information
Usage Examples
Basic Relationship Traversal
Simple traversal with default settings:Cross-Vocabulary Mapping
Find mappings between vocabularies:Path Finding
Find specific paths between concepts:Important Notes
- Complexity limits: Maximum 10 starting concepts and depth 10 to prevent performance issues
- Result limits: Use
max_results_per_concept
to control response size - Performance: Complex traversals may take several seconds
- Memory usage: Deep traversals with many concepts can be memory-intensive
- Path finding: Enable path details only when needed as it increases processing time
Related Endpoints
- Batch Relationship Queries - Simpler bulk relationship queries
- Get Concept Relationships - Single concept relationships
- Get Concept Hierarchy - Hierarchical relationships only