SDKs connect to Turso using the libsql:// protocol, unless using the HTTP API.

​
Database URL

You can find your database URL using the Turso CLI or Platform API, it looks something like this:

libsql://[DB-NAME]-[ORG-NAME].turso.io

WebSockets generally offer better performance when maintaining an open socket for multiple queries, whereas HTTP is typically more efficient for single queries due to reduced client-server round trips — it’s advisable to benchmark both to ascertain the best option for your specific needs.

​
Auth Tokens

SDKs require an auth token, unless working locally. You can create a new token for your database (or group) using the Turso CLI and Platform API.

Using Turso CLI and Platform API you can:

  • Create tokens for a one database or all databases in a group
  • Create full-access and read-only tokens
  • Set expiration for tokens
  • Invalidate all tokens

SDKs connect to Turso using the libsql:// protocol, unless using the HTTP API.

​
Database URL

You can find your database URL using the Turso CLI or Platform API, it looks something like this:

libsql://[DB-NAME]-[ORG-NAME].turso.io

WebSockets generally offer better performance when maintaining an open socket for multiple queries, whereas HTTP is typically more efficient for single queries due to reduced client-server round trips — it’s advisable to benchmark both to ascertain the best option for your specific needs.

​
Auth Tokens

SDKs require an auth token, unless working locally. You can create a new token for your database (or group) using the Turso CLI and Platform API.

Using Turso CLI and Platform API you can:

  • Create tokens for a one database or all databases in a group
  • Create full-access and read-only tokens
  • Set expiration for tokens
  • Invalidate all tokens