Social data API for developers

One API key and one response shape for TikTok, Instagram, YouTube, X, LinkedIn, Reddit and more.

6 endpointsTikTok, Instagram, YouTube, X, LinkedIn

RequestGET · cURL
curl -sS \
-H "x-api-key: YOUR_API_KEY" \
"https://api.socialfetch.dev/v1/tiktok/profiles/nasa"

Is there one API for all the major social media platforms? Social Fetch is one. A single API key covers TikTok, Instagram, YouTube, X, LinkedIn, Reddit and more, and every response has the same envelope: data, plus meta with the request ID and creditsCharged. There is a typed TypeScript SDK, an OpenAPI spec and an MCP server, and you pay per call.

A real run. Measured and priced.

One account, three networks, one response shape, run on 21 Nov 2026 against live public data. Three calls with one key, and every response carried the same envelope: the data, plus a meta block with the request ID and credits charged.

  1. 01 GET /v1/tiktok/profiles/nasa

    Found: 2,211,981 followers and 70 videos.

    1 credit, 1.8 s

  2. 02 GET /v2/instagram/profiles/nasa

    Found: 104,277,920 followers and 5,018 posts.

    1 credit, 1.6 s

  3. 03 GET /v1/youtube/channel?handle=NASA

    Found: 15,100,000 subscribers and 6,205 videos.

    1 credit, 2.2 s

Credits
3
3 calls
Starter pack
$0.042
$14 per 1,000 credits
Scale pack
$0.0049
$1.64 per 1,000 credits
Runtime
5.6 s
Server time, calls one after another

Credits are each route's published price. Dollar figures are those credits at the list rate of each pack. Results and times are from the calls above, made on 21 Nov 2026; live data changes, so a run today returns newer numbers.

What usually breaks first

Where a home-built scraper or a marketplace API tends to fail once it runs in production.

  • Every platform's own API is different

    Its own auth, its own app review, its own rate limits and its own field names. Some have no public API at all, and home-made scrapers break when the page changes.

  • Five APIs, five of everything

    Gluing five of them together means five clients, five error formats and five bills.

  • You need one client

    The same auth header, the same envelope, the same error codes and one balance, whichever network the data comes from.

The routes. 6 for this job.

The routes teams call for this job on TikTok, Instagram, YouTube, X, and LinkedIn. Each one links to its reference page, with every parameter and field.

Full API reference

5 steps. How teams wire it up.

The usual order. Change the schedule, schema and thresholds to fit your stack.

  1. Step 1: Get a key

    Sign up, copy your API key and send it in the x-api-key header on every request.

  2. Step 2: Install the SDK or use the spec

    The TypeScript SDK types every route. In other languages, generate a client from the OpenAPI spec or call the REST routes directly.

  3. Step 3: Branch on lookupStatus

    A lookup that finds nothing answers not_found rather than failing, so a missing account doesn't look like an outage.

  4. Step 4: Handle errors once

    Errors share one shape and one set of codes on every route. Errors lists them, with which ones to retry.

  5. Step 5: Watch your spend

    Each response's meta.creditsCharged says what the call cost. Log it with your own job id.

Why developers pick Social Fetch

  • 87 platforms on one key

    No app review per platform and no OAuth dance.

  • One envelope

    data and meta on every route, and lookupStatus on lookups, so one parser covers them all.

  • No requests-per-second cap on paid calls

    Your balance is the limit, with a cap on requests in flight; rate limits has the details.

  • Pay per call

    Looking up one account on TikTok, Instagram and YouTube is 3 credits.

  • You only pay for completed lookups

    Requests that fail on our side cost nothing.

Common questions

Is there one API for all the major social media platforms?

Social Fetch covers TikTok, Instagram, YouTube, X, LinkedIn, Reddit and more with one API key and one JSON envelope, and comes with a TypeScript SDK, an OpenAPI spec and an MCP server.

Do I need each platform's developer approval?

No. Social Fetch returns public data with your Social Fetch key, so there is no app review on each platform.

What happens when an account doesn't exist?

The call returns a normal response with lookupStatus: not_found, so your code can branch on it instead of catching an error.

Is there an SDK?

Yes: the TypeScript SDK, on npm as @socialfetch/sdk. Calls cost the same credits as the raw API.

Start on free credits. Make your first request.

Sign up and get 100 credits, no card needed. Run the request above, then buy more when you need them. Credits never expire.