twitter-hand-skill

Twitter/X Management Expert Knowledge

Twitter API v2 Reference

Authentication

Twitter API v2 uses OAuth 2.0 Bearer Token for app-level access and OAuth 1.0a for user-level actions.

Bearer Token (read-only access + tweet creation):

Authorization: Bearer $TWITTER_BEARER_TOKEN

Environment variable: TWITTER_BEARER_TOKEN

Authentication modes:

• Bearer Token only (default): Sufficient for posting tweets, reading timelines, and searching. All core functionality works with just the Bearer Token.
• Bearer Token + OAuth 1.0a (optional): Required for user-context operations such as liking tweets, retweeting, following/unfollowing, and accessing DMs. Set TWITTER_API_KEY, TWITTER_API_SECRET, TWITTER_ACCESS_TOKEN, and TWITTER_ACCESS_TOKEN_SECRET to enable these features.

Note: The Like endpoint (POST /2/users/:id/likes) and Retweet endpoint (POST /2/users/:id/retweets) require OAuth 1.0a User Context authentication. If only Bearer Token is configured, these operations will be skipped with a warning.

Core Endpoints

Get authenticated user info:

curl -s -H "Authorization: Bearer $TWITTER_BEARER_TOKEN" \
  "https://api.twitter.com/2/users/me"

Response: {"data": {"id": "123", "name": "User", "username": "user"}}

Post a tweet:

curl -s -X POST "https://api.twitter.com/2/tweets" \
  -H "Authorization: Bearer $TWITTER_BEARER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"text": "Hello world!"}'

Response: {"data": {"id": "tweet_id", "text": "Hello world!"}}

Post a reply:

curl -s -X POST "https://api.twitter.com/2/tweets" \
  -H "Authorization: Bearer $TWITTER_BEARER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"text": "Great point!", "reply": {"in_reply_to_tweet_id": "PARENT_TWEET_ID"}}'

Post a thread (chain of replies to yourself):

1. Post first tweet → get tweet_id
2. Post second tweet with reply.in_reply_to_tweet_id = first tweet_id
3. Repeat for each tweet in thread