App Logo
x.com

Pin a tweet to your X (Twitter) profile

Automatically pin a tweet to your X (Twitter) profile on x.com. Pin one of your own tweets to the top of your profile, given its URL. Already-pinned tweets are reported rather than re-pinned. Pinning a new tweet replaces whatever was previously pinned. Returns tweet_id, pinned, was_pinned, and account_used. X can briefly serve a stale pinned-state right after a preceding pin/unpin on the account — if you just changed the pin state, allow a few seconds before calling this again for a reliable was_pinned reading.

Input

tweet_url required

Full URL of your tweet to pin, e.g. https://x.com/handle/status/123.

Output

pinned required
tweet_id required
was_pinned required

true if the tweet was already pinned before this call — no action was taken.

account_used optional

handle of the logged-in account that performed the action, read from the account switcher UI.

FAQ

Pin one of your own tweets to the top of your profile, given its URL. Already-pinned tweets are reported rather than re-pinned. Pinning a new tweet replaces whatever was previously pinned. Returns tweet_id, pinned, was_pinned, and account_used. X can briefly serve a stale pinned-state right after a preceding pin/unpin on the account — if you just changed the pin state, allow a few seconds before calling this again for a reliable was_pinned reading.
Ask an AI agent connected to Reduck to run reduck/x.com/pin_tweet, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/x.com/pin_tweet
You do not need one. "Pin a tweet to your X (Twitter) profile" drives the real x.com pages in a browser, so it works whether or not x.com offers an API for this.
Required: tweet_url.
It returns pinned, tweet_id, was_pinned, account_used.
Yes. It acts as you on x.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the x.com cookies saved by the Reduck extension.
It makes changes on x.com, like sending, posting, booking or buying something.
Ask an AI agent connected to Reduck to run reduck/x.com/pin_tweet, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/x.com/pin_tweet
It is part of Reduck's official curated catalogue.

Related scripts

x.com

X (Twitter) search unofficial API: search tweets, no API key

Search X (Twitter) for tweets with every X search operator, from the Top tab (a ranked sample, the default) or the Latest tab (chronological), picked by the tab arg. Returns per tweet a canonical record: id, url, author {id, handle, name}, text, created_at, lang, likes, retweets, replies, quotes, bookmarks, views, is_retweet, is_quote, plus followers (the author's follower count, a search-only enrichment), and the top-level query and count. Top is a ranked sample, not exhaustive.

x.com

Get a tweet and its replies on X (Twitter)

Fetch a tweet by URL — the focal post plus the surrounding conversation. Returns `tweet` (the focal post; null if deleted/tombstoned) and `replies[]`, which holds every other tweet on the conversation page: both the focal's ancestors (the thread above it, present when the focal is itself a reply; each has `in_reply_to` null or pointing above the focal) and the replies below it (`in_reply_to` points at the focal or a sibling reply). Use `in_reply_to` to tell ancestors from replies and rebuild the thread — the array is not filtered to descendants of the focal. Each entry is a canonical tweet record: id, url, author {id, handle, name}, text, created_at, lang, likes, retweets, replies, quotes, bookmarks, views, is_retweet, is_quote, in_reply_to {id, author_handle}. Scrolls the main thread until `count` is met (then complete=false — more may exist) or it drains (complete=true). Replies behind a "Show more replies"/hidden/probable-spam cursor are not expanded, so even complete=true is a floor, not a guarantee every nested reply was seen.

x.com

X (Twitter) profile unofficial API: get a user's bio and followers

Look up an X user's profile by handle. Returns handle, user_id, name, bio, location, website, joined, followers_count, following_count, is_verified, is_self, is_following, follows_you. Follower/following counts are exact integers, not X's abbreviated "3.7M" display text. bio and website carry the real destination URLs, with X's t.co shortlinks resolved. is_following is null on your own profile (you have no follow relationship to yourself); user_id is always present.

Start building not clicking

Get started for free