How do I authenticate with the TAP API?

Issue a scoped API key from /settings/api-keys inside your workspace. Keys are workspace-bound, scope-limited, and stored as SHA-256 hashes. Pass it as a Bearer token on every request: Authorization: Bearer tap_ak_live_... The plaintext key is shown once at creation.

What API scopes are available?

Available scopes include contacts:read/write, campaigns:read/write, pitches:read/write, outcomes:read/write, webhooks:read/write, skills:read/write, artists:read/write, outreach:read/write, approvals:read, agents:read/write, actions:read, workspace:write, enrich, and validate. Requests without a permitted scope return a 403 with a structured error identifying the missing scope.

Does TAP have an MCP server?

Yes. Install it with npx -y @totalaudiopromo/tap-mcp@latest. It exposes the same surface a human operator uses (45 tools across campaigns, contacts, pitches, and analysis), scoped to your workspace, and works with Claude Desktop, Cursor, Continue, and any Model Context Protocol client. MCP server install is available with a release pack.

Does TAP support webhooks?

Yes. Subscribe a URL to campaign, pitch, and coverage events from /settings/webhooks. Payloads are signed (verify the X-TAP-Signature header), retried on 5xx, and configurable per workspace. Events include campaign.created, pitch.sent, pitch.replied, pitch.bounced, and coverage.logged. Webhooks are available with a release pack.

Developers

Build on the TAP API, MCP server, and webhooks

The TAP developer surface is a 38-endpoint REST API, a 45-tool MCP server, signed webhooks, and a published OpenAPI spec, all scoped to your workspace and authenticated with scoped API keys.

TAP now has more than a static API page. The public API, MCP server, transcript hub, and assistant layer are becoming one developer surface. Use this page to find what is shipped now and what is still only foundation work.

Building an integration for TAP? This page is for you. Connecting the agent you already use to your TAP workspace is a different job, and has its own page.

Try the API live Read OpenAPI View pricing

REST API

Ship contact, campaign, webhook, and transcript flows from the same surface your operators use.

MCP Server

Give agents first-class access to campaign memory, action queues, and pitch tooling without scraping the UI.

Transcript Hub

Route Meet, Zoom, Granola, Drive, and manual transcripts into one canonical memory layer.

Radio Plays Bridge

Import deduplicated, WARM-backed radio plays through the radio import route.

Explorer

Explore the live surface area

Search the shipped API, MCP tooling, examples, and machine-readable endpoints from one place. This is the fastest way to figure out what is ready now versus what still belongs in roadmap copy.

Browse workspace, contact, and release endpoints.

27 matches

Contacts

GET

/api/v1/contacts

List contacts with pagination and search

contacts:read

POST

/api/v1/contacts

Import up to 500 contacts with validation

contacts:write

GET

/api/v1/contacts/{id}

Get a single contact with full details

contacts:read

DELETE

/api/v1/contacts/{id}

GDPR-compliant contact erasure

contacts:write

POST

/api/v1/contacts/validate

Batch email validation (up to 100)

validate

POST

/api/v1/contacts/enrich

AI enrichment with 14 data points per contact

enrich

Campaigns

GET

/api/v1/campaigns

List campaigns with status and artist filters

campaigns:read

POST

/api/v1/campaigns

Create a new PR campaign

campaigns:write

GET

/api/v1/campaigns/{id}

Get campaign details with stats

campaigns:read

PATCH

/api/v1/campaigns/{id}

Update campaign fields

campaigns:write

GET

/api/v1/campaigns/{id}/contacts

List contacts linked to a campaign

campaigns:read

POST

/api/v1/campaigns/{id}/contacts

Add up to 200 contacts to a campaign

campaigns:write

GET

/api/v1/campaigns/{id}/pitches

List pitch drafts for a campaign

campaigns:read

POST

/api/v1/campaigns/{id}/pitches

Generate AI pitch drafts

campaigns:write

GET

/api/v1/campaigns/{id}/outcomes

List outcomes for a campaign

campaigns:read

POST

