x-api

Post a tweet by sending a POST request to https://api.x.com/2/tweets with a JSON body containing the text field, authenticated via OAuth 1.0a user context. Use requests_oauthlib's OAuth1Session with your consumer key, consumer secret, access token, and access token secret.

Post each tweet sequentially, passing the previous tweet's ID in the reply.in_reply_to_tweet_id field of each subsequent request. Collect the returned tweet IDs to track the full thread.

OAuth 2.0 Bearer tokens are app-only and best for read operations like search and timelines. OAuth 1.0a user-context authentication is required for write operations such as posting tweets, managing accounts, and DMs.

Read the x-rate-limit-remaining and x-rate-limit-reset response headers at runtime and back off when remaining calls are low. Avoid hardcoding static rate limit tables since limits vary by endpoint, auth method, and account tier.

Upload media first via the v1.1 endpoint https://upload.twitter.com/1.1/media/upload.json to get a media_id_string, then include that ID in the media.media_ids array when posting the tweet through the v2 endpoint.

A 403 error typically means your app lacks write permissions or you are using app-only Bearer auth for a write operation. Switch to OAuth 1.0a user-context credentials and verify your app's permissions in the X developer portal.