Twitter / X Username Checker

Bulk-check whether Twitter / X usernames (handles) are available or already taken. Feed in a list of handles and get back a clean, structured result for each one — available or not. Duplicates and invalid handles are filtered out automatically, so you never waste a check.

What does Twitter / X Username Checker do?

This Actor takes a list of X (Twitter) handles and tells you, for each one, whether it can still be registered. It's built for speed and runs entirely on the Apify platform, so you get API access, scheduling, integrations, proxy rotation, and run monitoring out of the box — no browser or local setup required.

Why use Twitter / X Username Checker?

• Brand protection — confirm your brand or product handle is still free before someone else grabs it.
• Handle hunting — find short, clean, or on-brand handles that are still available.
• Bulk research — check hundreds of handles in one run instead of typing them one by one.
• Automation — schedule recurring checks and wire the results into your own tools via the API.

How to use Twitter / X Username Checker

1. Open the Actor and go to the Input tab.
2. Paste your list of handles (one per line). The @ prefix is optional and case doesn't matter.
3. (Optional) Adjust the proxy settings.
4. Click Start and wait for the run to finish.
5. Download your results from the Output tab.

Input

Field	Description
Usernames to Check	The list of handles to verify (up to 1000 per run). @ is optional, case is ignored, and duplicates are removed before checking. Unique handles beyond the first 1000 are skipped.
Proxy Configuration	Proxy settings. Residential proxies are recommended for large lists.

Example input:

{
    "usernames": ["jack", "my_cool_unclaimed_handle", "@SomeBrand"],
    "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Output

Each handle becomes one row in the dataset. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

[
    {
        "username": "jack",
        "available": false,
        "error": null
    },
    {
        "username": "my_cool_unclaimed_handle",
        "available": true,
        "error": null
    }
]

Data table

Field	Type	Description
username	text	The normalized handle that was checked.
available	boolean	true if the handle can be registered, false if taken, null if it couldn't be checked.
error	text	Populated only for invalid handles or handles that couldn't be checked.

How much does it cost?

Cost scales with the size of your list — you're billed per result, and each handle produces exactly one result. Duplicate and invalid handles are filtered before any checks run, so you only pay for real, unique handles. A run of a few hundred handles typically costs a small fraction of a compute unit.

Tips

• For large lists, keep the default residential proxy setting on to avoid rate limiting.
• If you see rows with an error, re-run just those handles.
• Valid X handles are 1-15 characters, letters, numbers, and underscores only — anything else is flagged as invalid without spending a check.

FAQ, disclaimers, and support

Is this legal? The Actor only checks public handle availability — the same information anyone sees when viewing a profile or signing up. It does not access private data or log into any account. You are responsible for complying with X's Terms of Service and applicable laws.

Why is a handle marked unavailable when no profile is visible? X reserves many handles (suspended, deactivated, or held) even when no public profile shows. Availability reflects whether the handle can be registered, not whether a profile currently exists.

Found a bug or need a custom version? Open an issue on the Actor's Issues tab and we'll take a look.