Twitter API for account data
Look up any X account by handle, read how its following has moved over time, measure what its posts actually earn in engagement, and verify that the person you are talking to controls it. No developer application, no per-post billing, no waiting on an approval queue.
- Endpoints for Twitter
- 55
- Free to start
- 500 requests
- Paid from
- $69/ 30 days
One request, no application
Send a key, get an answer. Every endpoint on this page uses the same header, the same envelope and the same error codes as the other six platforms.
curl "https://api.playersells.com/v2/accounts/x/elonmusk" \
-H "Authorization: Bearer $PLAYERSELLS_API_KEY"What the Twitter API returns
- handle, display name and bio
- follower, following, post and media counts
- verification status, including whether it is paid or legacy
- account creation date
- profile and banner image URLs
- follower history, so growth is measurable rather than guessed
- engagement rate, top posts and viral patterns
Where the data comes from
Our own X crawler, running continuously since 2026 and backed by a Postgres catalog we operate. Live lookups go through our profile service rather than the official API, which is why a fresh read costs one request instead of a per-post fee.
What this API cannot do
- Protected accounts return what the public profile shows and nothing behind the lock.
- Post-level history is deepest for accounts already in the catalog. A handle we have never seen is fetched live, and its history starts from that read.
- We do not post, follow, like or send messages. This is a read API.
Twitter endpoints
27 built specifically for Twitter, plus 28 that cover every platform.
Specific to Twitter
| Endpoint | What it does | Scope |
|---|---|---|
GET/accounts/{platform}/{handle} | Check one account against our catalog | directory:read |
GET/accounts/{platform}/{handle}/livelive | Check one account live, at the source | scrape:live |
GET/accounts/resolve | Find one handle on every platform at once | directory:read |
GET/directory/{platform} | List and filter a catalog | directory:read |
GET/directory/{platform}/{id} | One account or channel | directory:read |
GET/directory/{platform}/{id}/growth | Daily audience history | directory:read |
GET/directory/{platform}/{id}/followers | Inbound graph edges | directory:read |
GET/directory/{platform}/{id}/following | Outbound graph edges | directory:read |
POST/directory/{platform}/bulk | Resolve up to 100 records at once | directory:read |
GET/directory/{platform}/facets | Distribution of the catalog | directory:read |
GET/directory/search | Search every platform at once | directory:read |
GET/people/lookup | Find one handle across every catalog | directory:read |
GET/people/search | Find accounts matching audience and engagement criteria | directory:read |
GET/scrape/x/userlive | Live X profile | scrape:live |
POST/scrape/x/userslive | Live X profiles, batched | scrape:live |
GET/scrape/x/verifylive | Prove ownership of an X account | scrape:live |
GET/insights/x/{handle} | Complete intelligence dossier for one X account | insights:read |
GET/insights/x/{handle}/engagement | Engagement metrics for one X account | insights:read |
GET/insights/x/{handle}/top-tweets | The account's permanently kept best posts | insights:read |
GET/insights/x/{handle}/viral-patterns | What makes this account's posts perform | insights:read |
GET/insights/x/{handle}/benchmark | This account against its follower cohort | insights:read |
GET/insights/x/leaders | Accounts ranked by how well they engage | insights:read |
GET/insights/x/coverage | How much of the catalog has tweet-level coverage | insights:read |
POST/insights/x/compare | Side-by-side metrics for up to ten accounts | insights:read |
GET/marketplace/listings | Browse active marketplace listings | marketplace:read |
GET/tools/audience-finder | Search the Telegram, TikTok and X catalog | tools:use |
GET/leads/x/followers | Follower-graph export for one X account | leads:read |
Across all platforms
| Endpoint | What it does | Scope |
|---|---|---|
GET/accounts/platforms | What a check can answer, per platform | directory:read |
POST/accounts/check | Check up to 50 accounts at once | directory:read |
GET/directory | Catalog capability map | directory:read |
GET/scrape/status | Live backend health and capacity | scrape:live |
GET/insights/audience | Who follows an account, and what they have in common | insights:read |
GET/research/findings | Findings the research engine is willing to state | research:read |
GET/research/findings/{id} | One finding with its full test history | research:read |
GET/research/runs | Research pass history | research:read |
GET/research/events | The research changelog | research:read |
GET/engines | Operational health of every insight engine | engines:read |
GET/engines/{key} | One engine in detail | engines:read |
GET/marketplace/listings/{id} | Get one public listing | marketplace:read |
GET/marketplace/stats | Platform totals | marketplace:read |
GET/marketplace/leaderboard | Best-selling sellers | marketplace:read |
GET/marketplace/pricing | Live fee schedule and boost packages | marketplace:read |
GET/tools | List every analysis tool | tools:use |
POST/tools/valuationlive | Value an X account | tools:use |
POST/tools/shadowban-checklive | Check an X account for visibility filtering | tools:use |
POST/tools/follower-auditlive | Audit an X account's followers for fakes | tools:use |
POST/tools/engagement-calculatorlive | Measure an X account's engagement rate | tools:use |
POST/tools/best-posting-timelive | Find when an X account should post | tools:use |
POST/tools/algorithm-scorelive | Score an X account against the ranking signals | tools:use |
POST/tools/bio-optimizerlive | Score and rewrite an X bio (AI) | tools:use |
POST/tools/profile-roastlive | Roast and fix an X profile (AI) | tools:use |
POST/tools/tweet-analyzerlive | Analyze a single X post | tools:use |
POST/tools/mention-checkerlive | See who is mentioning an X account | tools:use |
POST/tools/growth-simulator | Project how long a follower target takes | tools:use |
GET/tools/profile-piclive | Fetch an X profile picture URL | tools:use |
Twitter API questions
Is this the official X API?
No. It is an independent API over data we collect ourselves from public X profiles. That is the point: there is no developer application, no approval queue, and no per-post charge. If you need to publish tweets or read a private timeline, you need the official API instead. If you need to read public account data at volume, this is cheaper and faster to start with.
How current is the data?
Catalog reads carry a cache_age_s field in every response, so you always know how old the number you are looking at is. When you need a value that is current to the second, call the live endpoint, which fetches from the source at request time and reports an age of zero.
Can I verify that someone owns an X account?
Yes. Ask the owner to place a short code in their bio, then call the verification endpoint with the handle and the code. It reads the bio live and answers with a plain true or false plus the exact text it matched, so a disputed result can be inspected rather than argued about.
What does a Twitter API request cost?
A catalog read counts as one request against your monthly plan. A live fetch counts as several, because it costs real upstream work. The multiplier is listed on every plan and on each endpoint in the documentation, so the cost of a call is knowable before you make it.
The same API, on six other platforms
One key, one envelope, one bill. Reading a second platform is a different path, not a different integration.