Sourcevine API Docs

Turn a public TikTok, Instagram, YouTube, X or Facebook URL into clean JSON, with an API per platform and job, priced per call and timestamped.

What Sourcevine does

Sourcevine gives you an API per platform and job across TikTok, Instagram, YouTube, X and Facebook. You send a public URL; you get back JSON in that platform’s own vocabulary: a TikTok save is a collect, a YouTube follower is a subscriberCount. A metric a platform does not publish is absent rather than a guessed zero.

Every response says how old it is and whether it cost you anything.

It returns public profile and post information only, with no private-account content or contact details. A platform may show a sign-in prompt for public content; public visibility defines the data scope, not the presence of a login screen.

The APIs

One API per platform and job: stats for a post or video, a profile, a page of recent posts, comments and replies, search, hashtags, sounds, trending, and the YouTube transcript. Most take a public URL; search and trending take a keyword or a country. Each answers in that platform’s own vocabulary.

The API reference lists every one, by platform, with its endpoint, input and price, and links to the full reference for each. The same APIs are browsable by job at sourcevine.io/apis.

The original generic endpoints

GET /v1/profile, GET /v1/profile/posts and GET /v1/post still work and still return one normalized shape across platforms. They predate the named APIs and are not going away, but the named ones are what the rest of these docs use.

What makes the responses usable

Explicit nulls. When a platform does not report a metric you get null, not 0. A zero standing in for “unknown” is the single most common way normalized social data misleads people, and we would rather return nothing than something wrong.

No invented equivalence. A TikTok view and an Instagram view are not the same measurement and we never merge them into one canonical social score. Named APIs keep the platform terms visible; legacy generic endpoints keep one normalized shape for older integrations. Both are documented in response shapes.

A timestamp on every object. Every response says when we read the platform, and when the platform itself dated the data where it publishes that.

What it costs

Credits are charged per operation, and each API’s price is on its reference page. A resource that turns out to be deleted or private is a live fetch too, and is charged like one. Full detail in credits & billing.

An empty result is charged the same way. Retrieval failures are never charged.

The API is the source of truth. If something here does not match what a response returns, the API is right and this page is wrong. Please tell us.

Last updated 7 October 2026