Suggest relevant handles for new users the moment they sign up.
Username Generator creates handle suggestions from a person's name or email address. It returns an array of suggested usernames based on the input, while paid plans can request multiple options at once.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"count": 10,
"suggestions": [
"doxologysean",
"sean",
"downpoursean",
"tonsilarsean",
"interdependencysean",
"seantrivant",
"seansquireen",
"seankillifish",
"seantiltyard",
"seaninterrupt"
],
"email": "[email protected]"
}
}
About the Username Generator API
Username Generator works by generating usernames based on the specified criteria. It uses advanced algorithms to generate usernames and returns a list of usernames.
What people use it for
- Player Profile Setup
- Gaming platforms generate candidate gamer tags from a new player's real name during account creation.
- Forum Handle Autofill
- To speed up community registration, web forums present handle suggestions derived from an applicant's entered email address.
- Corporate Directory Provisioning
- When creating new workforce accounts, IT identity systems supply employee names to reserve standard internal usernames.
- Student Account Provisioning
- Feed enrolled student names into the endpoint to recommend clean login handles across school portals and learning apps.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Username Generator
Same data, same APIVerve account, same credit balance — one key works on all of them.
Can I generate handles from both full names and email addresses?
Does the API return multiple username suggestions in a single call?
Can I specify the number of generated usernames on the Free plan?
What happens if I omit the count parameter in my request?
What would generating usernames for 10,000 signups a month cost me?
Request parameters — GET /v1/usernamegenerator
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
emailRequired | string | [email protected] | The email address to generate usernames from email |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
countOptionalPremium | integer | 10 | The number of usernames to generate default 1 · range 1-10 |
curl "https://api.apiverve.com/v1/usernamegenerator?email=sean%40mail.com&count=10" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/usernamegenerator
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"count": 10,
"suggestions": [
"doxologysean",
"sean",
"downpoursean",
"tonsilarsean",
"interdependencysean",
"seantrivant",
"seansquireen",
"seankillifish",
"seantiltyard",
"seaninterrupt"
],
"email": "[email protected]"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
count | number | 10 | Total number of usernames generated in response |
suggestions | array | [doxologysean, ...] | Array of generated username suggestions for user |
email | string | "[email protected]" | Email address used to generate usernames |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Username Generator calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/usernamegenerator
No SDK to install — this is a plain HTTPS call to /v1/usernamegenerator with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/usernamegenerator" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/usernamegenerator
Install the Node.js SDK, then call the Username Generator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/usernamegeneratorconst res = await fetch("https://api.apiverve.com/v1/usernamegenerator", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/usernamegenerator
Install the Python SDK, then call the Username Generator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-usernamegeneratorimport requests
res = requests.get(
"https://api.apiverve.com/v1/usernamegenerator",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/usernamegenerator
Install the C# / .NET SDK, then call the Username Generator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.UsernameGeneratorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/usernamegenerator");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/usernamegenerator
No SDK to install — this is a plain HTTPS call to /v1/usernamegenerator with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/usernamegenerator", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/usernamegenerator
No SDK to install — this is a plain HTTPS call to /v1/usernamegenerator with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/usernamegenerator");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/usernamegenerator
No SDK to install — this is a plain HTTPS call to /v1/usernamegenerator with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/usernamegenerator")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Username Generator form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Username Generator API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Username Generator API.
Data Generation
- Acronym Generator
- Baby Name Generator
- Barcode Generator
- Bingo Card Generator
- Boggle Board Generator
- Captcha Generator
- Chart Generator
- Color Palette Generator
- Comment Generator
- Company Name Generator
- Cron Expression Generator
- Cuid Generator
- GUID Generator
- Hashtag Generator
- IMEI Generator
- Initialism Generator
- JSON Schema Generator
- Lorem Ipsum Generator
- Password Generator
- QR Code Generator
- Random Data Generator
- Random Identity Generator
- Random User Generator
- Random Word
- Short Code Generator
- Sitemap Generator
- Test Card Generator
- TOTP Generator
- ULID Generator
- User Agent Generator
- Username Generator
- UUID Generator