Overview
Each call picks a style, then one of that style's templates, then fills the template's named placeholders with random words. Every placeholder is replaced by a random entry from the style's word list for that placeholder type. If the style has no words for a placeholder, the shared common word list is used instead. Templates and word lists are loaded from a data file and cached in memory.
`style` is lowercased before use and must be one of dark, cosmic, elemental, tech, heroic or mystic; other values are rejected by validation. With no `style`, one is drawn at random from the available styles.
`name` is the finished name. `style` in the response is the style you requested, or the literal string `random` when you sent none, even though a specific style was used internally to build the name. If you need to know which style produced a name, pass the style explicitly.
Names are not checked for uniqueness or against existing characters and trademarks, and the same name can come back on separate calls, more often within a single style. If you need distinct names across calls, keep a record of the ones you have already issued and request again on a repeat. Both fields are returned on every plan.
Live Test Superhero Name Generator API →
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/superheroname?style=dark" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/superheroname?style=dark', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/superheroname?style=dark",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/superheroname?style=dark", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
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.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
styleOptional | string | Name styledarkcosmicelementaltechheroicmystic |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"name": "Lord Stalker",
"style": "dark"
}
}
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 |
|---|---|---|---|
name | string | "Lord Stalker" | Generated superhero name |
style | string | "dark" | Style used for name generation |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Game Development
- Generate hero names for RPGs and superhero games
- Creative Writing
- Find names for comic book or novel characters
- Team Building
- Create fun superhero personas for team activities
- Entertainment
- Generate amusing hero names for party games
Other ways to use Superhero Name Generator
Set up Superhero Name Generator on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Games: