Overview
The List Retrieval Nodes endpoint allows you to retrieve information about retrieval nodes within a flow. Retrieval nodes process queries by searching through chunked documents using vector similarity, applying filtering criteria, and returning the most relevant results for downstream processing.- Method: 
GET - URL: 
https://{flow_name}.flows.graphorlm.com/retrieval - Authentication: Required (API Token)
 
Authentication
All requests must include a valid API token in the Authorization header:Learn how to generate API tokens in the API Tokens guide.
Request Format
Headers
| Header | Value | Required | 
|---|---|---|
Authorization | Bearer YOUR_API_TOKEN | Yes | 
Parameters
No query parameters are required for this endpoint.Example Request
Response Format
Success Response (200 OK)
The response contains an array of retrieval node objects:Response Structure
Each retrieval node in the array contains:| Field | Type | Description | 
|---|---|---|
id | string | Unique identifier for the retrieval node | 
type | string | Node type (always “retrieval” for retrieval nodes) | 
position | object | Position coordinates in the flow canvas | 
style | object | Visual styling properties (height, width) | 
data | object | Retrieval node configuration and results | 
Position Object
| Field | Type | Description | 
|---|---|---|
x | number | X coordinate position in the flow canvas | 
y | number | Y coordinate position in the flow canvas | 
Style Object
| Field | Type | Description | 
|---|---|---|
height | integer | Height of the node in pixels | 
width | integer | Width of the node in pixels | 
Data Object
| Field | Type | Description | 
|---|---|---|
name | string | Display name of the retrieval node | 
config | object | Node configuration including search parameters | 
result | object | Processing results and retrieval metrics (optional) | 
Config Object
| Field | Type | Description | 
|---|---|---|
searchType | string | Type of search: “similarity”, “hybrid”, “keyword”, or “semantic” | 
topK | integer | Maximum number of documents to retrieve (default: 10) | 
scoreThreshold | float | Minimum similarity score threshold (0.0-1.0) | 
retrievalQuery | string | Custom query template for retrieval (optional) | 
Result Object (Optional)
| Field | Type | Description | 
|---|---|---|
updated | boolean | Whether the node has been processed with current configuration | 
processing | boolean | Whether the node is currently being processed | 
waiting | boolean | Whether the node is waiting for dependencies | 
has_error | boolean | Whether the node encountered an error during processing | 
updatedMetrics | boolean | Whether retrieval metrics have been calculated | 
total_retrievals | integer | Number of retrieval operations performed (if available) | 
Code Examples
JavaScript/Node.js
Python
cURL
PHP
Error Responses
Common Error Codes
| Status Code | Description | Example Response | 
|---|---|---|
| 401 | Unauthorized - Invalid or missing API token | {"detail": "Invalid authentication credentials"} | 
| 404 | Not Found - Flow not found | {"detail": "Flow not found"} | 
| 500 | Internal Server Error - Server error | {"detail": "Failed to retrieve retrieval nodes"} | 
Error Response Format
Example Error Responses
Invalid API Token
Flow Not Found
Server Error
Use Cases
Retrieval Node Management
Use this endpoint to:- Configuration Monitoring: Review search parameters and retrieval strategies
 - Performance Analysis: Check retrieval metrics and success rates
 - Flow Optimization: Analyze retrieval configurations for optimal performance
 - Quality Assurance: Monitor retrieval accuracy and relevance scores
 - Debugging: Identify issues with search configurations or processing
 
Integration Examples
Retrieval Performance Monitor
Retrieval Quality Analyzer
Best Practices
Configuration Management
- Optimal Top K: Use 5-20 results for most applications; adjust based on content volume
 - Score Thresholds: Set thresholds between 0.7-0.9 to balance quality and recall
 - Search Type Selection: Choose search types based on content characteristics and query patterns
 - Custom Queries: Use retrieval queries for domain-specific search optimization
 
Performance Optimization
- Monitor Metrics: Regularly check retrieval metrics and success rates
 - Threshold Tuning: Adjust score thresholds based on result quality analysis
 - Search Strategy: Experiment with different search types for optimal performance
 - Result Analysis: Analyze retrieved content relevance and adjust parameters accordingly
 
Quality Assurance
- Regular Auditing: Monitor retrieval node configurations for consistency
 - Performance Tracking: Track retrieval accuracy and response times
 - A/B Testing: Test different configurations to optimize retrieval quality
 - Feedback Integration: Use retrieval feedback to improve configuration parameters
 
Troubleshooting
Flow Not Found Error
Flow Not Found Error
Solution: Verify that:
- The flow name in the URL is correct and matches exactly
 - The flow exists in your project
 - Your API token has access to the correct project
 - The flow has been created and saved properly
 
Empty Retrieval Nodes Array
Empty Retrieval Nodes Array
Solution: If no retrieval nodes are returned:
- Verify the flow contains retrieval components
 - Check that retrieval nodes have been added to the flow
 - Ensure the flow has been saved after adding retrieval nodes
 - Confirm you’re checking the correct flow
 
Poor Retrieval Quality
Poor Retrieval Quality
Solution: If retrieval results are not relevant:
- Adjust score threshold to filter low-quality results
 - Increase Top K to get more diverse results
 - Check chunking node configuration for optimal chunk sizes
 - Verify that source documents contain relevant content
 
Processing Performance Issues
Processing Performance Issues
Solution: If retrieval is slow or timing out:
- Reduce Top K to decrease processing time
 - Optimize score thresholds to reduce candidate set
 - Check chunking configuration for appropriate chunk sizes
 - Monitor system resources and scaling requirements
 
Connection Issues
Connection Issues
Solution: For connectivity problems:
- Check your internet connection
 - Verify the flow URL is accessible
 - Ensure your firewall allows HTTPS traffic to *.flows.graphorlm.com
 - Try accessing the endpoint from a different network
 
Next Steps
After retrieving retrieval node information, you might want to:Update Retrieval Configuration
Modify retrieval node settings like search types, Top K, and thresholds
List Chunking Nodes
View chunking nodes that provide input to retrieval nodes
Run Flow
Execute your flow with the configured retrieval nodes
Flow Overview
Learn about all available flow management endpoints

