The X scheduling API

Create an X post with one HTTP call. It joins the same queue the dashboard uses, retries on failure, and reports back what actually went out.

Publish to X

# POST a text-and-media post to your connected X channel
curl -X POST https://api.postwharf.com/v1/posts \
  -H "Authorization: Bearer $POSTWHARF_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Shipping today.",
    "channels": ["ch_your_x_channel"],
    "media": ["med_optional"]
  }'

Schedule it instead

curl -X POST https://api.postwharf.com/v1/posts \
  -H "Authorization: Bearer $POSTWHARF_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"Tuesday drop","channels":["ch_your_x_channel"],"publish_at":"2026-09-01T09:00:00Z"}'

Find your X channel id

curl https://api.postwharf.com/v1/channels \
  -H "Authorization: Bearer $POSTWHARF_KEY"

Each connected account is a channel. The one you want has "platform": "x".

Check what happened

curl https://api.postwharf.com/v1/posts/post_xxx \
  -H "Authorization: Bearer $POSTWHARF_KEY"

The response carries one delivery per channel with its status, the live URL once published, and the error text if it failed. Deliveries are re-checked after publishing, so an X post removed later stops reporting as live.

What X accepts

280 characters, counting one post in a thread. Up to 4 images or 1 video per post — X does not take both in the same post.

Read from the table the API enforces, so a post over 280 is refused when you create it rather than truncated on the way to X.

Worth knowing about X

X bills per post at the API level; link posts cost more than plain text.

Every other network

Instagram · TikTok · LinkedIn · YouTube · Facebook · Threads · Pinterest · Bluesky · Reddit · Telegram · Discord · Snapchat · WordPress