Move from Post Bridge to PostWire in an afternoon

Post Bridge — their docs' example

curl -X POST https://api.post-bridge.com/v1/posts \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "caption": "Hello, world!",
    "scheduled_at": "2026-12-31T23:59:59Z",
    "media": ["media_id"],
    "social_accounts": [1234, 5678]
  }'

From api.post-bridge.com, read Oct 9, 2026. Their docs show this body inside a JavaScript fetch() with variables (scheduledAt, media_id, accountIds); here as cURL with sample values in their place.

PostWire — REST (the converter's output, with instagram and linkedin ticked)

curl -X POST https://postwire.io/api/schedule \
  -H "Authorization: Bearer $POSTWIRE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "platforms": [
    "instagram",
    "linkedin"
  ],
  "text": "Hello, world!",
  "run_at": "2026-12-31T23:59:59Z"
}'

your key from the pasted command is not carried over: the output uses $POSTWIRE_API_KEY social_accounts (Post Bridge account IDs) → brand_id: create one PostWire brand per client (POST /api/brands) and send its id; with a single brand you can leave brand_id out media are Post Bridge media IDs: upload the files to PostWire (POST /api/media/upload-url) or pass public URLs in "media"

PostWire — n8n node

PostWire node
  Resource:   Post
  Operation:  Schedule
  Networks:   instagram, linkedin
  Content:    Same Text on Every Network
  Text:       Hello, world!
  When:       At a Specific Time
  Publish At: 2026-12-31T23:59:59Z
  Options → Brand: the client's brand

PostWire — MCP (Claude, ChatGPT, any agent)

schedule_post({
  "platforms": [
    "instagram",
    "linkedin"
  ],
  "text": "Hello, world!",
  "run_at": "2026-12-31T23:59:59Z"
})

# or ask your agent: "Schedule this on Instagram and LinkedIn for 2026-12-31T23:59:59Z"