Skip to content
SociaMesh

Publish

One request, many accounts, a result for each.

POST /v1/posts
{
  "content": "Fresh bread today",
  "publishNow": true,
  "mediaIds": ["media_…"],
  "platforms": [
    { "platform": "bluesky", "accountId": "acct_…" },
    {
      "platform": "pinterest",
      "accountId": "acct_…",
      "platformSpecificData": { "boardId": "123456" }
    },
    { "platform": "linkedin", "accountId": "acct_…", "content": "A longer version for LinkedIn…" }
  ]
}
  • content is the default text; a target's own content overrides it.
  • platformSpecificData holds each platform's options (board, title, privacy level…). Each platform page lists them.
  • The whole request is validated first, all or nothing: if any account would fail validation, nothing is created and you get 422 with every issue.

Answers

StatusMeaning
200Every account finished within the wait; platforms[] has each result and success says whether all published.
202Still going: { status: "publishing", postId }. Poll GET /v1/posts/{id} or use webhooks.
201A draft or scheduled post was saved.

Per-account results

Each entry in platforms[] has a status (queued, publishing, published, failed, retry_scheduled, unknown_outcome…), platformPostUrl, publishedAt, attempts and, when it failed, an error with a canonical code. A post's overall status is derived from them: published, partial or failed.

Transient platform failures are retried automatically with backoff. When a platform didn't say whether a post went out (unknown_outcome), SociaMesh checks before retrying so nothing is posted twice; POST /v1/posts/{id}/retry with force: true overrides that, on your responsibility.

Change or remove

  • PATCH /v1/posts/{id}: edit a draft or scheduled post.
  • POST /v1/posts/{id}/cancel: stop what hasn't been sent.
  • DELETE /v1/posts/{id}?fromPlatforms=true: remove it, and delete it on the platforms that allow that.