/api/v1/campaigns/{id}/outcomes

Log an outcome against a campaign contact

campaigns:write

Outcomes

GET

/api/v1/outcomes

List outcomes with campaign/contact filters

campaigns:read

POST

/api/v1/outcomes

Log a campaign outcome

campaigns:write

GET

/api/v1/outcomes/{id}

Get a single outcome record

campaigns:read

PATCH

/api/v1/outcomes/{id}

Update an outcome record

campaigns:write

Workspace

GET

/api/v1/actions

Get prioritised action queue for active campaigns

campaigns:read

GET

/api/v1/webhooks

List registered webhooks

webhooks:read

POST

/api/v1/webhooks

webhooks:write

DELETE

/api/v1/webhooks/{id}

Remove a webhook registration

webhooks:write

GET

/api/v1/keys

List API keys for your workspace

session

POST

/api/v1/keys

Generate a new API key

session

DELETE

/api/v1/keys

Revoke an API key

session

Need the workflow layer, transcript adapters, or the monitoring bridge mapped out first? Start with the machine-readable docs and the shipped routes on this page.

Open OpenAPI

Scoped keys

Issue a key, scope it, hand it to your agent

Every API key on TAP is workspace-bound and scope-limited. Keys are stored as SHA-256 hashes only. Issue, rotate, and revoke from /settings/api-keys inside the workspace. The plaintext key is shown once at creation.

Create a key

Available scopes: contacts:read, contacts:write, releases:read, releases:write, pitches:write, skills:write, approvals:read, enrich, validate.

# Issue from the workspace UI (recommended)
# /settings/api-keys -> "Create key"
# Name: Agent Production
# Scopes: contacts:read, releases:read, pitches:write
# Expires: 90 days (rotate before expiry)

# Returned format (shown once):
# tap_ak_live_1a2b3c4d5e6f...

# Use as Bearer token on every request:
curl https://totalaudiopromo.com/api/v1/campaigns \
  -H "Authorization: Bearer $TAP_API_KEY"

Scope enforcement

Requests without a permitted scope return 403 with a structured error identifying the missing scope.

# Example: key with only contacts:read
curl -X POST https://totalaudiopromo.com/api/v1/contacts \
  -H "Authorization: Bearer $TAP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email":"[email protected]"}'

# 403 Forbidden
# {
#   "error": "scope_missing",
#   "required_scope": "contacts:write",
#   "key_scopes": ["contacts:read"]
# }

Scoped keys are available with a release pack. See what's included.

MCP server

Install `tap-mcp` once. Drive the workspace from any agent.

The TAP MCP server exposes the same surface a human operator uses, scoped to your workspace. Works with Claude Desktop, Cursor, Continue, and any Model Context Protocol client. Auth is the same scoped key issued above.

One-command install

Published to npm. No clone, no build.

# Run on demand
npx -y @totalaudiopromo/tap-mcp@latest

# Or install globally
npm install -g @totalaudiopromo/tap-mcp

# Required env
export TAP_API_KEY="tap_ak_live_..."
export TAP_WORKSPACE_ID="ws_..."   # optional, defaults to key's workspace

Claude Desktop config

Add to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS.

{
  "mcpServers": {
    "tap": {
      "command": "npx",
      "args": ["-y", "@totalaudiopromo/tap-mcp@latest"],
      "env": {
        "TAP_API_KEY": "tap_ak_live_..."
      }
    }
  }
}

Full tool list (30+ tools across releases, contacts, pitches, analysis) lives in the npm package README. MCP server install is available with a release pack.

Skills

House rules an agent can read before it acts

Skills are the workspace’s editable house rules. Fork the default seed, edit the body, diff against the seed, and version it. Every release agent reads the Skills before it drafts a single pitch.

Drive skills from your agent

Fork, run, and inspect over MCP or REST. UI editor lives at /settings/skills.

# List skills in the workspace (MCP)
tap_list_skills

# Fork the seed into an editable workspace copy
tap_fork_skill { "slug": "contact-research" }

