How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Wordnik Account API

API-key status and user authentication operations.

Wordnik Account API is one of 5 APIs that Wordnik publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Account. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 5 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.wordnik.com/v4.

5 operations 4 paths 4 schemas 4 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.wordnik.com/v4
Authentication
API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

Wordnik Account API declares 2 security schemes for authenticating requests. An API key is passed in the query as api_key (api_key). An API key is passed in the header as auth_token (auth_token). By default, every request must be authenticated.

  • api_key — Wordnik issues per-account API keys; pass via the apikey query parameter on every request.
  • auth_token — User auth token returned by /account.json/authenticate/{username}; required for user-scoped account and word-list operations.

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 4 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Account 5

API-key status and user authentication operations.

GET
/account.json/apiTokenStatus
Return API Token Status
getApiTokenStatus 1 param → 200
GET
/account.json/authenticate/{username}
Authenticate A User
authenticate 2 params → 200
POST
/account.json/authenticate/{username}
Authenticate A User (POST Body)
authenticatePost 1 param body → 200
GET
/account.json/user
Return The Currently Authenticated User
getLoggedInUser 1 param → 200
GET
/account.json/wordLists
Return The Authenticated User's Word Lists
getWordListsForLoggedInUser 3 params → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are WordList (11 properties), User (8 properties), ApiTokenStatus (6 properties), AuthenticationToken (3 properties). Each schema is shown below with its type and property counts.

AuthenticationToken
object
3 properties
User
object
8 properties
ApiTokenStatus
object
6 properties
WordList
object
11 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wordnik-account-api-openapi.yml Raw ↑

Other APIs Wordnik publishes across the network.

Wordnik Word API
Wordnik Word List API
Wordnik Word Lists API
Wordnik Words API
Where this information came from

This is an independent, third-party profile of Wordnik Account API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.