Build and automateAvailableDeveloper

Automate Tantra with account-level API keys.

Create a revocable key, send it in the X-API-Key header, and use the supported Tantra API to operate campaigns, contacts, webhooks, and related workflows.

Create an API key Read setup guide

Requires a Tantra account.

What you get

Named keys with optional expiry

Create a named API key with an optional expiry date.

Shown once, stored as a hash

The full secret is shown once at creation and stored as a hash afterward.

Key prefixes

Identify a key by its prefix without needing the full secret.

Immediate revocation

Revoke a key immediately if it's no longer needed.

API-supported rotation

Rotate a key through the API without waiting on manual support.

One key per integration

Use a dedicated key per integration and authenticate with the X-API-Key header.

How it works

Step 1
Create a named API key
Step 2
Copy the full secret, shown once
Step 3
Send it in the X-API-Key header
Step 4
Revoke or rotate it when needed

API keys

Supported actions and data

Tantra can do

Operate campaigns, contacts, webhooks, and related workflows over HTTPS
Authenticate requests with an X-API-Key header

Tantra receives

No data flows back automatically; each response is scoped to the request you made

Requirements and permissions

A Tantra account
An interactive Clerk session for some account-management endpoints

Good to know

Keys currently authenticate with account-level access. They are not permission-scoped until scope enforcement is implemented and tested.
Some account-management endpoints require an interactive Clerk session rather than an API key.
The full secret is shown once and stored as a hash afterward.

Frequently asked questions

Are API keys scoped to specific permissions?: Not currently. Keys authenticate with account-level access; treat any key as able to reach every route until scope enforcement ships.
What happens if I lose my key?: The full secret is shown only once at creation. Revoke it and create a new one if it's lost.
Can I use one key across multiple integrations?: You can, but a dedicated key per integration makes it easier to revoke one connection without affecting others.