Appearance
socialized.dev
Post a video once. Publish it everywhere. 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, four destinations, each with a durable, inspectable status. The dashboard at dash.socialized.dev is just 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.
| Noun | What it is |
|---|---|
| Account | The billing + team boundary. Holds your API keys. |
| Brand | A publishing identity inside the account. Owns the connections and the publications. One account can hold several; it is a required path segment (/brands/{brandId}/…); list brands with GET /brands. |
| Connection | A platform account you've authorized socialized.dev to publish to: a YouTube channel, an Instagram account. At most one per platform, per brand. |
| Asset | An uploaded file (the source video or a cover image), stored once. Account-scoped, so it can be published under any brand. |
| Publication | One "post once": a title, a caption, a cover, and a set of targets. |
| Target | One destination of a publication. Each travels queued → publishing → published, or failed with a reason you can retry. |
What you do, in order
- Get an API key on the Developer page and authenticate every call with it.
- Connect your platform accounts once (an OAuth step, done in the dashboard).
- Upload assets (videos and optional cover images) to the presigned URLs the API returns.
- Publish it to one or more connected destinations with a single call.
- 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.