# Run it, output queues for review, never sends
tap_run_skill { "slug": "contact-research", "input": { "campaign_id": "…" } }

# Same over REST
GET  /api/v1/skills
POST /api/v1/skills/contact-research/run

Agent discovery endpoint

Public well-known endpoint advertises the workspace skills surface to any client.

curl https://totalaudiopromo.com/.well-known/agent-skills

# 200 OK
# {
#   "$schema": "https://agentskills.io/schemas/v0.2.0/index.json",
#   "skills": [
#     { "name": "contact-enrichment", "type": "instructions",
#       "url": ".../agent-skills/contact-enrichment/SKILL.md",
#       "sha256": "…" },
#     …
#   ]
# }

Webhooks

Push release and pitch events to your stack

Subscribe a URL to release, pitch, and coverage events. Signed payloads, retry on 5xx, configurable per workspace. Manage from /settings/webhooks.

Example payload

Verify the X-TAP-Signature header against your endpoint secret before trusting the payload.

POST /your-endpoint
Content-Type: application/json
X-TAP-Signature: t=<unix-ts>,v1=<hex hmac-sha256 of "<ts>.<body>">
X-TAP-Event: pitch.replied

{
  "event": "pitch.replied",
  "workspace_id": "ws_...",
  "data": {
    "pitch_id": "p_...",
    "contact_id": "c_...",
    "campaign_id": "cmp_...",
    "reply_classification": "positive",
    "received_at": "2026-05-16T10:42:00Z"
  }
}

Webhook events: release.created, pitch.sent, pitch.replied, pitch.bounced, coverage.logged. Webhook subscriptions are available with a release pack.

Included in a release pack

Drive your workspace from anywhere

A release pack opens the doors, so the same workspace can be driven by an agent or by your own scripts as well as through the app. Scoped API keys, MCP server install, webhooks, the skill editor with version history, and the journalist and radio database.

See what's included Get started

Quick start

Start from the common workflows

These are the routes that matter first: getting data in, creating releases, giving agents access, and importing WARM-backed radio plays.

List contacts

Fetch the first 10 matching contacts from the REST API.

curl -H "Authorization: Bearer tap_ak_your_key" \
  "https://totalaudiopromo.com/api/v1/contacts?limit=10&search=BBC"

Create a campaign

Open a draft campaign and start attaching assets and contacts.

curl -X POST \
  -H "Authorization: Bearer tap_ak_your_key" \
  -H "Content-Type: application/json" \
  -d '{"name":"Spring Release","artist_name":"Artist Name"}' \
  "https://totalaudiopromo.com/api/v1/campaigns"

Ingest a transcript

Send Google Meet, Zoom, Granola, or manual transcript text into TAP.

curl -X POST \
  -H "Authorization: Bearer tap_ak_your_key" \
  -H "Content-Type: application/json" \
  -d '{"source":"granola","project_id":"<campaign-id>","raw_text":"Call transcript..."}' \
  "https://totalaudiopromo.com/api/transcripts/ingest"

Bridge in WARM plays

Import deduplicated bridge plays while Monitor is still coming online.

curl -X POST \
  -H "Authorization: Bearer tap_ak_your_key" \
  -H "Content-Type: application/json" \
  -d '{"project_id":"<campaign-id>","source":"warm","plays":[{"station_name":"Amazing Radio","play_date":"2026-04-16"}]}' \
  "https://totalaudiopromo.com/api/radio/import"

Machine-readable

Pull the metadata directly

The docs matter, but agents and internal tools should prefer the machine-readable assets that are already available.

Open machine-readable docs

OpenAPI spec

Full API specification in OpenAPI 3.1 format.

llms.txt

Product summary formatted for language models and agents.

llms-full.txt

Extended documentation with implementation detail.

RSS feed

Product updates and blog posts as a feed.

One surface for releases, contacts, and radio plays.

TAP already lets you ingest transcripts, operate releases, and bring in WARM-backed radio plays through the same API, MCP server, and webhooks your operators use.

Start a trial Read OpenAPI