Twitter User API: Look Up Any Profile at $0.0008/call

Call GET /twitter/user/info with the userName query parameter set to the handle (without the @ symbol). The response is a flat JSON object with the user's id, name, screen_name, description, followers_count, friends_count, statuses_count, verified, is_blue_verified, location, created_at, pinned_tweet_ids_str, and profile_image_url_https. Each call costs $0.0008 and returns the full public profile in a single round trip. There is no pagination because a user lookup is always a single record. Authenticate with your Bearer token in the Authorization header.

user/info returns the core profile object: id, name, handle, bio, follower counts, verification flags, location, creation date, and pinned tweet ids. user/user_about returns an extended view that includes the full pinned Tweet object (not just the id), an expanded bio, the website URL, and the joined date formatted differently. Use user/info when you only need the counts and metadata; use user/user_about when you need the actual content of the pinned tweet or the expanded profile card.

No. You authenticate with a Bearer token issued by TwitterAPIs at signup, not by X's developer platform. There is no OAuth app to create, no X developer account to register, and no approval queue to clear. Signup takes about 30 seconds and you get $0.50 in free credits immediately, no card required. Your Bearer token works on all four user endpoints and on the rest of the TwitterAPIs surface.

The followers_count field in the user/info response gives you how many accounts follow this user, and friends_count gives you how many accounts the user follows. Both are integers that reflect the current public counts X displays on the profile. If you need the actual lists rather than the counts, use the Twitter Followers API (GET /twitter/user/followers and GET /twitter/user/following), which pages through the full lists with cursor pagination.

Yes. GET /twitter/user/info_by_id accepts a userId numeric string instead of a handle. Numeric ids are stable and do not change when a user renames their account, so if you store ids in your database you can reliably resolve profiles even after handle changes. The response payload is identical to user/info. Both endpoints cost the same $0.0008 per call.

GET /twitter/user/affiliates returns the accounts that X has linked as affiliates of the target user. This typically applies to organizational accounts, news outlets, and brands that X surfaces as related under the profile. For individual creators the list is usually empty. When it is populated it gives you the affiliate's full user object, so you can resolve the full profile of every affiliated account in one call.

Every call to any of the four user endpoints costs $0.0008. There is no subscription and no minimum spend. If you look up 1,000 profiles it costs $0.80. If you look up 100 it costs $0.08. You start with $0.50 in free credits, which covers 625 profile lookups. There are no additional per-field fees; the full profile payload is always included.

Yes. The response includes two verification fields: verified (boolean) for the legacy blue badge that X issued before 2023 to notable accounts without payment, and is_blue_verified (boolean) for the current X Blue / paid verification status. Some accounts will have one true and one false; some will have both true. Both fields are present on every user/info response.