Populate tabletop campaigns with instant characters and quests.
D&D Generator creates random content for tabletop role-playing games including characters, NPCs, monsters, treasure, encounters, taverns, and quests.
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": {
"type": "character",
"count": 1,
"results": {
"name": "Ashorshadow",
"race": "Elf",
"class": "Warlock",
"level": 6,
"background": "Criminal",
"alignment": "Lawful Good",
"stats": {
"strength": 10,
"dexterity": 12,
"constitution": 7,
"intelligence": 15,
"wisdom": 12,
"charisma": 10
},
"hitPoints": 20
}
}
}
About the D&D Generator API
Perfect for dungeon masters who need quick inspiration, game preparation tools, or procedural content generation for RPG applications.
What people use it for
- Game Preparation
- Generate NPCs, encounters, and quests for tabletop RPG sessions
- Character Creation
- Create random characters with stats, backgrounds, and personalities
- World Building
- Generate taverns, locations, and story hooks for campaign settings
- RPG Applications
- Integrate procedural content generation into gaming platforms
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 D&D Generator
Same data, same APIVerve account, same credit balance — one key works on all of them.
What types of tabletop content can I generate?
Can I generate multiple items in a single call?
What character attributes are returned in the response?
Are character stats, hit points, and levels included on the Free plan?
How far does the Starter plan go for generating D&D content?
Request parameters — GET /v1/dndgenerator
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 |
|---|---|---|---|
typeOptional | string | character | Content type to generateallcharacternpcmonstertreasureencountertavernquest+1default all |
countOptional | integer | 1 | Number of items to generate default 1 · range 1-10 |
curl "https://api.apiverve.com/v1/dndgenerator?type=character&count=1" \
-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/dndgenerator
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": {
"type": "character",
"count": 1,
"results": {
"name": "Ashorshadow",
"race": "Elf",
"class": "Warlock",
"level": 6,
"background": "Criminal",
"alignment": "Lawful Good",
"stats": {
"strength": 10,
"dexterity": 12,
"constitution": 7,
"intelligence": 15,
"wisdom": 12,
"charisma": 10
},
"hitPoints": 20
}
}
}
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 |
|---|---|---|---|
type | string | "character" | Type of D&D content that was generated |
count | number | 1 | Number of items returned in results |
results | object | {...} | Generated D&D content with details and attributes. A single object when count is 1, an array of that many objects when count is above 1. The fields below are the character shape; each other type returns its own fields |
name | string | "Ashorshadow" | Name of the generated character or entity |
race | string | "Elf" | Character race for D&D gameplay |
class | string | "Warlock" | Character class defining abilities and skills |
levelPremium | number | 6 | Character experience level in progression |
backgroundPremium | string | "Criminal" | Character background providing narrative context |
alignmentPremium | string | "Lawful Good" | Character moral alignment for roleplay |
statsPremium | object | {...} | Core ability scores for character statistics |
strengthPremium | number | 10 | Strength ability score value |
dexterityPremium | number | 12 | Dexterity ability score value |
constitutionPremium | number | 7 | Constitution ability score value |
intelligencePremium | number | 15 | Intelligence ability score value |
wisdomPremium | number | 12 | Wisdom ability score value |
charismaPremium | number | 10 | Charisma ability score value |
hitPointsPremium | number | 20 | Character hit points for combat |
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 | D&D 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/dndgenerator
No SDK to install — this is a plain HTTPS call to /v1/dndgenerator 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/dndgenerator" \
-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/dndgenerator
Install the Node.js SDK, then call the D&D Generator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/dndgeneratorconst res = await fetch("https://api.apiverve.com/v1/dndgenerator", {
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/dndgenerator
No SDK to install — this is a plain HTTPS call to /v1/dndgenerator 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/dndgenerator",
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/dndgenerator
Install the C# / .NET SDK, then call the D&D 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.DDGeneratorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/dndgenerator");
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/dndgenerator
No SDK to install — this is a plain HTTPS call to /v1/dndgenerator 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/dndgenerator", 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/dndgenerator
No SDK to install — this is a plain HTTPS call to /v1/dndgenerator 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/dndgenerator");
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/dndgenerator
No SDK to install — this is a plain HTTPS call to /v1/dndgenerator 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/dndgenerator")
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 D&D 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 — D&D 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 D&D Generator API.
Entertainment
- Advice Generator
- Bucket List
- Charades Generator
- Chess Move Validator
- Chuck Norris Jokes
- Compliment Generator
- D&D Generator
- Dad Jokes
- Fortune Teller
- Historical Events
- Love Calculator
- Magic 8-Ball
- Music Note Generator
- Never Have I Ever
- Pictionary Generator
- Random Facts
- Random Joke
- Random Pun
- Random Quote
- Scrabble Word Scorer
- Sudoku Generator
- Trivia Generator
- Truth or Dare
- Wordle Helper
Related articles
All articles →
Python API Tutorial: Your First APIVerve Call10 lines of Python. That's all it takes to call 300+ APIs. Here's the complete quickstart for Python developers.Read
REST vs GraphQL: Which Should You Use?Skip the theory. Here's when to use REST endpoints and when GraphQL actually makes sense.Read
Complete Guide to API Testing with PostmanMaster API testing with Postman. Learn collections, environments, automated tests, and debugging techniques.Read