← Back to Index

Fathom Ingestion Capability

Status: Read-only access confirmed
API Key: Stored securely in /home/node/.openclaw/credentials/fathom/
Created: Feb 13, 2026


What I Can Access

1. Meetings List

Endpoint: GET /external/v1/meetings

Available Data:

What's NOT in list response:

2. Individual Meeting Details

Endpoint: GET /external/v1/meetings/{recording_id}

Additional Data:

3. Transcript Only

Endpoint: GET /external/v1/recordings/{recording_id}/transcript

Data:

4. Teams

Endpoint: GET /external/v1/teams

Data:


Current Ingestion Status

Tested: Meetings list (working ✅)

Example response:

{
  "title": "ZTAG Twice-Weekly Dev Meeting",
  "url": "https://fathom.video/calls/565027806",
  "recording_id": 122178894,
  "calendar_invitees": ["Quan Gan", "Malachi Burke", etc.],
  "recorded_by": {
    "name": "Quan Gan",
    "email": "quan@ztag.com",
    "team": "Executive"
  },
  "scheduled_start_time": "2026-02-13T04:00:00Z",
  "recording_start_time": "2026-02-13T04:01:32Z"
}

What I Can Build (Ingestion-Only)

Phase 1: Basic Ingestion ✅ Ready

Phase 2: Automated Syncing

Phase 3: Intelligence Layer


Available Filters

Date range:

Participants:

Pagination:

Example:

curl "https://api.fathom.ai/external/v1/meetings?from_date=2026-02-01&to_date=2026-02-13&limit=100" \
  -H "X-Api-Key: [KEY]"

Ingestion Strategy

Daily Batch Sync

Real-Time Webhook (Future)


Trust Model

Current Capability: Read-only (ingestion)

What I CAN do:

What I CANNOT do (by design):

Elevation Path:


Next Steps

Immediate (This Week):

  1. Build Fathom ingestion script
  2. Test full meeting pull (transcript + summary + actions)
  3. Store in structured format
  4. Add to morning briefing

Short-term (Next 30 Days):

  1. Daily batch sync operational
  2. Action item extraction working
  3. Search across meeting history
  4. Webhook integration for real-time

Long-term (3-6 Months):

  1. RAG layer includes meeting transcripts
  2. Proactive follow-up reminders
  3. Meeting prep based on past discussions
  4. Action item tracking automation

Created: Feb 13, 2026
Last tested: Feb 13, 2026 (API access confirmed)