> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gettap.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer API and webhooks

> Read and write Tap leads, notes, and meetings from your own systems, and get notified when they change.

When your tool isn't a supported CRM and [Zapier](https://docs.gettap.co/en/integrations/zapier.md) isn't enough, connect it to Tap directly. The Developer API lets your own systems read and write leads, notes, meetings, and action items; webhooks tell them the moment something changes.

> [!NOTE]
>
> Available on the **Sales Intelligence** plan and up, for **company admins**. Others don't see it; on a lower plan you see *"Connect your systems with the Developer API"* with **View plans**.

Everything lives under **Settings → Developer → API & webhooks**, in four tabs: **API keys**, **Webhooks**, **Usage**, and **Documentation**. The Documentation tab is the full reference for every endpoint and event.

## API keys

**1. Create a key**

Give it a name, choose its permissions, and optionally an expiry date.

**2. Copy the secret**

It's shown **once**: *"Copy it now. You won't be able to see it again."* Store it in your own secrets manager.

**3. Call the API**

Send the key as a bearer token. Your requests act for your company.

A key can read and write **leads**, **notes**, **meetings** — summaries and insights — and **action items**. Two permissions are off unless you choose them: reading full meeting transcripts, and deleting leads.

> [!WARNING]
>
> A key stops working if the admin who created it stops being an admin or leaves the company. Create keys for long-running integrations from an admin account that will stay put, and **Revoke** any key you no longer use.

## Webhooks

Add an `https` address that's reachable from the internet, and pick the events to send to it:

| Event | When it fires |
| - | - |
| `lead.created` | A lead is captured or created |
| `lead.updated` | A lead is edited |
| `lead.deleted` | A lead is deleted |
| `note.created` | A note is added |
| `meeting.completed` | A meeting finishes processing |
| `action_item.created` | A follow-up is added |
| `action_item.updated` | A follow-up changes, including its status |

Each delivery is signed, so your system can check it came from Tap. It carries the IDs of what changed rather than the data itself — fetch the details with your API key. **Send test event** checks your endpoint before you rely on it, and **Rotate signing secret** replaces the secret.

If your endpoint doesn't answer, Tap tries again after 1 minute, 5 minutes, 30 minutes, 2 hours, and 6 hours. After 25 failed deliveries in a row the webhook is **Disabled after repeated failures** — fix the endpoint, then **Re-enable** it. The **Delivery log** keeps every attempt for 30 days, with **Retry** on each.

## Limits

| | Limit |
| - | - |
| Requests per key | 120 a minute |
| Requests per company | 50,000 a month |
| API keys | 10 |
| Webhooks | 5 |

**Usage** shows requests by key over the last 7, 30, or 90 days, and this month's total against your quota.

> [!TIP]
>
> Prefer webhooks to polling. Asking for every lead every minute uses your monthly quota fast; a webhook tells you only when there's something new.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.