1. Choose whose key to use
A Fathom API key belongs to the user who makes it, and reads what that user can view in Fathom: the meetings they recorded and the meetings shared with them or their team. A meeting that is private to the person who recorded it stays out of reach of every other user’s key. So make the key as a Fathom admin who has view access to all shared calls (in Fathom, an admin sets this under the user’s permissions). Then share the meetings Neo should act on with a team, for example your client calls and your internal leadership meetings.2. Make the API key
In Fathom, open User Settings → API Access, generate an API key, and copy it. Keep it out of email and chat: anyone who has it can read the meetings it sees. Neo calls Fathom athttps://api.fathom.ai with the key in the X-Api-Key header.
3. Add the key in Neo
1
Open Integrations
In the Neo Dashboard, open Integrations and find the Fathom card, under Customer Success.
2
Save the key
Paste the API key and click Save settings. Neo checks it against Fathom before saving, so a wrong or revoked key is rejected straight away.
4. Turn Fathom on per agent
Open the agent, go to the Integrations section, and pick an access profile for the Fathom block, or set each area yourself:
See Fathom API for the profiles and what the agent can read.