---
name: fathom-install-auth
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
title: fathom-install-auth
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/fathom-install-auth
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/fathom-install-auth`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/fathom-install-auth`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/fathom-install-auth) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/fathom-install-auth`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/fathom-install-auth --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/fathom-install-auth --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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.
