Social Fetch

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; for agent onboarding and crawl rules, use /agents.txt; for the full endpoint list with links to pages like this one, use /llms-endpoints.txt; for one platform's parameters and curls, use /llms-{platform}.txt; use /llms.json when you need structured JSON for tool registration.

This page

• On-site (HTML): https://www.socialfetch.dev/docs
• Markdown (.mdx) URL: https://www.socialfetch.dev/docs.mdx

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, /llms.txt, or /llms.json for each route).
• OpenAPI JSON: https://www.socialfetch.dev/openapi.json

Recommended docs entrypoints (this site)

• Documentation overview — top-level orientation (markdown).
• Quickstart — authenticate with x-api-key, validate auth with whoami, and understand the JSON envelope.
• SDK — official TypeScript SDK guide, including SocialFetchClient, Result, and unwrap().
• Capability matrix — 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 — copyable workflows (brand monitoring, transcripts, Ad Library, creator scoring, Reddit research) with credit callouts and SDK examples.
• Integrations — MCP for AI clients, n8n verified node, Apify Store Actors, Make custom app, SDK, and REST API connection paths.
• MCP product page — hosted MCP overview, OAuth, Skills install.
• MCP integration — hosted /mcp server, OAuth, Cursor/VS Code/Claude install snippets, 910 endpoint tools, plus docs_search/docs_read for implementation help.
• n8n integration — install n8n-nodes-socialfetch, credentials, and workflow examples.
• Apify integration — Store Actors under @social-fetch, PPE billing, dataset export, and quick start.
• Make integration — custom app modules for Make scenarios, API key credentials, and module catalog.
• /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 — per-platform endpoint files generated from OpenAPI (parameters, credits, curls).
• /agents.txt — agent crawl/onboarding file with capabilities, auth rules, and allowlist.
• /llms.json — structured machine-readable operation inventory with parameter names, pagination, outcomes, credits, and SDK mapping.
• API reference hub — human-friendly index of operations with links into generated pages.
• Errors — shared error envelope and HTTP status guidance.
• Credits — metering, 402, and planning batch jobs.
• Outcome semantics such as found, not_found, and private are documented in Errors 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).

---

