Skip to content
Robotics-now edited this page Jun 17, 2026 · 7 revisions
OPEN API



Language API Key Format


Definitions · Synonyms · Antonyms · Part of Speech — in one free API call.


@Robotics-now @prajasus2308

Get a Key · Try It · Response Format · Errors


🚀 Getting Started

Tip

We suggest that you visit the website.

Step 1 — Get your free API key

Visit /client and fill in your name and email. Your key arrives in your inbox within seconds.

Your key looks like this: oa_f360fb6fe00b1be5b109e9

25 characters · always starts with oa_ · one per email · always free.

Step 2 — Make your first request
GET /api/{your_key}/eng/{word}
curl https://yourhost/api/oa_f367fb6fe04b1be5b129e9/eng/eloquent

Response Format

{
  "word": "eloquent",
  "lang": "eng",
  "results": [
    {
      "definition": "Having the power of expressing strong emotions or arguments in a fluent and convincing way.",
      "pos": "adj",
      "pos_name": "Adjective",
      "synonyms": "fluent, expressive, articulate",
      "antonyms": "inarticulate, silent"
    }
  ],
  "error": null
}

A word can return multiple results if it has more than one meaning. Each result is a separate object in the results array.


Spell Correction

Misspelled a word? The API detects it automatically and returns the closest match. The corrected spelling appears in the "word" field so you always know what was looked up.

graph TD
    Start([API is called]) -->|No error| ValidateKey[Validates API Key]
    Start -->|Error| LocalError[Local error]

    ValidateKey -->|fail| InvalidKey(["Key: Error <br/> Invalid or missing API key. Get one at /client"])
    ValidateKey -->|valid| ValidateLang[Validates Language]

    ValidateLang -->|fail| InvalidLang(["Key: Error <br/> Invalid language"])
    ValidateLang -->|success| DBCheck[Looks for word in database]

    DBCheck -->|found| ReturnNormal(["Returns Normal JSON data"])
    DBCheck -->|is not found| SpellCorrect[Spell correct]

    SpellCorrect --> LookClose[Look for close matches]
    
    LookClose -->|is found| ReturnCorrected(["Returns with corrected word <br/> Key: Error <br/> Corrected"])
    LookClose -->|can't be found| Gemini[Goes to Gemini]

    Gemini --> ReturnCorrected

    %% Success Styles (Green)
    linkStyle 0,3,5,6,9 stroke:#39FF14,stroke-width:2px;

    %% Failure Styles (Red)
    linkStyle 1,2,4 stroke:#FF3131,stroke-width:2px;

    %% "Not Found" / Discovery Styles (Blue)
    linkStyle 7,10,11 stroke:#00D4FF,stroke-width:2px;
Loading

Endpoints

GET /api/{key}/eng/{word}

This gives you the same json data as listed above.


Errors

Status Meaning Fix
401 Invalid API key Copy your key exactly from the email
500 Server error Try again or contact us
404 Page not found Use the default redirect


💬 Feedback

Something broken or a word missing? Open /client, scroll to the feedback form, leave a rating and a message. Email is optional but helps us follow up.


📋 Quick Reference

Base URL /api/{key}/eng/{word}
Language eng (English)
Key format oa_ + 22 hex chars = 25 total
Key cost Free
Keys per email 1
Response format JSON
Spell correction Automatic

Star on GitHub

Clone this wiki locally