Skip to content
PricingDocsBlog
MCP ServerIntegrationsLanguage ClientsFree ToolsTwitter ID FinderTwitter API Cost CalculatorTwitter Search APITwitter Followers APITwitter ScraperTwitter API Use CasesTwitter API Rate LimitsTwitter Unofficial APITwitter Free APITwitter API AlternativesTwitterAPIs vs TweepyTwitterAPIs vs RapidAPITwitterAPIs vs GetXAPI
AboutStatusAffiliatesTrustChangelogContact
Start Free

FREE TOOL

Twitter Follow Checker

The Twitter Follow Checker is a browser tool that reads the follow relationship between two X accounts and reports it in both directions at once. Following is not symmetric, so the useful answer is really two answers: whether the first account follows the second, and whether the second follows back. Enter two handles below and the tool resolves each one to its numeric ID, then reads the live relationship between that pair.

The key is sent to this site once, forwarded to the API for this single request, and never stored. Every lookup on this page is one read call at $0.0008. New accounts start with $0.50 of credit, which is 625 lookups. Create a key or read the API key guide.

A check made from two handles is three read calls: one to resolve each handle to its numeric ID, then one relationship read. Pass numeric IDs instead and the resolve steps still run, so the count is the same.

What a follow relationship actually contains

A relationship read returns a directional record between a source account and a target account. The two fields that matter for most questions are following, which is true when the source follows the target, and followed_by, which is true when the target follows the source. A mutual follow is both fields true at once. The record also carries block, mute and DM-eligibility state, and those fields are populated only when the caller has an authenticated view that can see them, so treat a null in that group as unknown rather than as a negative answer.

If you need the full list rather than a single pair, the followers API pages the followers and following lists with a cursor, and the user API page covers the profile object that carries the follower counts.

The same check in code

The relationship endpoint takes numeric IDs, so a script resolves each handle once and then reuses the IDs.

curl "https://api.twitterapis.com/twitter/user/check_follow_relationship\
?source_user_id=745273&target_user_id=2178758961" \
  -H "Authorization: Bearer YOUR_API_KEY"

# {"relationship":{"following":true,"followed_by":false, ...}}

Resolve a handle to an ID first with the Twitter ID finder, or in code with the user info endpoint shown on the quickstart.

Frequently Asked Questions

It resolves each account you enter into its numeric user ID, then reads the directional relationship between those two IDs from the check follow relationship endpoint. The result has two independent halves: whether A follows B, and whether B follows A. Those are separate facts, which is why a one-way answer is not enough to tell you whether a follow is mutual.

No. Both accounts are read through the public profile and relationship endpoints, which is the same information a person would see by opening the two profiles. Nothing is followed, liked, messaged, or written. This tool only makes read calls, and the proxy behind it is restricted to three read endpoints so it cannot perform a write action even if asked to.

Three read calls at $0.0008 each, so $0.0024 for one check. Two of those calls resolve the handles you typed into numeric IDs, because the relationship endpoint works on IDs rather than handles. If you are running this at volume in your own code, resolve each account once, cache the ID, and every subsequent check on that pair is a single call.

Not from a single check, and not from any honest tool that has no history of your account. Unfollows are a difference between two points in time, so seeing one means somebody stored your follower list earlier and compared it to the list now. This tool answers the present-tense question for a specific pair. To build unfollow tracking, snapshot your followers on a schedule with the followers endpoint and diff consecutive snapshots yourself.

Because block, mute, and DM state are visible only to an authenticated session that has standing to see them. When the endpoint has no authenticated view of that pair it sends null rather than guessing, and this tool prints Not returned instead of turning a null into a No. A null means the answer was unavailable, which is a different statement from the answer being negative.

Yes, through the API rather than this page. The relationship endpoint takes one source and one target per call, so a bulk job is a loop over your pairs with the IDs already resolved. There is no platform rate ceiling to work around and no monthly minimum, so the cost of a bulk run is simply the number of pairs times the per-call rate.

Next read

Continue exploring related pages:

Twitter API use cases

14 use cases from sentiment analysis to lead generation.

Twitter API answers

Short, sourced answers to the most common Twitter and X API questions.

Twitter timeline API

Pull an account's full posting history over one REST endpoint.

Twitter list API

Read list members and list timelines with the same Bearer key.

All toolsStart Free