Twitter (X) ID Finder

What is a Twitter user ID?

A Twitter user ID is the permanent number X assigns to an account when it is created. It is different from the @username: the username can be changed at any time, while the user ID never changes and, according to X's ID documentation, is globally unique across X. NASA's user ID, for example, is 11348282. Developers store the user ID, not the handle.

How to find a Twitter user ID from a username

1. Enter the username. Type the @username (handle) of the account into the Twitter ID finder above. The @ sign is optional.
2. Run the lookup. Select Find ID. The tool calls the user lookup endpoint once and reads the id field from the profile it returns.
3. Copy the user ID. Copy the numeric Twitter user ID. To go the other way, paste a numeric ID instead of a handle to get the current username back.

Why the numeric ID matters

A Twitter / X handle is not a stable identifier. Users rename, accounts get recycled, and a handle you stored last month can point at a different person today. The numeric user ID is assigned once at account creation and never changes, which is why every serious integration keys its data on the ID, not the username. To see whether a handle is currently taken, use the username checker.

This tool resolves either direction in one call. To do the same thing inside your own product, the GetXAPI user lookup returns the full profile (ID, follower counts, bio, creation date, verification) at $0.001 per request, with no X developer account. See the pricing for the full rate card, or the Python tutorial for a code walkthrough.

Twitter username to ID, and Twitter ID to username

This tool works both directions. Type an @username to get its numeric ID, or paste a numeric ID to get the current handle and profile back. The reverse lookup (ID to username) is the one people reach for most: when you have IDs saved from an old export and the handles may have changed, the ID is the only thing that still resolves reliably, because it never changes even after a rename.

What developers use the ID for

• A stable primary key: store follower, tweet, and profile data against the ID so a rename never orphans your records.
• Direct lookups: endpoints that take a user ID, such as user/info_by_id, resolve the account in one call with no handle involved.
• Deduplication: the same account can appear under different handles over time, the ID collapses them into one.

All of this is available programmatically: the followers and user endpoints return the numeric ID on every profile, so you can resolve handles and IDs at scale instead of one at a time.

How to find a Twitter (X) ID manually

You can read the ID from x.com itself, but it takes a browser and a few steps. Both routes below were checked on October 15, 2026 while signed in to x.com; X changes its page markup often, so treat them as a fallback rather than a method to build on.

• Username to ID, from the page: open the profile on x.com in a desktop browser, open developer tools, and search the Elements panel for -follow. The Follow button carries the ID in its test id, for example 11348282-follow on NASA's profile.
• ID to username, from the URL: open x.com/i/user/ followed by the number. On our test, x.com/i/user/11348282 redirected to x.com/NASA.
• The official API: X's users lookup endpoint returns the id field for a username, but it needs approved developer access and credentials, a lot of setup for one number.

Common use cases for a Twitter ID

• Giveaway and contest verification: pin entrants to their permanent ID so a handle change after entering cannot be used to game or duplicate entries.
• Duplicate and bot auditing: the ID is the only reliable key for spotting the same account across handle changes, or flagging suspicious ones.
• Account-age screening: resolve the ID and profile to read the creation date, a fast signal for filtering brand-new or throwaway accounts.
• Stable data storage: key your database on the ID so a rename never orphans a user's historical records.

Get a Twitter user ID from a username with the API

The tool above is one API call, and you can make the same call from your own code. Send the username to /twitter/user/info and read data.id. To go from a user ID back to a username, send the ID to /twitter/user/info_by_id and read data.userName. Each call is $0.001 and needs only a Bearer key, with no X developer account.

# username to user ID  ->  "11348282"
curl -s "https://api.getxapi.com/twitter/user/info?userName=nasa" \
  -H "Authorization: Bearer $GETXAPI_KEY"

# user ID to username  ->  "NASA"
curl -s "https://api.getxapi.com/twitter/user/info_by_id?userId=11348282" \
  -H "Authorization: Bearer $GETXAPI_KEY"

The same user object carries follower counts, the bio and the creation date, so one call answers most profile questions. The object reference lists every field.

User ID or tweet ID: which number do you have?

Both are numbers from the same ID system, so they are easy to mix up. Pasting a tweet ID into a user lookup returns nothing, and the reverse is true as well.

Store either one as a string. X's ID documentation describes them as 64-bit unsigned integers and warns that JavaScript, which is exact only up to 53 bits, can corrupt a long ID that is parsed as a number.

Ways to find a Twitter ID, compared

Use the tool for a one-off Twitter ID lookup, the x.com tricks when you are already signed in, and an API when you have more than a handful of accounts. Only the tool and the API work in both directions without an X login; the official X API needs approved developer access first.

Handle or numeric ID: which to store

Both identify the same account. Only one of them survives a rename, which is why every API response carries the number.

The practical rule: show the handle, store the ID. A dataset keyed on handles quietly breaks the first time someone renames.

Verified October 15, 2026 against X's ID documentation, X's user lookup documentation, X's API data dictionary, with both lookups tested live through GetXAPI on the same date.