Publish a post - Postinger

Check the destination

Read GET /accounts/ACCOUNT_ID/capabilities or run postinger accounts capabilities ACCOUNT_ID. Confirm the account is available and prepare content within its platform-specific rules.

Create a draft with targets

Upload media first and use its ID, not its URL, in mediaIds. Save this body as post.json, replacing the example UUIDs:

{
  "content": "A new update",
  "targets": [
    {
      "socialAccountId": "11111111-1111-4111-8111-111111111111",
      "options": { "format": "feed" }
    }
  ],
  "mediaIds": ["22222222-2222-4222-8222-222222222222"]
}

postinger posts create --file post.json --idempotency-key campaign-draft-001

The array order of mediaIds determines carousel order. An optional target contentOverride replaces the common caption for that account. The example’s feed option is for a feed-capable account; other platforms have different options.

Request publication

postinger posts publish POST_ID --yes --idempotency-key campaign-publish-001
postinger posts get POST_ID

The equivalent HTTP operation is POST /posts/POST_ID/publish, optionally with {"socialAccountId":"ACCOUNT_ID"} to select one target. A 202 response means accepted; data.targets is the number of targets queued.

Interpret the outcome

Post status	Meaning
`draft`	Saved, not scheduled
`scheduled`	Waiting for its scheduled time
`publishing`	Publication is in progress
`published`	Publication completed successfully
`partial`	Some targets succeeded and others failed
`failed`	Publication failed

Inspect targets[].status, error, waitReason, and nextAttemptAt. A platform can reject content after initial validation. Verify target results before retrying an uncertain publication. Deleting a Postinger post does not guarantee removal of copies already published on social platforms.