Random Word is a simple tool for getting random words. It returns a random word.
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": {
// Random Word response payload
}
}
About the Random Word API
Random Word works by retrieving random words from the entire English dictionary and providing them in a structured format. It returns a random word, and its definition and pronunciation.
What people use it for
- Language Learning
- Learn new words by using the Random Word API to get random words. Use the data to expand your vocabulary and improve language skills
- Creative Writing
- Inspire creativity by using the Random Word API to get random words. Use the data to generate writing prompts and spark new ideas
- Word Games
- Play word games by using the Random Word API to get random words. Use the data to create puzzles, quizzes, and challenges for entertainment
- Educational Tools
- Develop educational tools by using the Random Word API to get random words. Use the data to create spelling tests, vocabulary exercises, and language quizzes
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 Random Word
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Random Word API do?
How do I authenticate Random Word API requests?
How much does the Random Word API cost?
How fast is the Random Word API?
What response formats does the Random Word API support?
What HTTP method does the Random Word API use?
Request parameters — GET /v1/randomwords
Call it with your key and nothing else. Any query string you send is ignored rather than rejected.
curl "https://api.apiverve.com/v1/randomwords" \
-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/randomwords
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": {
"word": "persevering",
"definitions": [
"Characterized by perseverance; persistent. -- Per`se*ver\"ing*ly, adv."
],
"pronunciation": "P ER0 S AH0 V IH1 R IH0 NG"
}
}
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 |
|---|---|---|---|
word | string | "persevering" | The randomly selected English word from dictionary |
definitionsPremium | array | [Characterized by perseverance; persistent. -- Per`se*ver"ing*ly, adv.] | Array of definitions explaining the word's meanings |
pronunciationPremium | string | "P ER0 S AH0 V IH1 R IH0 NG" | Phonetic pronunciation using ARPABET format notation |
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 | Random Word 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/randomwords
No SDK to install — this is a plain HTTPS call to /v1/randomwords 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/randomwords" \
-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/randomwords
Install the Node.js SDK, then call the Random Word API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/randomwordsconst res = await fetch("https://api.apiverve.com/v1/randomwords", {
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/randomwords
No SDK to install — this is a plain HTTPS call to /v1/randomwords 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/randomwords",
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/randomwords
Install the C# / .NET SDK, then call the Random Word 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.RandomWordusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/randomwords");
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/randomwords
No SDK to install — this is a plain HTTPS call to /v1/randomwords 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/randomwords", 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/randomwords
No SDK to install — this is a plain HTTPS call to /v1/randomwords 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/randomwords");
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/randomwords
No SDK to install — this is a plain HTTPS call to /v1/randomwords 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/randomwords")
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 Random Word 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 — Random Word 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 Random Word 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
Related articles
All articles →
Generate Barcodes for Inventory and ShippingCreate Code 128 and Code 39 barcodes programmatically. Tutorial for inventory systems, shipping labels, and asset tracking.Read 
Add Secure Password Generation to Your AppGenerate cryptographically secure passwords via API. Tutorial with code examples for signup flows, admin panels, and password managers.Read 
QR Codes Are Back (And This Time It's Different)Remember when QR codes were a punchline? Now they're everywhere. Here's why this time it stuck.Read