Either Direction
Handle to numeric ID, or the ID back to whatever handle currently sits on it. The numeric ID never moves, so it is the half of the pair worth writing down.
A handle can be given up and handed out to somebody else. The numeric ID never moves, which is why records should hold that instead.
The ID either way, a whole list at a time, and today's handle stored alongside.
Handle to numeric ID, or the ID back to whatever handle currently sits on it. The numeric ID never moves, so it is the half of the pair worth writing down.
A whole list filled in at once, which is the difference between a two-minute job and a two-hundred-lookup afternoon. Most people need this once, for everything they have already recorded.
The handle as it stood that day gets stored beside the ID. That gives you your own baseline to compare against later, so a rename shows up as a mismatch rather than as silence.
Give it what you have, get back the part that lasts.
Handles, IDs, or a mix. It works out which way round each one needs to go.
Each account gets read and the missing half comes back, with the current handle recorded next to it.
Put the IDs into your records. The list stays, and the next pass compares against it.
Three limits worth understanding before an ID becomes your primary key.
An ID identifies an account, not a person. Accounts get sold, handed over, and repurposed, and the ID does not move with it, so a stable identifier is not a stable identity. Useful to hold in mind when the record is going to outlive the reason you made it.
.jpeg&w=1920&q=75)
X does not publish what an account used to be called, so nothing can hand you a list of former handles. What we can say is that an ID matches, and what we cannot say is what it was called before you started looking.
.jpeg&w=1920&q=75)
Who is behind an account is not something this answers, and not something it attempts. There is no verification step here, no linking of accounts to people, and no route from an ID to anybody's name. That is a deliberate line rather than a gap.
.jpeg&w=1920&q=75)
Which accounts, which direction, what else gets recorded. All of it stays as you left it, which turns maintenance into a re-run. Your AllyHub never starts from scratch again and gets faster every time.
.jpeg&w=1920&q=75)
People storing accounts in a system, teams maintaining a long list, people migrating old records, and anyone whose list has stopped matching.
Storing an account in a system means choosing what the key is, and the obvious choice is the one that is visible. It works until the day it does not, and then it fails quietly rather than loudly.
Creator rosters, research samples, watchlists. They get built once and consulted for years, which is exactly the timescale over which handles change hands and nobody sends a notification.
Moving old records somewhere new is the moment the quality of the original keys becomes everyone's problem. A migration is also the cheapest time to fix it, since everything is being touched anyway.
An entry that no longer looks like what you remember is either a rename or a different account entirely. Without an ID recorded, there is no way to tell those two apart.
Explore more AI-powered tools across research, content, and data.

Amazon Bestsellers Scraper — pull any ranking list with rank position, ASIN, price, and rating. No code, no Amazon API, all marketplaces. Try AllyHub free.

Amazon Product Scraper — pull structured product data from any Amazon domain without code or the Amazon API. Export JSON or CSV. Try AllyHub free.

Amazon Niche Finder — start from your interests, a category, or a rival, and get underserved niches scored on demand vs competition. Try AllyHub free.
Guides on recording accounts so the record survives.

Struggling to scrape Amazon product data without getting blocked? Learn safe, effective Amazon scraper methods using APIs, no-code tools, and Python.

Discover the 10 best Amazon competitor analysis tools used to track competitors, uncover keyword gaps, and understand why top listings outperform yours.

Discover the best Amazon SEO tools to boost your rankings, find high-converting keywords, and outpace competitors. Reviewed and ranked for e-commerce marketers.
What it is, cost, former handles, identity, and keeping a list current.
Something that returns the permanent numeric identifier behind an account. A lookup and a record are different asks. Most people arrive wanting one number and leave having changed how they store all of them.
Fifty handles, free. Longer lists, both directions in one pass, and re-running a list against its own last result, come with the paid plans.
No. X does not publish what an account used to be called, so any tool offering that is either guessing or working from a private archive. What this can do is store today's handle for you, which turns future renames into something you can detect yourself.
No, and it will not try. Accounts and people are different things; joining them up is not a feature here and not one we plan to add. If that is the requirement, this is the wrong tool for it.
A protected account still has an ID and it can still be resolved, since the handle and ID are public even when the posts are not. A deleted account is gone, and its handle may already belong to somebody else.
Most are a single box that converts one handle and forgets it. Here the whole list goes through together, the handle of the day is recorded next to each result, and the list waits for you to come back and check it.