Integrations · Developer
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.
AvailableDeveloper
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
- 1Create a named API key
- 2Copy the full secret, shown once
- 3Send it in the X-API-Key header
- 4Revoke or rotate it when needed
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.