Alternative GET method for executing SQL statements. This method passes parameters as URL query parameters. This method does not support the params body parameter.
This method is most suitable for simple, read-only queries where the statement can be safely included in a URL. For complex queries or those with parameters, use the POST method instead.
Access token obtained from the /v1/login endpoint.
Include in the Authorization header as: Bearer {token}
Supported response media types. The API returns large query results using chunked encoding.
application/json, application/stream+json, application/parquet Supported compression algorithms for responses. You can specify multiple algorithms as a comma-separated list.
Note: For large result sets, compression can impact performance. Without compression, result sets can be processed in a streaming fashion. With compression, the entire result set must be compressed before it is returned to the client.
The specific database in your system for the API call. If not specified, defaults to the database from the authentication token or system settings.
A valid SQL statement to execute. The statement must be URL-encoded.
Sets the response format.
array - Returns the schema and data as arrays (more efficient for large data sets) (default)collection - Returns data as JSON objects (more convenient for client processing)array, collection The number of rows to return in each chunk for streaming responses. A value of 0 (default) means the database determines how many rows to return.
x >= 0