SQL statements are executed by using HTTP methods and a URL that contains the SQL statement. Parameters are typically given by using http payload. All responses are JSON structures and contain meta, data, and status structures, see HTTP SQL requests and responses. Some structures might be empty depending on the request.
In the case of DDL and DML statements, the JSON structure that is returned contains empty meta and data structures. The status structure contains information about the DDL/DML statement execution result (response code, rows affected).
In the case of a query, the JSON structure that is returned contains result set metadata and the row data. For very large results, the result set that is returned might not be complete, in which case the HTTP response status code 206 is returned. You can then fetch more rows by sending the same request again until the complete result set and the HTTP response status code 200 are returned.
Note that '?' must be HTML URL encoded as '%3F' in URLs. If '?' binding is used, the actual parameter values are passed inside the message body. The parameters must be named by using keywords: param1=, param2= and so on. The number identifies the location of the '?' in the SQL statement. For example:
The message body sent with the message contains actual parameter values, for example: "param1=4¶m2=1".
The number of rows that are returned in one JSON response is limited to 100 rows. If more rows are available, the status response code 206 is returned, for example: