Fathom
DOCS & KNOWLEDGE · FILES & DOCS
Recorded meetings, transcripts, summaries, and action items from their own account.
Connecting Fathom in practice
Fathom allows a maximum of 60 API calls in any 60-second window per account, and the calls that matter cost more: recording downloads are 30 per 60 seconds and heavy requests drop to 5 per 60 seconds during periods of high activity. Keys are per user with no org-level key, and an OAuth app cannot pass include_summary or include_transcript on /meetings at all.
Scopes that draw scrutiny
include_transcript / include_summary on /meetingsThe full transcript and the meeting summary are opt-in parameters, and Fathom states OAuth apps cannot use them on /meetings — so an installed integration has to fetch them another way while a user-held API key can ask directly.API key (User Settings → API Access)Per-user only: Fathom documents no org-level keys, so an integration is scoped to the meetings of whichever employee generated the key, and it dies with them.
Rate limits
- A maximum of 60 calls to the API in a 60-second window.
- Heavy requests: 30 calls per 60 seconds, reduced to 5 per 60 seconds during high activity.
- Recording downloads: 30 calls per 60 seconds.
- OAuth token endpoint: 60 requests per 60 seconds per app.
- Limits are per account (per API key or OAuth token), and Fathom does not offer standard increases.
- Rate-limited endpoints return RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset and Retry-After headers.
Worth knowing
- The default page size is 10 meetings, so a month of calls is a long cursor walk inside a 60-request-per-minute budget.
- Transcripts only exist after post-call processing completes, so a webhook-triggered read can legitimately come back without one and has to be retried later.
- Only the account’s default summary template is returned, and only in markdown — there is no way to ask for a second template or for plaintext.
- There is no real-time transcript access, so anything "live" has to be built on the new-meeting-content-ready webhook instead.
Checked against Fathom API overview (2026-09-29), Fathom API FAQ (2026-09-29), Fathom developers (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Fathom behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.