Twitter Engagement API: Like, Repost and Measure

A Twitter engagement API is a REST interface with two halves. The write half performs the interactions themselves, so your code can like, repost, bookmark, follow or publish as a real X account. The read half returns the counters those interactions move, so you can measure like, repost, reply and quote totals on any public post. TwitterAPIs covers both on a single Bearer key: five write actions with matching undo calls at $0.0008 each, and four read endpoints at the same standard rate, with no X developer account and no monthly plan.

Yes, and this is the one setup step people miss. A read works on your Bearer token alone, because public data is not attributed to anybody. A write has to act as somebody, so it needs an X session. You supply auth_token and ct0 once through POST /twitter/customer/session, which costs nothing, and the session is stored against your key and applied to every subsequent like, repost, bookmark, follow and post. There is no OAuth consent screen and no app review in the path.

Yes, and it needs no session at all. GET /twitter/tweet/detail takes a post id or url on your Bearer token and returns the like, repost, reply, quote, bookmark and view counters on that post. Nothing is attributed to you and nothing is modified. That call is the right one for dashboards, leaderboards and reporting, where you want the number without touching the post.

Automation that a real person has authorised on their own account is ordinary API use; bulk unsolicited interaction is what platform policy targets, and X enforces against it regardless of which tool produced it. Two practical consequences. Register only sessions for accounts you actually control, and pace your write volume to look like a person rather than a loop. Our per-call billing means throttling costs you nothing, so there is no commercial reason to run hot.

Send POST /twitter/tweet/favorite with either the post id or its url as a query parameter, carrying your Bearer token. Because a like has to be attributed to a real account, you register your X session once beforehand with POST /twitter/customer/session, supplying auth_token and ct0. That registration call is free and is stored against your API key, so every later write is applied as your account automatically. Undoing is the mirror call, POST /twitter/tweet/unfavorite, at the same $0.0008.

Likes, reposts, bookmarks, follows and every matching undo bill at a flat $0.0008 per call, the same rate as a standard read, so a write costs you no more than a read. Publishing a post is the one premium write at $0.0016. Registering your session is free. There is no monthly minimum and no seat licence, which means a thousand likes costs about $0.80 and a script that idles costs nothing at all.

Reposts, yes. GET /twitter/tweet/retweeters pages through the accounts that reposted a given post, each with its profile fields, so you can profile who amplifies a topic. The list of accounts that liked a post is not exposed by X to third parties in the same way, so we do not offer it. The nearest available angle is the reverse lookup: GET /twitter/user/likes returns what a specific account has liked, which answers audience questions from the account side rather than the post side.