Tavus

Tavus is an AI video generation platform for creating personalized and conversational video content. Its API exposes programmatic access to replicas, videos, lipsyncs, faces, voices, and conversations, letting you generate and manage AI-driven video assets at scale.

Power end-to-end data operations for your Tavus API with Nexla. Our bi-directional Tavus connector is purpose-built for Tavus, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Tavus or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Tavus workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Tavus credential, you need a Tavus account and an API key. Tavus authenticates every API request with an API key sent in the x-api-key request header.

To obtain your Tavus API key, follow these steps:

1. Sign in to your Tavus account at the Tavus Platform.

2. Open the API Keys section of the Developer Portal. In the current Tavus interface this is available from the API Key menu within the platform.

3. Click Create New Key, enter a name for the key, and optionally restrict it to specific allowed IP addresses.

4. Click Create API Key and copy the generated key. Store it securely, as it grants access to your Tavus account and should be treated as a secret.

Your API key is confidential and should never be exposed in client-side code such as browsers or mobile apps. If a key is compromised, revoke it in the Tavus Developer Portal and generate a new one. For detailed information about authentication and available endpoints, refer to the Tavus API documentation.

Authenticate

Credentials required

An authentication method that requires sending a unique secret token with each API request

Field	Required	Secret	Description
API Key Value	Yes	Yes	An encoded string value used as a secret token to authenticate API requests

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Tavus API key in the API Key Value field. This value is sent in the x-api-key header on every request to the Tavus API and must be kept confidential.

   If your API key is compromised, revoke it in the Tavus Developer Portal and generate a new one. The API key grants access to your Tavus account data and should be treated as sensitive information.

   For detailed information about authentication and available endpoints, see the Tavus API documentation.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Tavus connector tile, then select the credential that will be used to connect to Tavus, and click Next; or, create a new Tavus credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Tavus endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Lipsyncs

This endpoint template retrieves a list of lipsyncs from your Tavus account.

For detailed information about response structures and available fields, see the Tavus API documentation.

[Rest API] Get Lipsync

This endpoint template retrieves a single lipsync by its identifier from your Tavus account.

For detailed information about response structures and available fields, see the Tavus API documentation.

[Rest API] List Replacements

This endpoint template retrieves a list of replacements from your Tavus account.

For detailed information about response structures and available fields, see the Tavus API documentation.

[Rest API] Get Replacement

This endpoint template retrieves a single replacement by its identifier from your Tavus account.

For detailed information about response structures and available fields, see the Tavus API documentation.

[Rest API] List Videos

This endpoint template retrieves a list of generated videos from your Tavus account.

For detailed information about response structures and available fields, see the Tavus API documentation.

[Rest API] Get Video

This endpoint template retrieves a single video by its identifier from your Tavus account.

For detailed information about response structures and available fields, see the Tavus API documentation.

[Rest API] List Faces

This endpoint template retrieves a list of faces from your Tavus account.

For detailed information about response structures and available fields, see the Tavus API documentation.

[Rest API] Get Face

This endpoint template retrieves a single face by its identifier from your Tavus account.

For detailed information about response structures and available fields, see the Tavus API documentation.

[Rest API] List Voices

This endpoint template retrieves a list of available voices from your Tavus account.

For detailed information about response structures and available fields, see the Tavus API documentation.

[Rest API] List Conversations

This endpoint template retrieves a list of conversations from your Tavus account.

For detailed information about response structures and available fields, see the Tavus API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Tavus data sources can also be manually configured to ingest data from any valid Tavus API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Tavus data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Tavus destination, and select the Send to Destination option from the menu. Select the Tavus connector from the list of available destination connectors, then select the credential that will be used to connect to Tavus, and click Next; or, create a new Tavus credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Tavus endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Lipsync

This endpoint template creates a new lipsync in your Tavus account using records from a Nexset.

Each record from your Nexset is sent as a request to the Tavus API. Ensure the record structure matches the format expected by the endpoint. For detailed information about request body formats, see the Tavus API documentation.

[Rest API] Delete Lipsync

This endpoint template deletes a lipsync from your Tavus account using records from a Nexset.

Each record from your Nexset is sent as a request to the Tavus API. Ensure the record structure matches the format expected by the endpoint. For detailed information about request body formats, see the Tavus API documentation.

[Rest API] Create Replacement

This endpoint template creates a new replacement in your Tavus account using records from a Nexset.

Each record from your Nexset is sent as a request to the Tavus API. Ensure the record structure matches the format expected by the endpoint. For detailed information about request body formats, see the Tavus API documentation.

[Rest API] Delete Replacement

This endpoint template deletes a replacement from your Tavus account using records from a Nexset.

Each record from your Nexset is sent as a request to the Tavus API. Ensure the record structure matches the format expected by the endpoint. For detailed information about request body formats, see the Tavus API documentation.

[Rest API] Generate Video

This endpoint template generates a new video in your Tavus account using records from a Nexset.

Each record from your Nexset is sent as a request to the Tavus API. Ensure the record structure matches the format expected by the endpoint. For detailed information about request body formats, see the Tavus API documentation.

[Rest API] Delete Video

This endpoint template deletes a video from your Tavus account using records from a Nexset.

Each record from your Nexset is sent as a request to the Tavus API. Ensure the record structure matches the format expected by the endpoint. For detailed information about request body formats, see the Tavus API documentation.

[Rest API] Rename Video

This endpoint template renames an existing video in your Tavus account using records from a Nexset.

Each record from your Nexset is sent as a request to the Tavus API. Ensure the record structure matches the format expected by the endpoint. For detailed information about request body formats, see the Tavus API documentation.

[Rest API] Create Face

This endpoint template creates a new face in your Tavus account using records from a Nexset.

Each record from your Nexset is sent as a request to the Tavus API. Ensure the record structure matches the format expected by the endpoint. For detailed information about request body formats, see the Tavus API documentation.

[Rest API] Delete Face

This endpoint template deletes a face from your Tavus account using records from a Nexset.

Each record from your Nexset is sent as a request to the Tavus API. Ensure the record structure matches the format expected by the endpoint. For detailed information about request body formats, see the Tavus API documentation.

[Rest API] Rename Face

This endpoint template renames an existing face in your Tavus account using records from a Nexset.

Each record from your Nexset is sent as a request to the Tavus API. Ensure the record structure matches the format expected by the endpoint. For detailed information about request body formats, see the Tavus API documentation.

Manual configuration

Tavus destinations can also be manually configured to send data to any valid Tavus API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Tavus APIs typically expect JSON format for most operations. For operations that act on a specific object, include the object's identifier in the endpoint URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Tavus endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Tavus endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.