Configure Fathom AI meeting assistant API access with API key authentication.
Installable skillMITBy jeremylongshoreUpdated Oct 30, 2026
INTENDED FORClaude CodeInstall in a listed agent.
instructions.md
---
name: fathom-install-auth-bed1a9b0b6c6
description: 'Configure Fathom AI meeting assistant API access with API key authentication.
Use when setting up Fathom API integration, generating API keys,
or configuring webhook access for meeting data.
Trigger with phrases like "install fathom", "setup fathom api",
"fathom auth", "fathom api key", "configure fathom".
'
allowed-tools: Read, Write, Edit, Bash(curl:*), Grep
version: 1.6.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- saas
- meeting-intelligence
- ai-notes
- fathom
compatibility: Designed for Claude Code
---
# Fathom Install & Auth
## Output
- A scoped Fathom credential/integration reference for the intended environment, with a verified low-impact connection test.
- A credential ownership, rotation, and revocation path that protects meeting content and contacts.
## Examples
Configure a development credential from the approved secret manager and verify access against a synthetic meeting/test account, recording only environment and result. If a token appears in code, logs, or support material, revoke it immediately and issue a replacement before further diagnosis.
## Overview
Set up Fathom AI API access for retrieving meeting transcripts, summaries, and action items. The API at `api.fathom.ai/external/v1` uses `X-Api-Key` header authentication with per-user API keys.
## Prerequisites
- Fathom account (free or Team plan)
- API access enabled in Settings
## Instructions
### Step 1: Generate API Key
1. Log in to https://fathom.video
2. Navigate to **Settings** > **Integrations** > **API Access**
3. Click **Generate API Key**
4. Copy and store the key securely
```bash
export FATHOM_API_KEY="your-api-key-here"
# Verify the key works
curl -s -H "X-Api-Key: ${FATHOM_API_KEY}" \
https://api.fathom.ai/external/v1/meetings?limit=1 | jq .
```
### Step 2: Configure Environment
```bash
# .env -- NEVER commit
FATHOM_API_KEY=your-api-key
FATHOM_BASE_URL=https://api.fathom.ai/external/v1
# .gitignore
.env
.env.local
```
### Step 3: Test API Connectivity
```bash
# List recent meetings
curl -s -H "X-Api-Key: ${FATHOM_API_KEY}" \
"https://api.fathom.ai/external/v1/meetings?limit=5" \
| jq '.meetings[] | {id: .id, title: .title, date: .created_at}'
```
### Step 4: OAuth Setup (For Public Apps)
```bash
# For building integrations others will use, register an OAuth app
# at developers.fathom.ai for marketplace listing eligibility
# OAuth apps cannot use include_transcript or include_summary
# in list requests -- use individual recording endpoints instead
```
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| `401 Unauthorized` | Invalid API key | Regenerate in Settings > API Access |
| `403 Forbidden` | Key lacks access | API keys access your meetings + team shared |
| `429 Too Many Requests` | Rate limit (60/min) | Implement backoff |
| Empty meetings list | No recordings yet | Record a meeting first |
## Resources
- [Fathom API Docs](https://developers.fathom.ai)
- [Fathom API Quickstart](https://developers.fathom.ai/quickstart)
- [Fathom Help Center](https://help.fathom.video/en/articles/8368641)
## Next Steps
Proceed to `fathom-hello-world` to retrieve your first meeting transcript.
---
name: fathom-install-auth-bed1a9b0b6c6
description: 'Configure Fathom AI meeting assistant API access with API key authentication.
Use when setting up Fathom API integration, generating API keys,
or configuring webhook access for meeting data.
Trigger with phrases like "install fathom", "setup fathom api",
"fathom auth", "fathom api key", "configure fathom".
'
allowed-tools: Read, Write, Edit, Bash(curl:*), Grep
version: 1.6.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- saas
- meeting-intelligence
- ai-notes
- fathom
compatibility: Designed for Claude Code
---
# Fathom Install & Auth
## Output
- A scoped Fathom credential/integration reference for the intended environment, with a verified low-impact connection test.
- A credential ownership, rotation, and revocation path that protects meeting content and contacts.
## Examples
Configure a development credential from the approved secret manager and verify access against a synthetic meeting/test account, recording only environment and result. If a token appears in code, logs, or support material, revoke it immediately and issue a replacement before further diagnosis.
## Overview
Set up Fathom AI API access for retrieving meeting transcripts, summaries, and action items. The API at `api.fathom.ai/external/v1` uses `X-Api-Key` header authentication with per-user API keys.
## Prerequisites
- Fathom account (free or Team plan)
- API access enabled in Settings
## Instructions
### Step 1: Generate API Key
1. Log in to https://fathom.video
2. Navigate to **Settings** > **Integrations** > **API Access**
3. Click **Generate API Key**
4. Copy and store the key securely
```bash
export FATHOM_API_KEY="your-api-key-here"
# Verify the key works
curl -s -H "X-Api-Key: ${FATHOM_API_KEY}" \
https://api.fathom.ai/external/v1/meetings?limit=1 | jq .
```
### Step 2: Configure Environment
```bash
# .env -- NEVER commit
FATHOM_API_KEY=your-api-key
FATHOM_BASE_URL=https://api.fathom.ai/external/v1
# .gitignore
.env
.env.local
```
### Step 3: Test API Connectivity
```bash
# List recent meetings
curl -s -H "X-Api-Key: ${FATHOM_API_KEY}" \
"https://api.fathom.ai/external/v1/meetings?limit=5" \
| jq '.meetings[] | {id: .id, title: .title, date: .created_at}'
```
### Step 4: OAuth Setup (For Public Apps)
```bash
# For building integrations others will use, register an OAuth app
# at developers.fathom.ai for marketplace listing eligibility
# OAuth apps cannot use include_transcript or include_summary
# in list requests -- use individual recording endpoints instead
```
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| `401 Unauthorized` | Invalid API key | Regenerate in Settings > API Access |
| `403 Forbidden` | Key lacks access | API keys access your meetings + team shared |
| `429 Too Many Requests` | Rate limit (60/min) | Implement backoff |
| Empty meetings list | No recordings yet | Record a meeting first |
## Resources
- [Fathom API Docs](https://developers.fathom.ai)
- [Fathom API Quickstart](https://developers.fathom.ai/quickstart)
- [Fathom Help Center](https://help.fathom.video/en/articles/8368641)
## Next Steps
Proceed to `fathom-hello-world` to retrieve your first meeting transcript.
Platform guidance
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.
When the user wants to understand, reduce, or recover from developer churn. Trigger phrases include "why developers leave," "churn rate," "win-back campaign," "at-risk users," "developer retention," "preventing churn," or "competitor switching."
ClaudeCodexCursorSales
jonathimer/devmarketing-skills contributors, via Agentic Awesome Skills
Uncover the functional, emotional and social jobs a customer hires a product to do: progress state, hiring trigger, alternatives, success criteria, JTBD map. Use when you need to understand why users buy, switch or churn, or to anchor positioning, messaging and onboarding in real jobs.
Hilft bei Anlagenliste Verstehen für Menschen mit Deutsch als Zweitsprache. Erklaert Juristendeutsch, klaert Risiko, Frist und naechste Handlung, und formuliert respektvoll in einfachem oder formalem Deutsch im Juristische Sprache Deutsch Als Zweitsprache.