Hangman Word Generator provides random words for hangman games with category filtering and difficulty levels based on word length.
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": {
// Hangman Word Generator response payload
}
}
About the Hangman Word Generator API
Includes word length, unique letter count, and suggested maximum guesses. Returns printable HTML for offline play.
What people use it for
- Game Development
- Power hangman games with curated word lists
- Educational Apps
- Create vocabulary games with categorized words
- Party Games
- Generate words for group hangman activities
- Language Learning
- Build vocabulary exercises with themed word lists
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 Hangman Word Generator
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Hangman Word Generator API do?
How do I authenticate Hangman Word Generator API requests?
How much does the Hangman Word Generator API cost?
How fast is the Hangman Word Generator API?
What response formats does the Hangman Word Generator API support?
What HTTP method does the Hangman Word Generator API use?
Request parameters — GET /v1/hangmanword
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.
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
categoryOptionalPremium | string | animals | Word categoryrandomanimalscountriesfoodssportscolorsoccupationsdefault random |
difficultyOptional | string | medium | Difficulty leveleasymediumharddefault medium |
countOptionalPremium | integer | 1 | Number of words default 1 · range 1-10 |
imageOptionalPremium | boolean | true | Set to true to generate a downloadable puzzle image default false |
curl "https://api.apiverve.com/v1/hangmanword?category=animals&difficulty=medium&count=1&image=true" \
-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/hangmanword
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": {
"words": [
{
"word": "PORCUPINE",
"blanks": "_ _ _ _ _ _ _ _ _",
"length": 9,
"uniqueLetters": 8,
"difficulty": "medium",
"category": "animals",
"maxGuesses": 7
}
],
"count": 1,
"difficulty": "medium",
"category": "animals",
"html": "<html><head><title>Hangman Words</title><style>body {font-family: Arial, sans-serif; padding: 20px; max-width: 600px; margin: 0 auto;}h1 {text-align: center;}.word-card {background: #f5f5f5; padding: 25px; margin: 20px 0; border-radius: 10px; text-align: center;}.blanks {font-size: 32px; font-family: monospace; letter-spacing: 8px; margin: 20px 0;}.info {font-size: 14px; color: #666;}.category {background: #2196F3; color: white; padding: 5px 15px; border-radius: 20px; display: inline-block; margin-bottom: 15px;}.hangman {font-size: 40px; margin: 20px 0;}</style></head><body><h1>Hangman</h1><div class='word-card'><span class='category'>animals</span><div class='hangman'>💀</div><div class='blanks'>_ _ _ _ _ _ _ _ _</div><div class='info'>9 letters | 8 unique | Max 7 wrong guesses</div></div></body></html>",
"image": {
"imageName": "d6e69eac-546c-4a2b-8413-2b65fd4a109a_hangman.png",
"format": ".png",
"downloadURL": "https://storage.googleapis.com/apiverve/APIData/hangmanword/d6e69eac-546c-4a2b-8413-2b65fd4a109a_hangman.png?GoogleAccessId=635500398038-compute%40developer.gserviceaccount.com&Expires=1766010232&Signature=En2KyqlZwODc1wOwqTyuVtHq5LqNHuFXdn9Xw6nKlwhmB2SMV9HTSwpfVi9SS1tC6tnq0sntOPZ4ANH8McPxnjqFJhT2VKXAObQSRha6IHR9J1ymSpH%2F5TJ4AmlRZ8nLvW1jXPWjNvnUvgrd%2BfN5zK1u9pQ1MYatBVeg63y0rOdxSPcJBMX%2BDdgzG1lJK3Rmugr0HWoVb9ocfk8R%2FGVPsLXzHuwZySOk%2BCyQ1IZAWoqYuX7v3wKf3JHhiK9ZQ%2FG58j2dSychhcDsBZyKXN1wSpRsRB%2F03F6zKkykiiVw%2FuGr9kjPGK1QRJ9XJZzLZ0Z9S%2BQ6ZoD5FrCJwTIVXTPHxg%3D%3D",
"expires": 1766010232291
}
}
}
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 |
|---|---|---|---|
words | array[1] | Array of hangman word objects with metadata | |
word | string | "PORCUPINE" | The actual word to guess in uppercase |
blanks | string | "_ _ _ _ _ _ _ _ _" | Blank representation of word for display |
length | number | 9 | Total number of letters in the word |
uniqueLetters | number | 8 | Count of distinct letters in the word |
difficulty | string | "medium" | Difficulty level of the word difficulty |
category | string | "animals" | Category classification of the word |
maxGuesses | number | 7 | Recommended maximum wrong guesses allowed |
count | number | 1 | Number of words returned in response |
difficulty | string | "medium" | Overall difficulty level requested |
category | string | "animals" | Overall category requested in query |
htmlPremium | string | "<html><head><title>Hangman Words</title><style>body {font-family: Arial, sans-serif; padding: 20px; max-width: 600px; margin: 0 auto;}h1 {t… | Rendered HTML for offline hangman game play |
image | object | {...} | |
imageNamePremium | string | "d6e69eac-546c-4a2b-8413-2b65fd4a109a_hangman.png" | Unique identifier name of generated image file |
formatPremium | string | ".png" | File format of the generated image file |
downloadURLPremium | string | "https://storage.googleapis.com/apiverve/APIData/hangmanword/d6e69eac-546c-4a2b-8413-2b65fd4a109a_hangman.png?GoogleAccessId=635500398038-co… | Signed URL for downloading the generated image |
expiresPremium | number | 1766010232291 | Unix timestamp when download URL expires |
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 | Hangman Word 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/hangmanword
No SDK to install — this is a plain HTTPS call to /v1/hangmanword 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/hangmanword" \
-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/hangmanword
Install the Node.js SDK, then call the Hangman Word Generator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/hangmanwordconst res = await fetch("https://api.apiverve.com/v1/hangmanword", {
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/hangmanword
No SDK to install — this is a plain HTTPS call to /v1/hangmanword with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/hangmanword",
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/hangmanword
Install the C# / .NET SDK, then call the Hangman Word 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.HangmanWordGeneratorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/hangmanword");
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/hangmanword
No SDK to install — this is a plain HTTPS call to /v1/hangmanword 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/hangmanword", 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/hangmanword
No SDK to install — this is a plain HTTPS call to /v1/hangmanword 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/hangmanword");
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/hangmanword
No SDK to install — this is a plain HTTPS call to /v1/hangmanword 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/hangmanword")
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 Hangman Word 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 — Hangman Word 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 Hangman Word Generator API.
Games
- Acrostic Puzzle Generator
- Anagram Puzzle Generator
- Card Deck Shuffler
- Coin Flipper
- Crossword Generator
- Cryptogram Generator
- Dice Roller
- Fill in the Blanks Generator
- Fortune Cookie Generator
- Game Character Generator
- Hangman Word Generator
- Lottery Number Generator
- Mad Libs Generator
- Maze Generator
- Rock Paper Scissors
- Slot Machine Simulator
- Spelling Bee Generator
- Superhero Name Generator
- Word Ladder Generator
- Word Scramble Generator
- Word Search Generator
Related articles
All articles →
Add Daily Horoscopes to Your App in 5 MinutesBuild a horoscope feature your users will actually check daily. Working code included.Read
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read