Check username availability

Reports whether a candidate username is free to claim before the user commits to a full signup or migration flow. Intended for debounced calls as the user types. Returns available: false when the username already belongs to another AppUser; returns HTTP 400 (VALIDATIONFAILED) when the username fails the format rules (3–30 chars; starts with a lowercase letter; lowercase letters, digits, and internal . - separators). Note: the DB unique constraint enforced at signup/migrate time remains the source of truth — a username reported as available can still race with a concurrent claim.

Access: Public endpoint.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required

Candidate username (3–30 chars; must start with a lowercase letter; may contain lowercase letters, digits, and the separators _ . - between alphanumeric characters).

Responses

400

Username failed format validation.

429

Too many username availability checks from this client. The error details include retryAfterSec (seconds until the window resets).

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json