Word Lexicon AnalyzerWord Lexicon Analyzer API

OnlineCredit Usage:1 per callRefreshed 1 month ago
avg: 246ms|p50: 233ms|p75: 255ms|p90: 281ms|p99: 335ms

Overview

To use Word Lexicon Analyzer, you need an API key. You can get one by creating a free account and visiting your dashboard.

GET Endpoint

URL
https://api.apiverve.com/v1/lexicon

Example

How to call the Word Lexicon Analyzer API in different programming languages.

cURL Request
curl -X GET \
  "https://api.apiverve.com/v1/lexicon?word=listen" \
  -H "X-API-Key: your_api_key_here"
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/lexicon?word=listen', {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

response = requests.get('https://api.apiverve.com/v1/lexicon?word=listen', headers=headers)

data = response.json()
print(data)
Go (net/http)
package main

import (
    "fmt"
    "io"
    "net/http"

)

func main() {
    req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/lexicon?word=listen", nil)

    req.Header.Set("X-API-Key", "your_api_key_here")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}
Example Response
{
  "status": "ok",
  "error": null,
  "data": {
    "word": "listen",
    "isAlphagram": false,
    "sortedForm": "eilnst",
    "isPalindrome": false,
    "hasAnagram": false,
    "isIsogram": true,
    "isPangramCandidate": false,
    "isScrabbleValid": true,
    "canBePalindromeAnagram": false
  }
}

Authentication

The Word Lexicon Analyzer API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the Word Lexicon Analyzer API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the Word Lexicon Analyzer API:

Analyze Word

ParameterTypeRequiredDescriptionDefaultExample
wordstringrequired
The word to analyze
-listen

Response

The Word Lexicon Analyzer API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.

Other Response Formats

XML Response
200 OK
<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <word>listen</word>
    <isAlphagram>false</isAlphagram>
    <sortedForm>eilnst</sortedForm>
    <isPalindrome>false</isPalindrome>
    <hasAnagram>false</hasAnagram>
    <isIsogram>true</isIsogram>
    <isPangramCandidate>false</isPangramCandidate>
    <isScrabbleValid>true</isScrabbleValid>
    <canBePalindromeAnagram>false</canBePalindromeAnagram>
  </data>
</response>
YAML Response
200 OK
status: ok
error: null
data:
  word: listen
  isAlphagram: false
  sortedForm: eilnst
  isPalindrome: false
  hasAnagram: false
  isIsogram: true
  isPangramCandidate: false
  isScrabbleValid: true
  canBePalindromeAnagram: false
CSV Response
200 OK
keyvalue
wordlisten
isAlphagramfalse
sortedFormeilnst
isPalindromefalse
hasAnagramfalse
isIsogramtrue
isPangramCandidatefalse
isScrabbleValidtrue
canBePalindromeAnagramfalse

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains the API response data if successful, otherwise null{...}

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

FieldTypeSample ValueDescription
wordstring"listen"
-
isAlphagrambooleanfalse
-
sortedFormstring"eilnst"
-
isPalindromebooleanfalse
-
hasAnagrambooleanfalse
-
isIsogrambooleantrue
-
isPangramCandidatebooleanfalse
-
isScrabbleValidbooleantrue
-
canBePalindromeAnagrambooleanfalse
-

Headers

Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →

GraphQL AccessALPHA

Access Word Lexicon Analyzer through GraphQL to combine it with other API calls in a single request. Query only the word lexicon analyzer data you need with precise field selection, and orchestrate complex data fetching workflows.

Test Word Lexicon Analyzer in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  lexicon(
    input: {
      word: "listen"
    }
  ) {
    word
    isAlphagram
    sortedForm
    isPalindrome
    hasAnagram
    isIsogram
    isPangramCandidate
    isScrabbleValid
    canBePalindromeAnagram
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The Word Lexicon Analyzer API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →

Rate Limiting

Word Lexicon Analyzer requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →

Error Codes

The Word Lexicon Analyzer API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →

SDKs for Word Lexicon Analyzer

Official Word Lexicon Analyzer packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

No-Code Integrations

Word Lexicon Analyzer works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Frequently Asked Questions

How do I get an API key for Word Lexicon Analyzer?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for Word Lexicon Analyzer and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does Word Lexicon Analyzer cost?

Each successful Word Lexicon Analyzer API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful word lexicon analyzer lookups.

Can I use Word Lexicon Analyzer in production?

The free plan is for testing and development only. For production use of Word Lexicon Analyzer, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.

Can I use Word Lexicon Analyzer from a browser?
Yes! The Word Lexicon Analyzer API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
What happens if I exceed my Word Lexicon Analyzer credit limit?

When you reach your monthly credit limit, Word Lexicon Analyzer API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?