Move from Zernio to PostWire in an afternoon

Zernio — their docs' example

curl -X POST https://zernio.com/api/v1/posts \
  -H "Authorization: Bearer $ZERNIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Hello world. This is my first post from the Zernio API.",
    "scheduledFor": "2027-01-01T12:00:00",
    "timezone": "America/New_York",
    "platforms": [
      {"platform": "linkedin", "accountId": "66b2e19d8c3f5a7e9d0b1c2d"}
    ]
  }'

From docs.zernio.com, read Oct 9, 2026.

PostWire — REST (the converter's output)

curl -X POST https://postwire.io/api/schedule \
  -H "Authorization: Bearer $POSTWIRE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "platforms": [
    "linkedin"
  ],
  "text": "Hello world. This is my first post from the Zernio API.",
  "run_at": "2027-01-01T12:00:00-05:00"
}'

your key from the pasted command is not carried over: the output uses $POSTWIRE_API_KEY accountId (a Zernio account) → 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 run_at: the time had no offset and was meant in America/New_York, so -05:00 was added

PostWire — n8n node

PostWire node
  Resource:   Post
  Operation:  Schedule
  Networks:   linkedin
  Content:    Same Text on Every Network
  Text:       Hello world. This is my first post from the Zernio API.
  When:       At a Specific Time
  Publish At: 2027-01-01T12:00:00-05:00
  Options → Brand: the client's brand

PostWire — MCP (Claude, ChatGPT, any agent)

schedule_post({
  "platforms": [
    "linkedin"
  ],
  "text": "Hello world. This is my first post from the Zernio API.",
  "run_at": "2027-01-01T12:00:00-05:00"
})

# or ask your agent: "Schedule this on LinkedIn for 2027-01-01T12:00:00-05:00"