· The SociaMesh team
One result per account, and never green on a guess
Why a SociaMesh post reports every account separately, and what we do when a platform doesn't say whether it published.
When you publish one post to five accounts, you don't get one answer. You get five, and they don't always agree. Bluesky confirms in a second. Instagram is still processing a video. LinkedIn refuses an image. A useful API has to say all of that, separately and plainly.
Every account has its own status
A SociaMesh post carries a result for each account: published with the platform's URL,
failed with a canonical error code and the platform's own code, or one of the in-between states
(publishing, retry_scheduled, pending_provider_confirmation). The post's overall status
(published, partial or failed) is derived from those, never stored on its own.
Green means the platform said yes
We only mark an account published when the platform has confirmed it, with an id we can link to.
Until then it isn't green anywhere: not in the API, not in webhooks, not in the console.
When nobody knows
Sometimes a request reaches the platform and the connection drops before the answer comes back.
The post may be live, or not. We call that unknown_outcome, and we check with the platform before
doing anything else, so a retry never posts twice. Forcing a retry past that is possible, but it's
a person's decision, and it's recorded.
Check before you send
POST /v1/posts/validate runs every platform's rules on your post (text length, media, required
options, scheduling) and lists every problem for every account at once. It's free and writes
nothing. The MCP server tells agents to run it before publishing, every time.