Discord Username Checker — Bulk Availability in One Tokenless Call

Bulk-check up to 500 Discord usernames per run for availability in a single call — using Discord's official signup availability endpoint, no login, no token, no captcha. Returns per-handle status (available, taken, invalid), specific diagnostics (e.g. USERNAME_INVALID_CHARACTERS), the exact requested vs. resolved handle, and a completed OUTPUT summary. Built for username acquisition research, brand protection and handle portfolio management.

Main Use Cases

• Brand protection — check all your trademarks and brand-word handles at once; log validity endings for renewal decisions.
• Username acquisition research — find available handles for gamer tags, vanity handles and portfolio buying.
• Handle portfolio management — monitor a large list of your own handles in one scheduled run (validity ending, case resolution).
• Social-launch planning — reserve/claim planning for product names across Discord before release.

How It Works

The actor calls Discord's unauthenticated username-attempt endpoint (the same one the signup form uses) with a clean session per handle. Each handle gets its own response: whether the username is available, taken, or invalid — plus the specific errorCode when Discord rejects it (invalid characters, taken, etc.). Results land one row per checked handle; a run-level summary (totals: available/taken/invalid, checked list) is written to the OUTPUT record in the key-value store.

Check 500 Usernames in One Run — No Tokens, No Self-Bots

Discord name checkers that use self-bots or user tokens violate Discord's Terms of Service and burn tokens/accounts. This actor uses the public unauthenticated endpoint — the exact request the signup page makes — so one API run checks up to 500 usernames (pay-per-result billing). No Discord account, no token, no captcha solving.

Detect Exact Reasons a Handle Is Unavailable

Beyond yes/no, each row carries the precise errorCode Discord returned (USERNAME_INVALID_CHARACTERS, USERNAME_TOO_SHORT, USERNAME_TOO_LONG, USERNAME_TAKEN, USERNAME_INVALID_RATE_LIMIT, USERNAME_CLAIMED, USERNAME_ALREADY_CLAIMED) — so you can distinguish handles that are taken from ones that are simply invalid or rate-limited, and retry precisely.

Input

Field	Type	Required	Default	Notes
usernames	array	Yes	—	Handles to check, one per line — up to 500 per run.
maxConcurrency	integer	No	15	Parallel checks (1–50). Higher is faster but more likely to hit Discord rate limits.
proxyConfiguration	object	No	Apify residential	Leave the default (Apify residential proxy) on — unproxied requests get rate-limited and fail.

Example Input

{
  "usernames": ["coolname", "my_brand-name", "john doe", "ab"],
  "maxConcurrency": 15
}

Example Output

{
  "status": 200,
  "requestedUsername": "my brand",
  "username": "my_brand",
  "isAvailable": true,
  "errorCode": "",
  "attempts": 5,
  "checkedAt": "2026-09-23T09:41:05.943Z"
}

Taken / invalid uses the same shape

isAvailable: false with the matching errorCode (e.g. USERNAME_TAKEN or USERNAME_INVALID_CHARACTERS) and the resolved username Discord actually evaluated against.

Verify Availability With Attempts & Status Diagnostics

status echoes the HTTP response (200 ok, 429 rate-limited, etc.), attempts tells you how many tries a handle took, and checkedAt timestamps every check — so reruns can dedupe, and rate-limit noise is visible in data, not hidden in logs.

Integrations & Automation

• Apify API — pipe results into a handle-portfolio ledger or brand-watch alerting.
• Scheduling — daily validity-ending watchers, weekly brand-handle sweeps.
• Webhooks — notify when a monitored handle flips to available.
• Export — JSON, CSV, Excel.

Recommended schedule: daily for validity-ending alerts and brand monitoring; the JSON body in a scheduled task makes 500-handle sweeps a one-click routine.

Related Actors

• Discord Username Checker — the largest checker on the Store (4,300+ users), per-check billing.
• Discord Username Checker — single-username availability checks with retries.
• Discord Username Checker — availability + plus-suffix removal checks.
• Discord Member Scraper — extract members from public channels and servers.

FAQ

Why use this actor instead of a token/self-bot checker?

Token-based checkers (self-bots, user tokens) violate Discord's Terms of Service and get accounts banned; many open-source "checkers" on GitHub require tokens or captcha-solving. This actor uses Discord's official unauthenticated signup endpoint — tokenless by design, safe for accounts, and one run covers up to 500 handles.

What are alternatives to this actor / Discord username checking?

• maged120/discord-username-checker — $0.01/result.
• dev00/discord-username-checker — $0.005/check, single-handle.
• khadinakbar/discord-username-checker — $0.008/handle.
• GitHub open-source checkers — token-based, ToS-violating, account-burning.

How do I check a whole list of handles daily?

Create a task with your full list (≤500) as usernames, schedule it daily — the OUTPUT summary only marks totals; you diff dataset rows across days to see availability flips.

Why did a handle I know is available come back invalid?

Discord rejects handles violating its rules with specific codes — read the errorCode: spacing is resolved (e.g. my brand → my_brand), but unsupported characters or reserved words return e.g. USERNAME_INVALID_CHARACTERS.

How is availability checked without logging in?

Exactly like the public signup page: the actor POSTs the handle to Discord's unauthenticated availability endpoint with a fresh session and reads the JSON decision — the same yes/no the browser gets.

SEO Keywords

discord username checker, discord username availability, discord handle sniper, bulk discord name check, discord username taken, discord name validation, discord brand protection, discord handle monitoring, tokenless discord checker, discord username api, discord unique username, discord vanity handle, discord signup availability, discord username error codes

For AI Agents & LLM Apps

• Purpose: given an array of usernames (≤500), returns one row per handle with isAvailable, Discord's errorCode when rejected, the resolved username, attempt count and timestamp; run-level totals land in the OUTPUT record.
• Minimal input:

{ "usernames": ["coolname", "gamer123", "my-brand"] }

• Output field list: status, requestedUsername, username, isAvailable, errorCode, attempts, checkedAt
• OUTPUT summary keys: existingCount, availableCount, invalidCount, otherCount, checkedList

Behaviors an agent should know:

• 500 username hard cap per run — requests above 500 in usernames are rejected; split larger lists across runs.
• errorCode is the source of truth for why: empty string = checked OK; a non-empty code (e.g. USERNAME_INVALID_CHARACTERS, USERNAME_TOO_SHORT, USERNAME_TAKEN) means unavailable for that specific reason. isAvailable reflects the code.
• Repeated/aggressive runs hit USERNAME_INVALID_RATE_LIMIT — back off and raise maxConcurrency less aggressively; the actor handles retries internally.
• Apify residential proxy is the default — Discord rate-limits unproxied requests, so disabling proxyConfiguration will cause many checks to fail.
• Spacing is normalized (e.g. my brand → my_brand); case and most separator chars resolve silently.
• Billing: pay-per-result — result per checked username (price set by the publisher in monetization settings), + Actor Start ~$0.00005 (Apify default); a 500-handle run is a single cheap call.

Legal & Compliance Disclaimer

This actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Discord Inc. It uses only Discord's official public signup/username-availability endpoint — no logins, no user tokens, no self-bot behavior, no private data. Users are responsible for complying with Discord's Terms of Service and applicable law, including rate limits and platform rules; automated monitoring should respect Discord's documented usage policies.