Execute SQL statement with database specified in path (GET method)
Alternative GET method for executing SQL statements with the database specified in the URL path. Parameters are passed as URL query parameters. Does not support the params field.
This endpoint is functionally identical to GET /execute but with the database
specified in the URL path. This can be more convenient for clients that
organize requests by database.
Example
Authentication
Path parameters
Headers
Supported compression algorithms for responses. Multiple algorithms can be specified as a comma-separated list. Common values include ‘gzip’, ‘deflate’, ‘br’ (Brotli), or combinations like ‘gzip, br’.
Note that for large result sets, compression may produce suboptimal results. Without compression the result sets can be chunks of rows and processed in a streaming fashion. With compression the entire result set must be compressed before it is returned to the client. Thus the entire result set will be decompressed on the client before any rows can be processed
Indicates the preferred encoding type from those specified in Accept-Encoding. This header provides fine-grained control when Accept-Encoding contains multiple values, allowing the client to explicitly specify which encoding is preferred for this specific request.
Specifies the desired compression level for the selected encoding algorithm. Values typically range from 1 (fastest, least compression) to 9 (slowest, maximum compression). The exact behavior depends on the specific compression algorithm being used.
Query parameters
SQL statement to execute. The statement must be URL-encoded.
Response format:
- array - Returns schema and data as arrays (more efficient for large datasets)
- collection - Returns data as JSON objects (more convenient for client processing)

