--- title: Turso API Integration on Truto slug: turso category: Default canonical: "https://truto.one/integrations/detail/turso/" --- # Turso API Integration on Truto **Category:** Default **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Organizations** — Organizations are the top level entity in the source application. Users are associated with an organization. - **Roles** — The Role object represents a role of a User. - **Users** — The User object represents a User. ## How it works 1. **Link your customer's Turso account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Turso.** The Proxy API is a 1-to-1 mapping of the Turso API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Automate database-per-tenant provisioning for your customers** — If you're building a platform that manages multi-tenant infrastructure, connecting to your users' Turso accounts lets you programmatically spin up isolated databases, assign edge locations, and mint scoped tokens — all without your users leaving your product. - **Offer database branching in CI/CD and preview environments** — DevTools and hosting SaaS companies can integrate with their users' Turso accounts to automatically branch production databases for PR previews and staging environments, then clean up branches on merge — giving end users production-like data in every deploy preview. - **Aggregate cross-tenant analytics from database-per-tenant architectures** — BI and analytics SaaS products can connect to a customer's Turso organization, enumerate all their tenant databases, and extract metrics across hundreds of isolated edge databases to power centralized dashboards and reporting. - **Provision and manage vector stores for AI agent workflows** — AI SaaS platforms can connect to users' Turso accounts to create dedicated databases with vector indexes, sync embeddings from uploaded documents, and enable low-latency RAG retrieval directly from the user's own edge infrastructure. - **Sync organization membership and roles for access governance** — Security and compliance SaaS products can pull organization members, roles, and invites from a customer's Turso account to audit access, enforce policies, and maintain a unified view of who has access to database infrastructure. ## What you can build - **One-click database branch creation for preview deploys** — Automatically fork a user's production Turso database when a PR is opened and inject the branch URL into the preview environment. - **Tenant database lifecycle manager** — Provision, configure edge locations for, and tear down isolated Turso databases as tenants are onboarded or offboarded in your platform. - **Cross-database metrics aggregation pipeline** — Enumerate all databases in a user's Turso organization and run extraction queries across them to feed a centralized analytics dashboard. - **Organization member and role sync** — Pull Turso organization users, roles, and invites into your product's user directory to power access reviews, audit logs, and RBAC policies. - **Scoped token minting for tenant isolation** — Programmatically generate restricted API tokens for individual tenant databases so end users can safely grant least-privilege access to downstream services. - **GDPR-aware edge group assignment** — Automatically assign newly provisioned databases to region-specific Turso groups based on tenant geography to satisfy data residency requirements. ## FAQs ### How do end users authenticate their Turso accounts through Truto? Turso uses API tokens for authentication. End users provide a Platform API token (generated from their Turso dashboard or CLI), which Truto securely stores and uses to make API calls on their behalf. ### What Unified APIs does Truto support for Turso? Turso is mapped to Truto's Unified User Directory API, which covers Organizations, Roles, and Users. This lets you read and manage organization membership and access roles through a standardized schema. ### Are there specific Truto tools available for Turso's Platform API operations like database provisioning or branching? Turso tools for operations like database creation, branching, group management, and token minting are built on request. Contact Truto to scope the specific Platform API endpoints your integration needs. ### Does Turso have rate limits I should be aware of? Yes, Turso's Platform API enforces rate limits that vary by plan. Truto handles retry logic and pagination so your integration gracefully manages rate-limited responses without you writing custom backoff code. ### Can I interact with the actual data inside a user's Turso databases through Truto? Turso exposes two API surfaces: the Platform API (infrastructure management) and the Database API (SQL over HTTP via libSQL). Truto's current mapping covers the Platform API side. Support for proxying SQL queries via the Database API can be scoped on request. ### How does Truto handle Turso's multi-organization structure? Turso users can belong to multiple organizations. Through the Unified User Directory API, Truto normalizes organization membership, roles, and user data so you can work with a consistent schema regardless of how many organizations an end user manages.