X API for Posting and Scheduling

The official X API

Posts are created with POST /2/tweets using OAuth 2.0 user context with the tweet.read, tweet.write and users.read scopes. Images and video are uploaded first through the chunked media endpoints (/2/media/upload/initialize, append and finalize), which need the media.write scope, and the returned media ID is attached to the post.

What posting requires

1. Create a developer account and an app in the X Developer Console (console.x.com).
2. Buy API credits. X bills usage per request; there is no subscription or minimum spend.
3. Configure OAuth 2.0 with PKCE for your app and request tweet.read, tweet.write, users.read and media.write.
4. Request the offline.access scope if you want refresh tokens; otherwise the user must sign in again after two hours.
5. Build your own queue if you need scheduled posts, and chain replies yourself to publish threads.

Cost: The X API uses pay-per-usage pricing with no subscriptions. Creating a post costs $0.015 per request, and a post that contains a URL costs $0.200. Post reads cost $0.005 per resource, capped at 3 million reads per monthly billing cycle on pay-per-usage plans. X's pricing page lists no free tier.

Official limits

Common gotchas

• Posts that contain a URL cost more than ten times a plain post at X's listed prices, which adds up for link-heavy accounts.
• X's docs state that quote posts via quote_tweet_id require an Enterprise plan and are not available on self-serve pay-per-use access.
• A media upload can succeed and still be rejected with a 403 when you attach it to the post, for example when the video is longer than that user is allowed to post.
• Without offline.access, access tokens expire after two hours and the user has to authorize again.

Post to X via API

curl -X POST https://api.publora.com/api/v1/create-post \
  -H "Content-Type: application/json" \
  -H "x-publora-key: sk_YOUR_API_KEY" \
  -d '{
    "content": "We moved our scheduler to a single queue. Three lessons.\n\n---\n\n1. Retries need idempotency keys.\n\n---\n\n2. Store every time in UTC.",
    "platforms": ["twitter-YOUR_USER_ID"],
    "scheduledTime": "2026-10-06T15:00:00Z"
  }'

import os
import requests

resp = requests.post(
    "https://api.publora.com/api/v1/create-post",
    headers={"x-publora-key": os.environ["PUBLORA_API_KEY"]},
    json={
        "content": "Release notes for v2.4 are live. Short thread on what changed.",
        "platforms": ["twitter-YOUR_USER_ID"],
        "scheduledTime": "2026-10-06T15:00:00Z",
        "mediaUrls": ["https://example.com/release-card.png"],
    },
)
resp.raise_for_status()
print(resp.json()["postGroupId"])

Or let an AI agent post

Connect any MCP client to mcp.publora.com:

• “Turn this blog post into an X thread of five or six posts and schedule it for Wednesday at 15:00 UTC.”
• “Schedule this announcement to X and LinkedIn for tomorrow at 13:00 UTC, with a shorter version for X.”
• “List my scheduled X posts for this week and delete the one about the webinar.”