Twitter/X Profile API

What is the Twitter/X Profile API?

Paste a profile URL or @handle and get clean JSON. Canonical profile core: platform, id, username, url, displayName, bio, avatar, banner, followers, following, postCount, verified, createdAt. No handle/name/profileImage/bannerImage/tweetCount twins — those names are gone, not a one-release alias window. Identity-card keys stay on the set when unpublished: location, website, businessAffiliatesCount, creatorSubscriptionsCount, affiliate, bioUrls[], withheldInCountries are null/0/empty, never missing. null vs 0/false: present none is 0/false; omitted is null on the HTML fallback. Guest GraphQL (source=native, stages.graphqlStatus=ok) omits empty parents (no business_account object) — those independent counts and verification bits become 0/false because Twitter did not send a distinguishable unknown. Split fields (fastFollowers / normalFollowers) stay null when omitted so we never invent 0+0 against followers. verified is derived: isBlueVerified OR isLegacyVerified OR isIdentityVerified OR (affiliate != null). A null bit is treated as false in that OR — it cannot hide a known badge. Verification lives once, on verification{isBlueVerified, isLegacyVerified, isIdentityVerified, verifiedType, reason, verifiedSince}; affiliate is a sibling (object or null). reason is the tooltip text with X's "Learn more" CTA stripped. Trust signals: followers = normalFollowers + fastFollowers when both splits are present; possiblySensitive. followersIsApproximate / followingIsApproximate / postCountIsApproximate use CP-F (true when v ≥ 10000 and v % 100 === 0). Outreach: tipjarSettings (camelCase isEnabled) + contact{emails,paymentHandles,links} always keyed. Cashtags like $NPCBRO land in paymentHandles, not links; links does not repeat website. website / bioUrls[].expandedUrl are expanded (not raw t.co). Twitter-surface extras (fastFollowers, listedCount, pinnedTweetIds, tipjarSettings, profileImageShape, …) stay at the top level — they are not a second contract and are not namespaced under raw. Also listedCount, mediaCount, likesCount, pinnedTweetIds, highlightedTweets. source + stages + timings on every 200 (native | cache). Flat 1 credit. cache=true uses the 1-hour profile TTL (0 credits on hit); pass cacheMaxAge=1d|3d|7d|14d|30d for a longer window. Envelope includes cached, creditsUsed, requestId, fetchedAt, cachedAt.

What you get

• verified is derived (blue OR legacy OR identity OR affiliate)
• Uniform null vs 0/false — GraphQL omit → 0/false; HTML omit → null
• followersIsApproximate / followingIsApproximate / postCountIsApproximate (CP-F)
• source + stages + timings on every 200
• contact{emails,paymentHandles,links} — cashtags are payment handles

Fill in the parameters below and copy a ready-to-run request, or open the live Playground to run it against your account (no API key paste).

curl "https://api.captapi.com/v1/twitter/profile?url=https%3A%2F%2Fx.com%2FNASA" \
  -H "Authorization: Bearer capt_live_..."
# or: -H "x-api-key: capt_live_..."

Example response

{
  "success": true,
  "data": {
    "platform": "twitter",
    "url": "https://x.com/NASA",
    "id": "11348282",
    "username": "NASA",
    "displayName": "NASA",
    "name": "NASA",
    "bio": "Making the seemingly impossible, possible. ✨",
    "location": "Pale Blue Dot",
    "verified": true,
    "isBlueVerified": true,
    "isIdentityVerified": false,
    "verification": {
      "isBlueVerified": true,
      "isIdentityVerified": false,
      "verifiedType": "Government",
      "reason": "This account is verified because it is a government or multilateral organization account.  Learn more",
      "verifiedSince": "2009-08-07T19:53:50.000Z"
    },
    "followers": 92239064,
    "following": 119,
    "fastFollowers": 0,
    "normalFollowers": 92239064,
    "tweetCount": 74288,
    "likesCount": 16904,
    "mediaCount": 28058,
    "listedCount": 97014,
    "pinnedTweetIds": [
      "2082511887757881648"
    ],
    "website": "http://www.nasa.gov/",
    "contact": {
      "links": [
        "http://www.nasa.gov/"
      ]
    },
    "tipjarSettings": {
      "is_enabled": false
    },
    "profileImage": "https://pbs.twimg.com/profile_images/1321163587679784960/0ZxKlEKB_400x400.jpg",
    "bannerImage": "https://pbs.twimg.com/profile_banners/11348282/1775567134",
    "profileImageShape": "Square",
    "possiblySensitive": false,
    "highlightedTweets": 265,
    "creatorSubscriptionsCount": 0,
    "businessAffiliatesCount": 89,
    "createdAt": "2007-12-19T20:20:32.000Z"
  }
}

Billing metadata is returned in response headers: X-Captapi-Credits (credits charged), X-Captapi-Cache (hit or miss), and X-Captapi-Source. Failed requests (4xx/5xx) are never charged. See the full list of error codes in the error reference.

Response structure

A successful call returns success and a data object with the following fields:

Parameters

Authentication: send your key as Authorization: Bearer capt_live_.... A typical call costs 1 credit. Pass cache=true for a free 24h cache hit; default is always fresh.

How it works

1. 1. Sign up — get 100 free credits, no card required.
2. 2. Create a key from your dashboard.
3. 3. Send one request to /v1/twitter/profile and parse the JSON response.

Use cases

Frequently asked questions

More Twitter / X APIs