Skip to main content
The List sources endpoint returns every source in the project’s knowledge graph for the authenticated project. Each item includes file metadata (ID, name, size, type, origin), current processing status, and a human-readable message. You can optionally filter by file_id.

Endpoint overview

HTTP Method

GET

Authentication

This endpoint requires authentication using an API token. 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

Query parameters

When file_ids is omitted, the response includes all sources in the project.

Response format

Success response (200 OK)

The endpoint returns a JSON array of source objects. Each object includes file metadata, status, and message:

Response fields

Status values

The status field is returned with capitalisation as stored in the backend (e.g. New, Completed). Typical values:

File Source Types

Code examples

JavaScript/Node.js

Python

cURL

Error responses

Common error codes

Error response format

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

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
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
Causes: Processing lag, system sync issues, or database inconsistenciesSolutions:
  • Wait a few minutes and retry the request
  • Check the Graphor dashboard for accurate status
  • Contact support if inconsistencies persist
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

Next steps

After listing your sources:

Upload sources

Ingest files, URLs, GitHub repos, or YouTube videos (async)

Reprocess source

Re-process an existing source with a different partition method (async)

Delete source

Remove a source from your project

Get build status

Poll status and optional elements for an async ingestion or reprocess