Multi-platform publishing
Text, images, video, threads, carousels and stories, behind one contract.
Publish, schedule and measure posts across social platforms through a single API, without a separate integration for each one.
Publish, schedule and measure posts across social platforms through a single API, without a separate integration for each one.
Each destination settles on its own. Webhooks tell you when each one lands, or why it did not — and nothing is published twice.
const api = 'https://api.postatom.com/v1';const headers = { Authorization: `Bearer ${process.env.POSTATOM_API_KEY}` };const { data } = await (await fetch(`${api}/accounts`, { headers })).json();const receipt = await fetch(`${api}/posts`, { method: 'POST', headers: { ...headers, 'Content-Type': 'application/json' }, body: JSON.stringify({ targets: data.filter((a) => a.publishingAvailable).map((a) => a.id), content: 'We shipped scheduled posts today.', }),}).then((response) => response.json());// Accepted now, answered per destination.const answer = await fetch(`${api}/posts/${receipt.id}`, { headers });const { data: post } = await answer.json(); The parts of a social integration nobody budgets for, built once and kept current.
Text, images, video, threads, carousels and stories, behind one contract.
Queue, reschedule and cancel without running a cron of your own.
Impressions, engagement and follower deltas, in one shape across platforms.
Read threads, reply, hide or delete from a single inbox.
Read and answer Instagram direct messages through a connected Page, with a webhook when a new one arrives.
Hosted consent screens, encrypted token storage, refresh wherever the platform allows it, and a webhook when access lapses.
Workspaces, environments and per-tenant accounts, isolated at the database.
A refused post stops with the platform’s own error kept for you to read, not a silent retry loop.
Scoped to one workspace and one environment. With a test key, posts to sandbox accounts make no network calls.
Send a person to a hosted consent screen. Tokens are encrypted, and refreshed where the platform allows it.
One call reaches every connected platform. Webhooks tell you when each one lands, or why it did not.
Your coding agent can wire PostAtom up on its own. So can you, with one HTTP request.
Drop a skill file into your coding agent. It reads the contract and starts posting, with no wrapper code of yours.
13 tools with schemas a model can call directly, over stdio or HTTP.
An OpenAPI 3.1 spec, idempotency keys on every publish, and typed SDKs Not published yet
13 tools with schemas a model can call directly, over stdio or HTTP. Not published yet
Yes. With a test key, a post to a sandbox account runs the same validation, queueing and status transitions without any network call to a platform.
No. Hosted OAuth connects your end users through PostAtom, so you do not register or maintain an app per platform.
Each destination settles independently. A post that a platform refuses stops with that platform’s own error recorded, while the others continue. Nothing is published twice.
A scheduled time is resolved to an absolute instant when the request is accepted, so a daylight-saving change cannot move it.
Yes. Workspaces and hosted consent are built for connecting your customers’ accounts rather than only your own.
No credit card to start. With a test key, posts to sandbox accounts make no network calls.