How do I thread multiple tweets together?

Use the post-level `thread` field: `{ segments: [{ content, mediaIds }, …] }`, 2–50 entries. Segment 0 is the head tweet and every later segment replies to the one before it — the top-level `content` field is ignored in favor of `segments` on thread-capable platforms (X and Threads).

Post a tweet to X via API — SkedCast developer guide

Browse docs

6 min read

Before you publish#

You need one already-connected account for the platform. Connect it yourself in the Agency Console, or — if a client owns the account — mint a self-serve connect link with POST /clients/:id/connect-invites and send it to them; they authorize from that page without ever getting a SkedCast login.

GET /v1/accounts lists what's connected, with each account's id — that id is what you pass in targets.accountIds below.

Compose and schedule#

bash

curl -X POST https://api.skedcast.com/v1/posts \
  -H "Authorization: Bearer sked_live_YOUR_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "<clientId>",
    "content": "Launch day is here 🚀",
    "mediaIds": ["<mediaAssetId>"],
    "targets": { "mode": "selection", "accountIds": ["<xAccountId>"] },
    "schedule": { "type": "at", "scheduledAt": "2026-07-01T15:00:00Z" }
  }'

A minimal x post, scheduled for a specific time.

The X API fields to post a tweet#

Everything platform-specific goes in one variants entry with "platform": "x" and an overrides object. The adapter reads only the keys it declares (below) and ignores the rest — send x keys on a x variant, nothing more.

Field	Type	Values / default	Notes
`quoteTweetId`	string	—	Quote a tweet id.
`replySettings`	enum	`following` \\| `mentionedUsers` \\| `subscribers` \\| `verified`	Omit for X's default (everyone can reply).
`madeWithAi`	boolean	`false`	Discloses AI-generated/altered media — independent of the post-level `aiDisclosure` field.
`paidPartnership`	boolean	`false`	Discloses a paid partnership / branded content.
`firstComment`	string	—	Costs one extra API call against the account's budget. Posted right after publish. Best-effort: a failed comment never fails the post and is not reported, so verify on the published post.

Verbatim from the REST API reference's X table.

With the platform-specific overrides#

json

{
  "clientId": "<clientId>",
  "content": "Shipped: bulk import now handles 5,000-row CSVs.",
  "mediaIds": [],
  "targets": { "mode": "selection", "accountIds": ["<xAccountId>"] },
  "variants": [
    { "platform": "x", "overrides": { "replySettings": "following" } }
  ],
  "schedule": { "type": "at", "scheduledAt": "2026-07-01T15:00:00Z" }
}

The same POST /posts body, with a variants entry added.

Checking the result#

Publishing fans out into one post target per account. GET /post-targets/:id (or GET /posts/:id) reports status, plus externalId (x's own post id) and permalink (its public URL) once published. Subscribe to the target.published / target.failed webhooks instead of polling if you can accept inbound HTTP — see the webhooks guide.

xtwitterapipublish

FAQ

How do I thread multiple tweets together?: Use the post-level `thread` field: `{ segments: [{ content, mediaIds }, …] }`, 2–50 entries. Segment 0 is the head tweet and every later segment replies to the one before it — the top-level `content` field is ignored in favor of `segments` on thread-capable platforms (X and Threads).

How to post a tweet to X through the SkedCast API