Documentation (https://www.socialfetch.dev/docs)

Social Fetch is a REST API for normalized social media data. Look up profiles, posts, and engagement metrics across Instagram, TikTok, X/Twitter, YouTube, and more, with one JSON shape and one API key. The same data powers trackers in the Social Fetch app that need no code.

Base URL https://api.socialfetch.dev. Authenticate with the x-api-key: sfk_... header. The spec is at /openapi.json. New here? Start with the Quickstart.

Pick your path

• Quickstart — Make your first authenticated request and learn the response envelope.

• Recipes — Copyable workflows: brand monitoring, transcripts, ads, creator scoring, Reddit research.

• TypeScript SDK — Typed client methods and Result-based error handling instead of raw HTTP.

• API reference — Every operation, with parameters, examples, and response schemas.

• Credits & billing — Which routes cost credits, how to read creditsCharged, and what 402 means.

• Integrations — SDK, MCP, n8n, Apify, x402: connect Social Fetch to your stack.

• Monitors — Check a source on a schedule and get a signed webhook when something new appears.

• X Follower Tracker — Track an X account's followers, see who joined and left, and explore the audience. No code.

• Ad Tracker — Keep every ad a competitor runs on Meta, LinkedIn, Google and TikTok, with weekly changes. No code.

Not sure where to begin? Match your setup:

• Calling the API directly: Quickstart, then Errors, Credits and the API reference.
• Building in TypeScript: Quickstart, then the SDK guide.
• Not writing code: use the trackers in the app, starting with the X Follower Tracker or the Ad Tracker, or build a workflow in n8n.
• Watching a source for changes: set up a monitor and receive webhooks.
• Handing this to a coding agent: connect MCP, or point it at /llms.txt, /agents.txt, /llms.json, and /openapi.json.

The app

Everything above is managed from the Social Fetch app. Sign up free to get credits to try things out.

• Playground: try any endpoint with your own values and see the response before you write code.
• API Keys: create the key you put in the x-api-key header.
• Tools: the Follower Tracker and Ad Tracker, which run on your credits.
• Usage: your credit use and request volume. See Credits.
• Billing: your credit balance and top-ups.
• Team: invite people to your workspace. See Teams and workspaces.

Platform coverage

Every platform returns the same { data, meta } envelope.

• Instagram: profiles, posts, reels, highlights, search
• TikTok: profiles, videos, products, user search
• X/Twitter: profiles, tweets, communities, search
• YouTube: channels, videos, transcripts, playlists, search
• Yelp: paginated business reviews returned directly by the API (source availability varies by review category)
• Fandom: wiki pages with infoboxes, search, page and category listings, article comments, Discussions threads, activity feeds, and recent changes
• Apple App Store: apps by id or bundle id, app details, reviews, in-app purchases, search, developer catalogues and charts
• Behance: profiles and their latest projects, project records with source files, tag assets and services, freelance briefs, and recent and featured project lists
• Dailymotion: videos, video search, comments, transcripts, users, playlists and discovery feeds
• Deezer: tracks and albums with credits, artist discographies, playlists, charts, genres, radio, podcasts, concerts, lyrics and oEmbed embeds
• Dev.to: posts with full bodies, search, comments, profiles, organizations, tags, trends, feeds, videos, podcasts, events and communities
• Discord: invites, public server pages, directory browse and search, the server, game, application and announcement indexes, trending games, games, applications, templates, widgets and announcements
• Dribbble: profiles, shots, collections, services, designers, jobs, stories, project briefs
• Flickr: photos, photographers, albums, galleries, groups, tags, Explore and search
• Google News: search, top stories, topic streams, headlines, publishers, Full Coverage stories, article-link resolution and suggestions
• Google Trends: trending searches, topic suggestions, place and category lists, interest over time and by region, related queries and combined reports
• Gumroad: products, product page details, reviews, related products, call slots, search, suggestions, categories, tags, creators, creator products and posts, posts and comments, wishlists and wishlist items
• Hugging Face: models, datasets, Spaces, papers, collections, repository files, and accounts
• Kick: channels, VODs, clips, gifter leaderboards, channel-point rewards, goals, emotes, live status, the live directory, top gifted streams, search, category groups, top categories, categories, top channels, events, drop campaigns and active chatters
• Ko-fi: creator profiles, posts, comments, membership tiers, supporters, shop items, commissions, gallery items and albums
• Lemmy: instances, communities, posts, comments, users, search and moderation logs
• Letterboxd: film pages, member diaries, reviews, watchlists, lists, followers, tags, statistics and popular members
• Lnk.Bio: profiles, links, link search, and the public profile directory
• Mastodon: profiles, posts, reply trees, hashtag and public timelines, trends, search and server details from any compatible server
• Medium: tag, author and publication feeds, daily post and entity sitemaps
• MyAnimeList: anime and manga titles, cast, statistics, reviews, rankings, seasons, news, public profiles
• npm: packages, versions, downloads, advisories, provenance, dependents, search, users and orgs
• Polymarket: events, markets, order books, prices, price history, trades, holders, profiles, leaderboards, Perps and Polymarket US
• Product Hunt: posts, products, launches, leaderboards, comments, reviews, topics, categories and users
• Shopify: storefront data: products, variants, collections, pages, blogs, search, reviews and pickup availability
• Stack Overflow: questions, answers, comments, users, tags, revisions and citations across the Stack Exchange network
• Stan Store: creator profiles, listed products, full product details, booking availability and the creator directory
• Steam: app details, reviews and review totals, player counts, news, achievements, store search, charts, market prices and the hardware survey
• Substack: publications, posts, comments, readers, Notes, search, categories and the publication directory
• Vimeo: videos, profiles, followers, channels, groups, showcases, search, comments, credits, categories and On Demand titles
• Wikipedia: pages, article content, revisions, links, categories, nearby pages, pageviews, feeds, recent changes, users and Wikidata
• Yahoo Finance: quotes, charts, company statements, analyst and holder data, screeners, calendars, news and earnings-call transcripts
• Facebook, Reddit, LinkedIn, Pinterest, Threads, Bluesky, Twitch, GitHub, Rumble, Spotify, Apple Music, SoundCloud, Snapchat, Telegram, Linktree, Hacker News, Truth Social, Google, Amazon: profiles, posts, and platform-specific lookups
• Web: fetch any page as Markdown or HTML, or ask a question about it
• Query: validate a Boolean query: explain it in English or Spanish, import it from Talkwalker, Brandwatch, Meltwater, Onclusive or X, and see how each platform would search it
• Monitors and webhooks: schedule recurring checks and receive signed deliveries
• Utilities: whoami, balance, and health

See the API reference for every operation and its schema.

Docs for machines

Building with a coding agent or generating client code:

• Append .mdx to any docs URL for the raw Markdown, e.g. /docs/quickstart.mdx.
• /llms.txt: curated discovery index with coverage, why to use it, and workflow-oriented doc links.
• /agents.txt: agent onboarding, auth and pagination rules, and the crawl allowlist.
• /llms-endpoints.txt: every operation with a link to that route's markdown page.
• /llms-{platform}.txt: per-platform files with parameters, credits, and example curls (from OpenAPI).
• /llms.json: structured route inventory with parameters, pagination, outcomes, credits, and SDK mappings.
• /openapi.json: full schema for codegen, validation, and tooling.
• Capability matrix: every operation in one generated table, with identifiers, pagination, outcomes, credits, and SDK method. Prefer /llms.json for agents.