turbopuffer
This connector is a Reverse ETL destination for sending data to turbopuffer.
Status
This destination is currently in development. Authentication can be validated, but loading/syncing data is not yet available.
Setup
- In turbopuffer, create or obtain an API key with access to your account.
- Determine the region for your turbopuffer deployment (see supported values below).
- In your Reverse ETL destination configuration, enter the API key and region.
Authentication
This destination authenticates using a Bearer token.
- Header:
Authorization: Bearer <api_key> - During credential validation, the connector calls:
GET https://{region}.turbopuffer.com/v1/namespaces
If the request fails, the connector reports a credential validation error.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
api_key | string | ✅ | turbopuffer API key used for Bearer authentication. |
region | string | ✅ | turbopuffer region subdomain used to build the API base URL. Supported values: us-east-1, gcp-us-central1, aws-eu-west-1. |
Streams
Not yet available. This destination does not currently load records into turbopuffer.
Hashing and normalization
This destination does not currently expose field-level hashing options.
Data contract
Not yet available. The destination load behavior and required schema are still in development.