Skip to main content
Tantra

Integrations · Build and automate

Automate Tantra with account-level API keys.

Create a revocable key, send it in the X-API-Key header, and operate campaigns, contacts, webhooks, and related workflows through the Tantra API. Add prospects to a campaign from your own code, and they enter its omnichannel sequence automatically.

AvailableDeveloper

Requires a Tantra account.

What you get

Add prospects to campaigns

Send prospects to a campaign from your own code with an API key. Each one enters the campaign's sequence automatically, with no CSV upload or manual start.

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 when it is no longer needed.

Rotation through the API

Rotate a key programmatically through the API.

One key per integration

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

How it works

  1. 1

    Create a named API key, with an optional expiry

  2. 2

    Copy the full secret, which is shown once

  3. 3

    Send it in the X-API-Key header on each request

  4. 4

    Add prospects to a campaign from your code

  5. 5

    Revoke or rotate the key when needed

Supported actions and data

Tantra can do

  • Operate campaigns, contacts, webhooks, and related workflows over HTTPS
  • Add prospects to a campaign from your own code
  • Authenticate requests with an X-API-Key header

Tantra receives

  • Prospects added to a campaign from your own code
  • Each response is scoped to the request you made

Requirements and permissions

  • A Tantra account

  • A signed-in browser session for some account-management endpoints

Scope and limits

  • Keys currently authenticate with account-level access. They are not permission-scoped until scope enforcement is implemented and tested.
  • Some account-management endpoints require a signed-in browser session rather than an API key.
  • The full secret is shown once and stored as a hash afterward.
  • Every prospect passes the same suppression, validation, sending-limit and sending-window checks, however it arrives.

REST API questions

Further setup detail is in the help center.

Create an API key.

Automate Tantra operations over HTTPS with revocable, account-level API keys.