Skip to content

socialized.dev ​

Post once. Know exactly where it went live. socialized.dev takes one uploaded video and fans it out to every platform you publish on (YouTube, Instagram Reels, and Facebook today) behind a single REST API.

It exists because most “post everywhere” tools are dashboards you click. This is infrastructure you build on: one upload, one call, every destination, each with a durable, inspectable status. The dashboard at dash.socialized.dev is the best-known client of the same API.

The shape in one read ​

A publish is five nouns. You will meet all of them in the quickstart.

NounWhat it is
TeamWho you work with. Owns the plan, the API keys and the brands. Every account gets one at its first sign-in.
BrandA publishing identity inside the team. Owns the connections and the publications. One team can hold several; it is a required path segment (/brands/{brandId}/…); list brands with GET /brands.
ConnectionA platform account you’ve authorized socialized.dev to publish to: a YouTube channel, an Instagram account. At most one per platform, per brand.
AssetAn uploaded file (the source video or a cover image), stored once. Team-scoped, so it can be published under any brand.
PublicationOne “post once”: a title, a caption, a cover, and a set of targets.
TargetOne destination of a publication. Each travels pending → processing → published, or failed with a reason you can retry.

What you do, in order ​

  1. Get an API key on the Developer page and authenticate every call with it.
  2. Connect your platform accounts once (an OAuth step, done in the dashboard).
  3. Upload assets (videos and optional cover images) to the presigned URLs the API returns.
  4. Publish it to one or more connected destinations with a single call.
  5. Watch each target settle to live, by polling or by webhook.

Start with the quickstart, publish straight from your terminal with the CLI, or jump to the REST API reference.

The API is the product; the dashboard is its best-known client.