Skip to main content
This example publishes one logical post to two connected accounts. 
curl -s \
  -H "Authorization: Bearer po_live_xxxxx_xxxxx" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: launch-001" \
  -X POST https://postonce.to/api/public/v1/posts \
  -d '{
    "content": "Shipping the public API today.",
    "external_id": "launch-001",
    "targets": [
      { "account_id": "account-1" },
      {
        "account_id": "account-2",
        "content_override": "Shorter version for X"
      }
    ]
  }'

​
What happens next

  • PostOnce creates one aggregate public post
  • the request fans out internally to per-account rows
  • each target is delivered through the same Trigger-backed posting pipeline used by the dashboard

​
Idempotency

Use Idempotency-Key when creating posts so retries do not accidentally create duplicate publish jobs.