Repository navigation
add Fathom API doc to engine/ - #2
Merged
Merged
Conversation
Owner
|
Hey bud, sorry I'm only seeing this now. I do have a Fireflies API script in there, but I have used Fathom and it's just as easy, so happy to merge this and share it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
engine/fathom.md — a tool doc for Fathom's public API, following the same structure as apollo.md and apify.md.
GTM problem it solves
Fathom is the easiest way for an individual GTM operator to get programmatic access to their own call transcripts. Unlike most conversation intelligence platforms, the API is available on the free tier with no admin gate, so individual ICs can start building per-account intelligence workflows without waiting on procurement.
The doc covers:
Auth, endpoints, and a batch pull pattern that filters meetings by company domain
Four GTM use cases: per-account intelligence (CSM account wiki), churn signal detection, objection pattern mining, and handoff briefings
The MCP endpoint for Claude Code integration
Rate limiting, pagination, and known gotchas
Why Fathom first
I started with Fathom rather than Gong because the individual-API-key access makes it approachable for ICs and smaller teams. Gong, Chorus, Fireflies, etc. could follow the same pattern in future docs.
Validation
Tested against Fathom's live API with an active account. Response shape, auth header format, and pagination behavior match what's documented above.