Endpoint Overview
HTTP Method
GET
Endpoint URL
Authentication
This endpoint requires authentication using an API token. You must include your API token as a Bearer token in the Authorization header.Learn how to create and manage API tokens in the API Tokens guide.
Request Format
Headers
Header | Value | Required |
---|---|---|
Authorization | Bearer YOUR_API_TOKEN | ✅ Yes |
Query Parameters
This endpoint does not require any query parameters. It returns all sources in the dataset associated with your API token.Response Format
Success Response (200 OK)
The endpoint returns an array of source objects with comprehensive information about each document:Response Fields
Field | Type | Description |
---|---|---|
status | string | Current processing status (see status values below) |
message | string | Human-readable status description |
file_name | string | Name of the source file or identifier |
file_size | integer | Size of the file in bytes (0 for URLs) |
file_type | string | File extension or type |
file_source | string | Source type: local file , url , github , or youtube |
project_id | string | UUID of the project |
project_name | string | Name of the project |
partition_method | string | Processing method used or applied |
Status Values
New
New
Description: Document has been uploaded but processing hasn’t started yetNext Steps: Processing will begin automatically or can be triggered manually
Processing
Processing
Description: Document is currently being processedDuration: Can take from minutes to hours depending on document complexity and method
Completed
Completed
Description: Document has been successfully processed and is ready for useReady for: Chunking, retrieval, and integration in RAG pipelines
Failed
Failed
Description: Document processing encountered an errorActions: Check document format, try different processing method, or contact support
Unknown
Unknown
Description: Status information is not availableCauses: System error or data inconsistency
File Source Types
Source Type | Description | Typical Use Cases |
---|---|---|
local file | Files uploaded directly from your computer | Documents, PDFs, images, spreadsheets |
url | Content imported from web URLs | Web pages, articles, online documents |
github | Content imported from GitHub repositories | Code documentation, README files, wikis |
youtube | Content imported from YouTube videos | Video transcripts, educational content |
Code Examples
JavaScript/Node.js
Python
cURL
PHP
Error Responses
Common Error Codes
Status Code | Error Type | Description |
---|---|---|
401 | Unauthorized | Invalid or missing API token |
403 | Forbidden | Access denied to the specified project |
500 | Internal Server Error | Server-side error retrieving sources |
Error Response Format
Error Examples
Invalid API Token (401)
Invalid API Token (401)
Access Denied (403)
Access Denied (403)
Server Error (500)
Server Error (500)
Response Analysis
Filtering and Processing Results
Status Monitoring
Integration Examples
Project Health Check
Source Management Dashboard
Automated Processing Pipeline
Best Practices
Performance Optimization
- Cache results: Store the response locally for a reasonable period
- Filter client-side: Process the full list to extract specific information you need
- Monitor regularly: Set up automated checks for processing status
- Batch operations: Use the list to plan batch processing operations
Data Management
- Track processing times: Monitor how long documents take to process
- Identify patterns: Look for file types or sizes that frequently fail
- Maintain logs: Keep records of source management activities
- Plan capacity: Use file counts and sizes for storage planning
Error Handling
- Implement retries: Handle temporary network issues with exponential backoff
- Log failures: Keep detailed logs of API failures for debugging
- Monitor status: Regularly check for failed processing jobs
- Graceful degradation: Have fallback plans when the API is unavailable
Troubleshooting
Slow response times
Slow response times
Causes: Large number of sources, server load, or network issuesSolutions:
- Implement request timeouts (30+ seconds recommended)
- Use response caching for non-critical applications
- Consider pagination if available in future API versions
Empty response
Empty response
Causes: No sources in project, wrong API token, or permission issuesSolutions:
- Verify you have uploaded documents to your project
- Check that your API token is correct and active
- Ensure you’re accessing the right project
Inconsistent status information
Inconsistent status information
Causes: Processing lag, system sync issues, or database inconsistenciesSolutions:
- Wait a few minutes and retry the request
- Check the GraphorLM dashboard for accurate status
- Contact support if inconsistencies persist
Authentication errors
Authentication errors
Causes: Invalid token, expired token, or revoked accessSolutions:
- Verify token format and validity
- Check token hasn’t been revoked in dashboard
- Generate a new token if necessary