Query Connector
Run an ad-hoc SQL query against a connector’s source and return the bounded result inline. Read-only by default (enforced node-side); write mode must also be allowed by the connection’s local policy on the connector box. Requires a connector advertising query:sql (0.1.26+).
Authorizations
Timbal API key. Obtain your API key from the Timbal platform settings. See Authentication for more information.
Body
Connection ref on the node (from /browse/connections).
The SQL to run. One statement on MySQL; multi-statement batches work on Postgres and SQL Server (the last result set is returned; on Postgres that's the last row-returning set — zero-row sets are invisible to the node's driver — while SQL Server returns the true last set even when empty).
Row cap on the returned result. Defaults to 500, ceiling 10000.
x >= 0read (default) | write. read is enforced node-side with
engine-level read-only semantics; write additionally requires the
connection's local policy (connections.json) to allow writes.
Node-side execution budget in milliseconds. Defaults to 30000, ceiling 60000.
x >= 0Response
Query executed
x >= 0Row-major, aligned with columns. Cells are plain JSON scalars:
numbers stay numbers, exact decimals and timestamps are strings,
binary is 0x-prefixed hex, NULL is null.
The node's row or byte cap bit — rows is a prefix of the real result.
Rows changed by non-row-returning statements, when the engine reports
it (Postgres/MySQL; null on SQL Server = unknown, not zero).
x >= 0