List query sources
Lists the query sources registered for this deployment. Every source supports the same operations: scan its schema, and submit queries that return a queryUuid whose results are fetched with the standard async query results endpoint. Requires the multi-source-query feature flag.
Authentication: personal access token. The spec defines an api_key security
scheme — send an Authorization: ApiKey <your-personal-access-token> header
(value format: ApiKey <your key>). A session_cookie scheme (connect.sid)
exists for browser sessions. Operations in this spec declare security: [], an
artifact of the upstream spec generator — authentication is still enforced by the
server.
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
projectUuid | string | Yes |
Responses
200 — Success
{
"results": {
"sources": [
{
"description": "string",
"label": "string",
"sourceType": "semanticLayer"
}
]
},
"status": "ok"
}default — Error
{
"error": {
"data": "string",
"message": "string",
"name": "string",
"statusCode": 0
},
"status": "error"
}List chart scheduler runs
Get the run history of a single scheduler on a chart
Scan query source schema
Scans the schema of one query source into the standard shape: tables with columns of {reference, type}. For the semantic layer, tables are explores and columns are field ids; for warehouse SQL, tables come from the warehouse catalog resolved for your credentials, like the SQL runner; the duckdb source has no schema of its own — its tables are the references given to each query.