# Twitter Follow Checker: Does A Follow B on X Canonical: https://www.twitterapis.com/tools/twitter-follow-checker Description: Check whether one X account follows another, in both directions, from live data. Enter two handles and read the directional follow relationship in seconds. Generated: 2026-09-14T03:00:37.995Z --- 1. [Home](/) 2. / [Tools](/tools) 3. / Follow Checker FREE TOOL # Twitter Follow Checker ## How do I check whether one X account follows another? 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 and the tool resolves each to its numeric ID, then reads the live relationship between that pair. ## 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](/twitter-followers-api) pages the followers and following lists with a cursor, and the [user API](/twitter-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](/tools/twitter-id-finder), or in code with the user info endpoint shown on the [quickstart](/quickstart). ## Frequently Asked Questions ### How does the Twitter follow checker work? 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. ### Does the checked account get notified? 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. ### How much does a follow check cost? 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. ### Can I see who unfollowed me on X? 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. ### Why do the blocking and muting fields say Not returned? 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. ### Can I check follow relationships in bulk? 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. One rate ceiling applies, 600 requests a minute and 20 concurrent per key, and there is 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-usecases)[ Twitter API answers Short, sourced answers to the most common Twitter and X API questions. ](/answers)[ Twitter timeline API Pull an account's full posting history over one REST endpoint. ](/twitter-timeline-api)[ Twitter list API Read list members and list timelines with the same Bearer key. ](/twitter-list-api) [All tools](/tools)[Start Free](/signup?utm_source=aio&utm_medium=organic&utm_campaign=aeo-tools-twitter-follow-checker) [ TwitterAPIs ](/) The cheapest pay-as-you-go Twitter and X API. $0.0008 per call, which works out to $0.04 per 1,000 tweets on a full 20-tweet page. No subscriptions and no developer account. ## Product / API - [Pricing](/pricing) - [Cost Calculator](/twitter-api-cost-calculator) - [Rate Limits](/twitter-api-rate-limits) - [MCP Server](/mcp) - [Integrations](/integrations) - [Language Clients](/sdk) - [Changelog](/changelog) - [Status](/status) ## Developers - [Documentation](https://docs.twitterapis.com) - [API Reference](https://docs.twitterapis.com/docs/reference/search/tweet-advanced-search) - [User Info](https://docs.twitterapis.com/docs/reference/user-reads/user-info) - [User Tweets](https://docs.twitterapis.com/docs/reference/user-reads/user-tweets) - [Advanced Search](https://docs.twitterapis.com/docs/reference/search/tweet-advanced-search) - [Verified Followers](https://docs.twitterapis.com/docs/reference/follower-graph/user-verified-followers) ## Resources / Compare - [Answers](/answers) - [Reviews](/reviews) - [Free Tools](/tools) - [Twitter ID Finder](/tools/twitter-id-finder) - [Get a Twitter API Key](/twitter-api-key) - [Official X API Comparison](/twitter-api-pricing) - [Twitter API Use Cases](/twitter-api-usecases) - [Twitter API Alternatives](/twitter-api-alternatives) - [Twitter Unofficial API](/twitter-unofficial-api) - [Twitter Free API](/twitter-free-api) - [TwitterAPIs vs twitterapi.io](/twitterapis-vs-twitterapi-io) - [TwitterAPIs vs GetXAPI](/twitterapis-vs-getxapi) - [TwitterAPIs vs TweetAPI](/twitterapis-vs-tweetapi) - [TwitterAPIs vs TwexAPI](/twitterapis-vs-twexapi) - [TwitterAPIs vs RapidAPI](/twitterapis-vs-rapidapi) ## Legal - [About](/about) - [Security](/security) - [Trust](/privacy-and-data-handling) - [Terms of Service](/terms-of-service) - [Affiliates](/affiliates) - [Contact](/contact) - [Jobs](/jobs) © 2026 TwitterAPIs. All rights reserved. TwitterAPIs is an independent third-party API for developers and researchers. Not affiliated with, endorsed by, or sponsored by X Corp. All systems operational