A valid request URL is required to generate request examples{
"results": {
"queries": [
{
"queryUuid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"sourceType": "semanticLayer",
"nodeId": "<string>"
}
]
},
"status": "ok"
}{
"error": {
"name": "<string>",
"statusCode": 123,
"data": "<unknown>",
"message": "<string>"
},
"status": "error"
}Execute source queries
Submits one or more source queries through the common interface. Every query body is tagged by sourceType and every query returns a queryUuid, polled with the standard async query results endpoint (or Get source query status for many at once).
Queries reference each other’s results by nodeId: a duckdb query’s references expose other queries’ results as tables, named by node id (array shorthand) or by alias (map form, which also accepts queryUuids of results from previous submissions). A referenced result keeps the column names of the query that produced it — field ids for semanticLayer queries, SELECT output names for sql queries.
All queries are submitted immediately; a query referencing still-running results waits inside its own execution and fails if a referenced query fails, so no orchestration happens outside the queries themselves. Submit queries one at a time (interactive use) or as a whole pipeline in one call — the two are equivalent, so a serialized multi-query analysis is just the bodies of the queries that were run interactively, with queryUuid references swapped for node ids. Note that results expire: re-run upstream queries whose results have expired instead of referencing their old queryUuids.
A valid request URL is required to generate request examples{
"results": {
"queries": [
{
"queryUuid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"sourceType": "semanticLayer",
"nodeId": "<string>"
}
]
},
"status": "ok"
}{
"error": {
"name": "<string>",
"statusCode": 123,
"data": "<unknown>",
"message": "<string>"
},
"status": "error"
}Path Parameters
Body
One or more source queries, submitted together. Order does not matter: queries are submitted in dependency order (a duckdb query after the queries its references name) and every query starts executing immediately — dependency waiting happens inside the referencing query.
The tagged union every submit endpoint takes: one shape per source, discriminated by sourceType. New sources add a member here — this union is the extension point, not new WarehouseTypes values.
- Option 1
- Option 2
- Option 3
- Option 4
Show child attributes
Show child attributes
Bypass cached results for every query in the submission.
Parameter values shared by every query in the submission, layered over project and explore defaults. A query referencing a parameter with no value refuses rather than running with a placeholder.
Show child attributes
Show child attributes
dashboardView, autorefreshedDashboard, exploreView, filterAutocomplete, chartView, chartHistory, sqlChartView, sqlRunner, viewUnderlyingData, alert, scheduledDelivery, csvDownload, gsheets, scheduledGsheetsChart, scheduledGsheetsDashboard, scheduledGsheetsSqlChart, scheduledChart, scheduledDashboard, calculateTotal, calculateSubtotal, embed, ai, mcp.run_metric_query, mcp.run_sql, mcp.search_field_values, api, cli, metricsExplorer, preAggregateMaterialization, composeSqlRunner, multiSourceQuery, dataAppSample Was this page helpful?