Give one Twitter search keyword and an expected count to get matching public post identifiers, publish times, and collection metadata.
Twitter Account Info
Collect public profile details, audience metrics, and verification signals for one or more Twitter accounts
Overview
Twitter and X profile pages mix identity, audience size, verification, and protection signals in a layout that is hard to compare across accounts. This app turns those public profiles into a consistent record set so research, partnership, and monitoring teams can work from the same identifiers, metrics, and timestamps.
The value is the joined profile snapshot: displayed name, username, account ID, public URL, follower and following figures, verification and protection flags, bio text, and collection time stay together for each submitted username. That makes it easier to qualify creators, compare audience scale, and keep a watch list current without reconstructing profiles by hand.
Data notes
The data comes from the public Twitter profile associated with each submitted username. One record is produced for each submitted username when the source returns a profile or a no-data marker. Duplicate submitted usernames are removed across collected pages. Audience counts, bio text, professional attributes, location, and timestamps retain the source text; a source value can be unavailable and appear empty. Follower count, Following count, Fast followers, Like count, Listed count, Media count, and Post count are kept as source text rather than normalized numbers. Can DM, Media tag, Protected account, Translator, Custom timelines, Graduated access, and Sensitive are also retained as source text, even when they look like yes/no flags. Has email, Verified, and YouTube linked are true/false values. Collected at and Joined at are preserved as supplied, without inferring a timezone. Private, suspended, and login-only accounts are outside the coverage.
What the results look like
Each record represents the public profile collected for one submitted Twitter username.
| Account name | Username | Follower count | Verified | Submitted account | No data |
|---|---|---|---|---|---|
| 💫Etoiles💫 | 000uTSIDER | 2 | No | 000uTSIDER | No |
| demo.account | Yes |
Additional values include Avatar URL, Profile URL, Account ID, Bio, Affiliate label, Business ID, Can DM, Media tag, Cover photo URL, Collected at, Entity type, Fast followers, Following count, Custom timelines, Graduated access, Profile entities, Has email, Protected account, Translator, YouTube linked, Joined at, Source keyword, Like count, Listed count, Location, Media count, Pinned tweets, Sensitive, Professional info, Interstitial type, Post count, and Translator type.
Use cases
- Qualify partnership targets by comparing Account name, Username, and Follower count across a watch list.
- Map public presence by lining up Profile URL, Bio, Location, and Joined at for accounts you already monitor.
- Separate empty outcomes from usable profiles by checking No data together with Submitted account before using Like count or Post count.
- Distinguish public versus restricted profiles by reading Protected account, Verified, and Sensitive together with Account name.
Scope and boundaries
Each run accepts 1 to 200 Twitter usernames and returns at most one public profile record per username when data is available.
- Good for
- When you need a current public profile snapshot for specific Twitter accounts
- When you need displayed audience size, verification, protection, and public profile signals in one record
- Do not use for
- When you need posts, comments, or search results rather than account-level profile information
- When you do not have a Twitter username to collect
Failure handling
Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.
- 1If no profile data is returned, verify the username and confirm the account is still public
- 2Retry later after rate limiting, temporary unavailability, or a timeout
- 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
- 4If authentication fails, verify the API Key configured for the execution environment
Input
Parameters required to call this App, generated from the input.schema in manifest.json.
- Twitter username list
itemsRequiredarray<object>The Twitter usernames to collect. Submit 1 to 200 items; each item needs one username.Itemsup to 200 itemsExample[{"account":"000uTSIDER"}]
Output
Field structure of a single record, generated from the output.schema in manifest.json.
- Submitted account
task_itemstringThe username submitted for this recordExample000uTSIDER - No data
no_databooleanWhether this submitted username returned no public profileExamplefalse - Source keyword
keywordstringThe source keyword associated with the collected accountExample000uTSIDER - Account ID
account_idstringThe Twitter account identifier returned for the profileExample1652063959627841537
Sample data
Generated from output.schema. Fields without a sample value use structural placeholders.
{
"task_item": "000uTSIDER",
"no_data": false,
"keyword": "000uTSIDER",
"account_id": "1652063959627841537",
"account_name": "💫Etoiles💫",
"account_avatar_url": "https://pbs.twimg.com/profile_images/1718476282885808128/3IcN2Gim_normal.jpg",
"account_home_url": "https://x.com/000uTSIDER",
"account_signature": "she/her",
"affiliates_highlighted_label": "{\"label\":null}",
"biz_id": "000uTSIDER",
"can_dm": "false",
"can_media_tag": "true",
"cover_photo_url": "<cover_photo_url>",
"crawl_time": "2026-08-27T14:07:55",
"entity_type": "user",
"fans_count": "2",
"fast_followers_count": "0",
"friends_count": "17",
"has_custom_timelines": "false",
"has_graduated_access": "true",
"info": "{\"description\":{\"hashtags\":null,\"urls\":null,\"userMentions\":null},\"url\":null}",
"is_mail": false,
"is_protected": "false",
"is_translator": "false",
"is_verified": false,
"is_youtube": false,
"joined_date": "2023-04-29T05:35:28",
"likes_count": "7093",
"listed_count": "0",
"location": "<location>",
"media_count": "5",
"pinned_tweet_ids": "<pinned_tweet_ids>",
"possibly_sensitive": "false",
"professional": "<professional>",
"profile_interstitial_type": "<profile_interstitial_type>",
"publish_content_count": "202",
"translator_type_enum": "none",
"user_handle": "000uTSIDER"
}Integration
This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.
With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.
Client config
Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=hello_moto/twitter-account-info",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Let AI set it up for you
Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (By default it guides you through signing in, and never asks you to send your API key in the chat.)
detail.access.mcp.composeHint
Pricing
Charged once per submitted run, regardless of how many records are returned.
Charged by the number of records successfully returned. Failed runs are not charged.
Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.
View creditsTry it now
Fill in the parameters and run. Results come from a real call.