> **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`). --- # Save and share ads on boards (https://www.socialfetch.dev/docs/tools/ad-tracker/save-and-share-ads) A **board** is a collection of ads you've picked out, sometimes called a swipe file: the hooks worth borrowing, every competitor's Black Friday offers, or the ads to show a client. Boards are free; saving, noting and sharing ads doesn't use credits. ## Save an ad 1. Find an ad on the dashboard, a competitor's page or a board, and hover over its picture. Click the bookmark that appears in the top-left corner. On an ad's own page, click **Save** at the top right. 2. The first time you save an ad, the tracker makes a board called **Saved** and puts the ad on it. 3. Tick the boards you want the ad on, or click **New board**, type a name and click **Create**. 4. Optionally, type in **Note** why it's worth keeping and click **Save note**. A note belongs to the ad, so it shows on every board the ad is on. Only people in your workspace see notes. ## See your boards Click **Boards** at the top of the Ad Tracker. Each board shows a few of its ads, its name and how many ads it has. Click **New board** to make one before you save anything to it; give it a **Name** and, if you like, a **Description** of what the ads have in common. On a board, each ad has its note underneath. Click **Add a note**, or the note, to write or change it. To take an ad off the board, click the bin icon beside its note; **Undo** puts it back. The **⋯** button at the top of a board has **Rename** and **Delete board**. Deleting a board deletes its notes and its share link, but the ads stay in your tracker. ## Share a board Share a board with a client, a colleague or anyone else, without them needing an account. 1. Open the board and click **Share**. 2. Switch on **Share by link**. 3. Click **Copy** and send the link. People who open the link see the board's name and description and its ads, and can click an ad to read its copy, see how long it ran and open it in its library. They don't see your notes, your other boards or anything else in your workspace. A green dot on **Share** shows that the link is on. Switching **Share by link** off breaks the link permanently, for everyone who has it. If you share the board again, it gets a new link, which you'll need to send again. ## Who sees what Boards belong to your workspace. Owners and admins see every board; members see the boards they made. Only the person who made a board, or an owner or admin, can rename, share or delete it. If you remove a competitor, its ads leave your boards too. - [Use cases](/docs/tools/ad-tracker/use-cases) — A swipe file, client reports and more. - [Alerts and exports](/docs/tools/ad-tracker/alerts-and-exports) — Emails, webhooks and CSV files.