> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/fathom.md). # Fathom Generate a Fathom API key and connect the Appmixer Fathom connector. The Appmixer Fathom connector uses **API key** authentication. You do not need to register an OAuth app. Each user creates a personal API key in their Fathom account and enters it when they connect Fathom in Appmixer. *** ## 1. Generate an API key 1. Log in to [Fathom](https://fathom.video). 2. Open **Settings** (top right) and go to the **API Access** section of your user settings. The direct link is [fathom.video/customize#api-access-header](https://fathom.video/customize#api-access-header). 3. Click **Add**, then **Generate API Key**. 4. Give the key a name (for example `Appmixer`) and create it. 5. Copy the key and store it somewhere safe. {% hint style="info" %} Fathom API keys belong to the user who creates them. A key can read meetings that user recorded, plus meetings shared with them or with their team. It never gives access to other users' private meetings, and that includes admin keys. Connect Fathom with the account whose meetings you want to work with in Appmixer. {% endhint %} The Fathom API reference is at [developers.fathom.ai](https://developers.fathom.ai). *** ## 2. Connect in Appmixer When you add a Fathom component to a flow, Appmixer asks you to connect an account. Paste the key into the **API Key** field. Appmixer sends the key in the `X-Api-Key` header to `https://api.fathom.ai/external/v1`. To check the key, it calls `GET /meetings?limit=1`. Fathom has no profile endpoint, so the connection is named after the user who recorded the most recent meeting. If the account has no meetings yet, the connection is named **Fathom account**. *** ## 3. New Meeting Content Ready trigger You do not need to set up a webhook in Fathom yourself. When a flow with the **New Meeting Content Ready** trigger starts, Appmixer uses your API key to register a webhook in Fathom (`POST /webhooks`) that points at the flow's webhook URL. When the flow stops, Appmixer deletes that webhook. * Turn on at least one of **Include Summary**, **Include Transcript**, **Include Action Items** or **Include CRM Matches**. Fathom rejects the webhook registration if none of them are on. * **Triggered For** controls which recordings fire the trigger. If you leave it empty, it defaults to **My recordings**. * Your Appmixer API must be reachable from the public internet so that Fathom can deliver webhook calls. *** ## Rate limits Fathom limits API usage per user, counted across all of that user's keys: 60 requests per 60 seconds overall, and 30 requests per 60 seconds for heavy endpoints such as meeting summaries and transcripts. Fathom can lower the heavy-endpoint limit when its platform is under load. The connector queues requests to stay under these limits. The List and Find components also stop paginating after a fixed maximum number of items and pages. *** ## Troubleshooting * **401 Unauthorized when connecting:** check that you copied the whole key and that it has not been deleted in **Settings → API Access**. * **A meeting is missing from the results:** the key only sees meetings recorded by its owner or shared with them or their team. Ask the meeting owner to share the meeting, or connect the owner's account. *** ## Backoffice configuration Configuration ID: `appmixer:fathom`. For how to set connector configuration values, see [Connector Configuration](https://docs.appmixer.com/getting-started/services). You do not need any Backoffice configuration to authenticate, because every user enters their own API key. There is one optional key: * `outputFilePrefix`: optional. A prefix for the names of CSV files created when a List or Find component (**List Meetings**, **Find Meetings**, **List Meeting Types**, **List Teams**) runs with the **Store to CSV file** output type. Files are named `-.csv`. The default is `fathom-objects-export`. ```bash appmixer service-config set appmixer:fathom -u -d '{"outputFilePrefix": "fathom-objects-export"}' ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.appmixer.com/connector-configuration/fathom.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.