Move from Blotato to PostWire in an afternoon

Blotato — their docs' example

POST https://backend.blotato.com/v2/posts HTTP/1.1
Content-Type: application/json
blotato-api-key: YOUR_API_KEY

{
  "post": {
    "accountId": "98432",
    "content": {
      "text": "This will go live later",
      "mediaUrls": [],
      "platform": "twitter"
    },
    "target": {
      "targetType": "twitter"
    }
  },
  "scheduledTime": "2025-12-25T15:00:00Z"
}

From help.blotato.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": [
    "x"
  ],
  "text": "This will go live later",
  "run_at": "2025-12-25T15:00:00Z"
}'

your key from the pasted command is not carried over: the output uses $POSTWIRE_API_KEY accountId (a Blotato 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 is in the past: PostWire refuses a schedule in the past — set a future time

PostWire — n8n node

PostWire node
  Resource:   Post
  Operation:  Schedule
  Networks:   x
  Content:    Same Text on Every Network
  Text:       This will go live later
  When:       At a Specific Time
  Publish At: 2025-12-25T15:00:00Z
  Options → Brand: the client's brand

PostWire — MCP (Claude, ChatGPT, any agent)

schedule_post({
  "platforms": [
    "x"
  ],
  "text": "This will go live later",
  "run_at": "2025-12-25T15:00:00Z"
})

# or ask your agent: "Schedule this on X for 2025-12-25T15:00:00Z"