Browse docs
What a unified social media API actually unifies#
Building against ten platforms directly means ten OAuth implementations, ten rate-limit regimes, ten media-upload flows, and ten ways of reporting an error. A unified API like SkedCast's collapses that to one: one Bearer auth scheme (API key or OAuth 2.1), one keyset pagination convention, one RFC 9457 error shape, one presign → upload → register media flow, and one compose endpoint (POST /v1/posts) that fans out to every destination you name.
- One auth model — API keys or OAuth 2.1, never a separate app registration per platform.
- One compose call — a single POST /v1/posts with a targets array, not ten platform-specific create-post calls.
- One media pipeline — upload once, publish to as many platforms as the asset has renditions for.
- One event stream — webhooks with one signature scheme, regardless of which platform fired the event.
What stays platform-specific, on purpose#
A real difference — TikTok's mandatory privacyLevel, Pinterest's required boardId, YouTube's video title — is a difference the underlying platform enforces, not one a unifying layer can paper over honestly. SkedCast's approach: keep those in a per-platform variants[].overrides object, typed and documented per platform, rather than inventing a fake lowest-common-denominator field that quietly drops functionality.
{
"clientId": "<clientId>",
"content": "Same caption, different platforms.",
"mediaIds": ["<mediaAssetId>"],
"targets": { "mode": "selection", "accountIds": ["<tiktokAccountId>", "<pinterestAccountId>"] },
"variants": [
{ "platform": "tiktok", "overrides": { "privacyLevel": "PUBLIC_TO_EVERYONE" } },
{ "platform": "pinterest", "overrides": { "boardId": "<boardId>" } }
],
"schedule": { "type": "at", "scheduledAt": "2026-07-01T15:00:00Z" }
}Where SkedCast's /v1 draws the line#
FAQ
- Does a unified API mean every platform has the same features?
- No — a unified API means one contract for the parts that are genuinely common (auth, pagination, errors, media, events). Platform-specific capability (TikTok's privacy levels, YouTube's category taxonomy) stays platform-specific because it's real, not an artifact of bad API design.
- Is a unified API just a thin wrapper that loses functionality?
- It depends on the implementation. The test is whether platform-specific fields are still reachable — SkedCast's `variants[].overrides` keeps every documented per-platform field available rather than only exposing a shared subset.
- Is a unified social media API the same as a social media API aggregator?
- Yes — "social media API aggregator" and "unified social media API" describe the same idea: one API for all social networks instead of a separate integration per platform. SkedCast's POST /v1/posts is that one call, with platform-specific fields isolated to a variants[].overrides object per network.
- Can I use the unified social media API from Python?
- Yes — it's a standard REST API (JSON over HTTPS), so any HTTP client works, including Python's requests or httpx. There's no dedicated Python SDK yet; the official SDK is TypeScript, documented on the SDK page.