Random Lexicon
Dictionaries
Random words and definitions using optional filters
Dictionary Data
Verified today: 100% uptime
Free on the Basic plan for nonprofit and research use. Commercial use gets a free trial, then needs a paid plan.
Send it as ?api_key=YOUR_KEY
Checked by hand on 2026-10-24 against Wordnik API pricing. Providers change their terms, so confirm on their own pages before you commit.
API key
Required, free signup
HTTPS
Supported
Browser calls
No, needs a proxy
Status
Live · 100/100
Wordnik provides programmatic access to dictionary data. Delivered over secure HTTPS protocols, it exposes structured endpoints designed to integrate cleanly into modern frontend frameworks, backend microservices, and automated data pipelines without requiring local database provisioning.
Engineers building web dashboards, mobile applications, CLI utilities, or background cron workers in need of reliable dictionaries data feeds.
Consuming Wordnik removes the operational overhead of running custom scrapers, orchestrating headless browser fleets, or manually seeding and maintaining a local database. Instead of reverse-engineering volatile DOM layouts or dealing with anti-bot IP blocks, your application connects directly to a standardized JSON interface designed for backend ingestion with consistent schema schemas. Dedicated authentication ensures rate quotas and credential tracking per project environment.
Last checked 2026-10-24. Measured independently, not self-reported by the provider.
Practical real-world patterns for integrating Wordnik into software systems.
Embed data and functionality from Wordnik directly into application onboarding, profile enrichment, or reporting dashboards.
Periodically extract updates from Wordnik to generate daily digests, analytics reports, or Slack notifications.
Provide real-world mock data and operational endpoints for client demos, portfolio apps, or MVP validation.
Production-ready starting templates with error handling for Wordnik.
// Requires an API key. Check the docs for whether it goes in a header or a query parameter.
// Modern native fetch with error handling
async function callApi() {
try {
const response = await fetch('https://developer.wordnik.com/api/v1/resource', {
method: 'GET',
headers: {
'Authorization': 'Bearer YOUR_API_KEY',
Accept: 'application/json',
},
});
if (!response.ok) {
throw new Error(`HTTP ${response.status}: ${response.statusText}`);
}
const data = await response.json();
console.log('Response payload:', data);
return data;
} catch (error) {
console.error('API request failed:', error);
throw error;
}
}
// callApi();This API does not send CORS headers, so a browser will block a direct call from your front end. Call it from your server, or put a small proxy in front of it.
Inspect the expected JSON structure returned by Wordnik.
Authentic sample payload structure to evaluate schema attributes before integration.
{
"status": 200,
"api": "Wordnik",
"endpoint": "/wordnik",
"data": {
"id": 101,
"title": "Wordnik Sample Payload",
"description": "Dictionary Data",
"verified": true,
"category": "Dictionaries",
"updated_at": "2026-10-24T07:40:09.547Z"
},
"meta": {
"response_time_ms": 1914,
"cached": false
}
}Technical factors to keep in mind when integrating Wordnik into production environments.
Avoid triggering rate limits on public feeds by caching response payloads in Redis, Vercel KV, or standard HTTP Cache-Control headers with a 5-to-15 minute TTL.
Never expose private API keys in client-side JavaScript or bundle environments. Proxy requests through a Next.js API route or serverless backend to keep secret keys out of public DevTools inspection.
This API does not send Access-Control-Allow-Origin response headers. Direct fetch() calls from browser JavaScript will fail due to Same-Origin Policy. Route your calls through a server backend or lightweight edge proxy.
Always inspect response.ok before executing response.json(). Upstream services returning 4xx or 502 Bad Gateway often serve HTML error pages, which cause syntax errors when parsed as JSON.
Aggregated from 2 public sources (public-api-lists, public-apis), then normalised and checked by us.
Report an issue with this listing ↗Dictionaries
Random words and definitions using optional filters
Dictionaries
Collaborative dictionary data
Dictionaries
The CTP API provides integration methods for connecting the functionality and content of the Chinese Text Project with external web applications. It consists of a Plugin API for adding external tools and a JSON API for leveraging CTP features externally.
Dictionaries
Synonyms, thesaurus and antonyms information for any given word
Dictionaries
This API allows users to access word definitions, phonetics, and usage examples by sending a request with a specific English word. It serves as a resource for developers building applications that require linguistic data, enhancing learning and communication tools.
Dictionaries
Bilingual Dictionary and Thesaurus Data
Answered from what our own scheduled checks found, not from the provider's marketing.
Free on the Basic plan for nonprofit and research use. Commercial use gets a free trial, then needs a paid plan. The cheapest paid plan: Hobby: $10 a month for 1,000 calls an hour. Checked on 2026-10-24.
Yes, and it is free: you get one by signing up. Send it as ?api_key=YOUR_KEY.
1. Create a free Wordnik account. 2. Log in to the Wordnik developer site and request an API key. 3. Pass it as the api_key query parameter.
Basic plan: 100 calls an hour, $0.
Not directly. Wordnik did not return CORS headers when we checked, so the browser will block your page from reading the response even though the request itself succeeds. Call it from a server, or put a small proxy in front of it.
Yes, as of 2026-10-24. Our automated check reached Wordnik and recorded a 100% reliability score with a median response time of 1914 ms. We re-check on a schedule, and this page updates with the result.