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 a thread by chaining tweets where each subsequent tweet includes a reply object with in_reply_to_tweet_id set to the previous tweet's ID. Iterate through your list of texts, capture each returned tweet ID, and pass it as the reply target for the next post.

OAuth 2.0 bearer tokens provide app-only authentication suited for read-heavy operations like search and public data access. OAuth 1.0a user-context authentication is required for write operations such as posting tweets, managing accounts, and sending direct messages.

Upload media using the v1.1 endpoint at https://upload.twitter.com/1.1/media/upload.json with OAuth 1.0a, which returns a media_id_string. Then include that ID in the media.media_ids array when posting the tweet through the v2 tweets endpoint.

A 429 error means you have hit the rate limit for that endpoint and auth method. Read the x-rate-limit-remaining and x-rate-limit-reset response headers, then back off until the reset timestamp instead of retrying immediately.

Yes, recent tweet search works with an app-only OAuth 2.0 bearer token, which does not require user context. Set the Authorization header to Bearer followed by your token and query the /2/tweets/search/recent endpoint with operators like from: or -is:retweet.