x-api

X API Knowledge

Post Creation

X API v2 endpoint for creating posts:

POST https://api.x.com/2/tweets
Authorization: Bearer {access_token}
Content-Type: application/json

{"text": "Hello world"}

With media:

{
  "text": "Check this out",
  "media": {
    "media_ids": ["1234567890"]
  }
}

Authentication

X uses OAuth 2.0 with PKCE (Proof Key for Code Exchange):

• Authorization URL: https://x.com/i/oauth2/authorize
• Token URL: https://api.x.com/2/oauth2/token
• Access tokens expire in 2 hours
• Refresh tokens valid for 6 months (requires offline.access scope)
• The plugin auto-refreshes tokens before each API call

Required scopes: tweet.read tweet.write users.read media.write offline.access

Media Upload

Single-shot upload to POST https://api.x.com/2/media/upload:

• Format: multipart/form-data
• Fields: media_data (base64), media_category ("tweet_image")
• Returns data.id (media ID string)

Constraints

• Max 4 images per post
• Images: max 5 MB (JPG, PNG, GIF, WEBP)
• GIFs: max 15 MB, resolution max 1280x1080
• Videos: max 512 MB, 0.5-140 seconds (requires chunked upload)

Post Content Guidelines

• Free tier: 280 characters per post
• Premium/X Blue: 25,000 characters
• Hashtags: use sparingly, 2-3 max
• @mentions count toward character limit
• URLs are shortened to 23 characters by t.co
• Line breaks are preserved

Writing an attractive, readable post (ALWAYS craft, never dump raw text)

Every time you compose for X, deliberately write the post for the platform. Do NOT paste an article abstract or a LinkedIn body verbatim. Source material (a WeChat article, a LinkedIn post) is INPUT to be re-cut for X, not the post itself. Re-cut it every time.

Hook the first line. The opening line is the post: it is what shows in-feed and decides the scroll-stop. Lead with one of: a surprising/specific stat, a bold claim, a provocative question, or a concrete value proposition. Put the most counterintuitive fact first. Never open with throat-clearing ("In this post I want to talk about...").