Twitter Profile API — Look Up a Public X Account
Use the Twitter Profile API to read an account’s name, bio, images and available follower statistics by username or profile URL. Build your own account reference sheet from the returned fields.
1 credit per successful request, including empty results. Failures are free.
https://api.goanyapi.com/api/v1/twitter/user/profileRun a request to see the visual result
The response is organized into metrics, lists and tables that match the JSON on the right.
Run a request to see the response here
Fill in the demo parameters to preview an example response for free. Sign in to send live requests with your own parameters.
Build an account reference without guessing its identity
A display name alone is a weak reference when collecting sources or maintaining a list of public accounts. The Twitter Profile API lets you start with a username and inspect the returned handle, original account ID, description and website together. Use the information to prepare your own account sheet before deciding whether the account is relevant to your work. Public statistics add context to that record; they do not establish credibility, audience quality or the identity of individual followers.
Saved example: the ChineseWSJ profile
Enter ChineseWSJ, @ChineseWSJ or https://x.com/ChineseWSJ as screenName. The saved record identifies the account as 华尔街日报中文网, with ID 46574977, location China and a website at cn.wsj.com. It contains a biography, avatar and banner, 3,341,431 followers, 493 following, 99,028 tweets and 6,229 media tweets. Verified is true and protected is false in this sample. These are saved values, not a claim about the account’s present state. You can organize the returned fields into a publisher reference sheet and add your own review date. The profile documentation explains the request format.
- data.result.id
- The account ID is a string. Store it beside the returned handle in the account sheet, giving reviewers an original identifier in addition to the display name.
- data.result.description
- Retain the public biography as account-provided wording. The saved text describes the publisher and its membership offering; place your own subject labels beside the original description.
- data.result.followers
- The saved follower count is 3,341,431. Pair it with following in an account statistics table while keeping each measure separate. A follower count is not a follower list.
- data.result.mediaTweetCount
- The sample has 6,229 media tweets and 99,028 tweets overall. These fields describe account-level counts; a specific post’s content belongs to a separate tweet lookup.
- data.result.verified
- Verified is true in the sample, while protected is false. Display these as separate booleans alongside verifiedType instead of deriving verification from a nonempty text label.
- data.result.createdAt
- This is the account creation timestamp. Store it separately from retrieval time and post publication dates. Location and website provide additional profile context for the same account sheet.
Public profile context, with explicit limits
This endpoint reads one public account record and has no pagination. It does not return follower lists, direct messages, email addresses or private posts. Avatar and banner URLs are available only when returned and may become unavailable later. Nulls, empty strings, missing fields, zero counts and false booleans retain their meaning. Successful requests, including successful empty results, use the current configured fee; failures are free. Supported profile URL parsing is part of the same request.
Put public account fields to work
Choose a practical account task, then assemble the result in your own application. The API returns profile data; your workflow supplies classification, storage and review.
Create a source directory entry
An editor can create a publisher directory entry from name, handle, ID and biography. The X user profile API supplies the account record; the editor adds subject tags and review notes to the directory.
Keep the declared website alongside the handle
Researchers can place the declared website alongside the account handle in a source sheet. This gives a reviewer the exact address to inspect when checking how an account presents its organization or publication.
Capture account-level statistics
A reporting tool can display followers, following, tweet count and media tweet count in separate columns. Store dated observations to support later comparisons of the same public account without mixing the four measures.
Show the returned profile identity
A public account catalog can display the returned avatar and banner with its name and handle. Retain the original image addresses and provide a fallback so the text reference remains useful if an image fails.
Read status flags as separate facts
A review queue can show verified, protected and verification type together. Keeping each field visible helps reviewers distinguish the returned account status from the editorial categories they assign to the directory.
Prepare a concise account brief
An HTTP-capable Agent can request a named account and prepare a brief containing its biography, website, creation date and counts. Configure authorization securely in the client, then keep the original record alongside the brief.
Questions about inputs, results and costs
No. This endpoint returns the available account-level follower count, not follower identities or a list to page through. It also does not provide audience demographics or follower contact details. If your task depends on those records, the public profile response does not establish that capability.
Use the username, an @username or the full supported profile URL in screenName. A numeric account ID is returned for reference but is not the declared input here. A post link is a different resource, and URL parsing does not create a separate charged request.
They describe the returned account status. The sample’s verified value is true and protected is false; other records can differ or omit fields. These values do not promise private content access or certify the accuracy of the biography. Read each flag independently and keep the raw JSON.
Opening the page loads a saved example without a business request. An explicit successful lookup, including an empty result, uses the current displayed configuration; a failed request is free. Looking up the same account again is another request, with no built-in subscription or automatic monitoring.
Connect account context to individual posts
Use the Twitter Profile API to understand the public account record. Explore a known post or a separate trend timeline when your next question concerns content. Additional lookups are independently requested and billed.