> **For coding agents and LLMs:** This is one page from the Social Fetch docs (markdown export). For curated orientation and workflow guidance, start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for agent onboarding and crawl rules, use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for the full endpoint list with links to pages like this one, use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt); for one platform's parameters and curls, use [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt); use [`/llms.json`](https://www.socialfetch.dev/llms.json) when you need structured JSON for tool registration. ## This page - **On-site (HTML):** - **Markdown (.mdx) URL:** ## API base URL and authentication - **API origin (from OpenAPI `servers`):** `https://api.socialfetch.dev` - **Authentication:** send `x-api-key: sfk_...` on `/v1/**` and `/v2/**` routes unless the operation is explicitly anonymous (check OpenAPI `security`, the [API reference hub](https://www.socialfetch.dev/docs/api.mdx), [`/llms.txt`](https://www.socialfetch.dev/llms.txt), or [`/llms.json`](https://www.socialfetch.dev/llms.json) for each route). - **OpenAPI JSON:** ## Recommended docs entrypoints (this site) - [Documentation overview](https://www.socialfetch.dev/docs.mdx) — top-level orientation (markdown). - [Quickstart](https://www.socialfetch.dev/docs/quickstart.mdx) — authenticate with `x-api-key`, validate auth with `whoami`, and understand the JSON envelope. - [SDK](https://www.socialfetch.dev/docs/sdk.mdx) — official TypeScript SDK guide, including `SocialFetchClient`, `Result`, and `unwrap()`. - [Capability matrix](https://www.socialfetch.dev/docs/capability-matrix.mdx) — every operation with identifiers, pagination, outcomes, media download, credits, and its SDK method. Generated from OpenAPI, so use it for route selection instead of scanning individual pages. - [Recipes](https://www.socialfetch.dev/docs/recipes.mdx) — copyable workflows (brand monitoring, transcripts, Ad Library, creator scoring, Reddit research) with credit callouts and SDK examples. - [Integrations](https://www.socialfetch.dev/docs/integrations.mdx) — MCP for AI clients, n8n verified node, Apify Store Actors, Make custom app, SDK, and REST API connection paths. - [MCP product page](https://www.socialfetch.dev/mcp) — hosted MCP overview, OAuth, Skills install. - [MCP integration](https://www.socialfetch.dev/docs/integrations/mcp.mdx) — hosted `/mcp` server, OAuth, Cursor/VS Code/Claude install snippets, 264 endpoint tools, plus docs_search/docs_read for implementation help. - [n8n integration](https://www.socialfetch.dev/docs/integrations/n8n.mdx) — install `n8n-nodes-socialfetch`, credentials, and workflow examples. - [Apify integration](https://www.socialfetch.dev/docs/integrations/apify.mdx) — Store Actors under @social-fetch, PPE billing, dataset export, and quick start. - [Make integration](https://www.socialfetch.dev/docs/integrations/make.mdx) — custom app modules for Make scenarios, API key credentials, and module catalog. - [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt) — every documented operation with a direct link to that route's agent-readable markdown page (prefer this over parsing OpenAPI). - [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt) — per-platform endpoint files generated from OpenAPI (parameters, credits, curls). - [`/agents.txt`](https://www.socialfetch.dev/agents.txt) — agent crawl/onboarding file with capabilities, auth rules, and allowlist. - [`/llms.json`](https://www.socialfetch.dev/llms.json) — structured machine-readable operation inventory with parameter names, pagination, outcomes, credits, and SDK mapping. - [API reference hub](https://www.socialfetch.dev/docs/api.mdx) — human-friendly index of operations with links into generated pages. - [Errors](https://www.socialfetch.dev/docs/errors.mdx) — shared error envelope and HTTP status guidance. - [Credits](https://www.socialfetch.dev/docs/credits.mdx) — metering, `402`, and planning batch jobs. - Outcome semantics such as `found`, `not_found`, and `private` are documented in [Errors](https://www.socialfetch.dev/docs/errors.mdx) and on operation pages when present in the OpenAPI contract. ## Markdown docs convention - Every docs page has a markdown twin: append **`.mdx`** to the docs pathname (for example `/docs/quickstart` → `/docs/quickstart.mdx`). - Agents that send `Accept: text/markdown` on `/docs/**` HTML URLs may receive markdown directly (same URL, `Vary: Accept`). - Published blog posts use the same convention: `/blog/{slug}` → `/blog/{slug}.mdx`, or `Accept: text/markdown` on the HTML URL (`Vary: Accept`). --- # X Follower Tracker alerts and exports (https://www.socialfetch.dev/docs/tools/follower-tracker/alerts-and-exports) ## Turn on email alerts Every email alert starts switched off. To choose yours, open the account's **Settings** tab, open **Alerts and goal**, switch on what you want and click **Save settings**. | Setting | What you get | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | **Weekly digest** | An email on Monday morning with the week's new followers, departures and returns. | | **Daily summary** | A short email each morning with the day's changes. | | **Watchlist alerts** | An email after a check when someone on your [watchlist](/docs/tools/follower-tracker/explore-the-audience#keep-a-watchlist) follows or leaves. | | **Growth alert** | An email when one check finds at least this many new followers. Leave it blank for no alert. | | **Departure alert** | An email when one check finds at least this many people who left. Leave it blank for no alert. | The digest and summary arrive at around 8am UTC (8am London time in winter, 9am in summer) and are sent even when nothing changed, so you know the tracker is still running. They give counts of new followers, departures and returns, and name anyone on your watchlist who changed. With **Weekly digest** or **Watchlist alerts** on, you also get an email when the first check has collected the audience. Emails go to the person who added the account. Each email ends with a link to turn off follower tracker emails. That link turns them off for every tracked account in the workspace, including ones other people added, so in a shared workspace it's better to switch off just the alerts you don't want in each account's **Settings**. ## Set a follower goal **Follower goal**, in the same section, is a number to aim for. The account's page shows how close you are under **Followers**, and says when you reach it. It doesn't send an email. ## Export to CSV Download what the tracker has collected as CSV files, which open in Excel, Google Sheets or Numbers. On the account page, click **Export** and choose one: * **Audience**: everyone who follows the account, with their handle, name, follower count, bio and category. It's available once the first check has collected the audience. * **Change history**: every new follower, departure and return, with their handle and name and the time window when the tracker saw each change. * **Account summary**: the account's follower count, collected audience, profile details and check dates. To export part of the audience, set up filters or open a segment on the **Audience** tab and click **Export CSV** there. The file has just the people you can see. The file is prepared in the background. The **Exports** panel above the tabs shows its progress, then a **Download** button. Each file holds up to 1,000 rows, so a bigger export comes in parts, with a button for each. A few things to know: * Exports never include your private notes, tags or AI labels. Email addresses and phone numbers in bios are masked. * In the change history, handle and name are blank for people whose profile details haven't been collected (for example when the **Profile details** limit was reached). Their X account ID is always there, in the **id** column. * Each export can be downloaded for 24 hours, and only by the person who asked for it. - [Use cases](/docs/tools/follower-tracker/use-cases) — Put alerts and exports to work. - [Troubleshooting](/docs/tools/follower-tracker/troubleshooting) — Exports that don't arrive, and more.