Connect your application
Choose a client
Section titled “Choose a client”Start with your language guide. Applications need a configured host, port, account and database name. Use the endpoint appropriate to that client, not the web console URL.
Check a local HTTP connection
Section titled “Check a local HTTP connection”curl --fail http://localhost:7173/healthcurl --fail-with-body http://localhost:7173/v1/sql \ -H 'Content-Type: application/json' \ -d '{"sql":"SELECT 1 AS ok"}'The query response contains {"ok":1} in its rows array.
Application connections
Section titled “Application connections”Use the address reference for your installed server. Enable TLS and authentication before sending credentials over a network.
Bound parameters and transactions depend on the client API. Keep a transaction on one connection; independent HTTP requests do not imply a shared transaction.
Existing tools
Section titled “Existing tools”Existing SQL clients, JDBC tools, ORMs and Redis clients have dedicated integration pages. These compatibility paths are optional; you do not need to understand their protocol implementation to build an application.
SQL client compatibility · ORMs · Redis clients
Related
Section titled “Related”This site uses Google Analytics cookies to count visits. Privacy · License