#1718·corsair

Turso

Author: thephilomathSonalCreated Sep 9, 2026Updated Sep 9, 2026
Labelsenhancement

What API or service would you like integrated?

Turso

API documentation link

https://docs.turso.tech/api-reference/

What would you like to do with this integration?

I would like to add a Turso integration to Corsair for working with Turso's serverless SQLite/libSQL databases.

The integration should support three operations:

  1. TURSO_CLOSEST_REGION — determine the closest Turso deployment region based on the client's location to help minimize database latency.

  2. TURSO_LISTEN_TO_CHANGES — listen to committed insert, update, and delete events for a specific table using Turso's /beta/listen endpoint. This requires a database-specific Turso URL. Where /beta/listen is unavailable, the integration should follow Corsair's documented fallback behavior.

  3. TURSO_VALIDATE_API_TOKEN — validate a Turso API token and retrieve its expiration timestamp.

The integration will use Turso API-key/Bearer authentication and expose these capabilities as Corsair actions.

Do you need webhook support?

  • Yes, I need webhook support for this integration

Webhook details (if applicable)

No response

Additional context

Turso uses API-key/Bearer authentication. The platform API is available at https://api.turso.tech.

The /beta/listen operation requires a database-specific Turso URL rather than the platform API URL. The endpoint is unavailable on AWS regions for Free, Developer, and Scaler plans, so the implementation should respect the documented fallback behavior.

Credentials must not be committed to the repository.

The goal is to implement the integration using Corsair's existing plugin architecture and testing conventions.