Documentation
The Lexicala Web API is a RESTful API that provides quality lexical data of K Dictionaries originating from lexicographic resources for 50 languages, including monolingual cores as well as numerous bilingual pairs and multilingual combinations. All endpoints return data in JSON format, except for two endpoints that return data in JSON-LD (RDF) format.
GETTING STARTED
To utilize the API, registration is required through our RapidAPI page. Upon registration, you will receive an X-RapidAPI-Key, which is required to access the API endpoint.
The base URL for the API is https://lexicala1.p.rapidapi.com. You can find code snippets and test various requests on our RapidAPI page.
LANGUAGES AND DATA
- Information about the languages available through the API can be obtained with GET /languages, including the full names corresponding to language codes, and the languages available in the various resources* (in order to use the links below, use your X-RapidAPI-Key).
By default, the results are from K Dictionaries’ Global series. In addition, there are data from the Password series, the Password-associated MultiGloss series, and Random House Webster’s College Dictionary.
- Global includes 25 monolingual cores (see list below), to many of which are added translation equivalents, producing diverse bilingual pairs and multilingual combinations.
- Password consists of an English learner’s dictionary core, translated into 46 languages.
- MultiGloss is based on Password bilingual glossaries to English, which are automatically expanded to 44 more languages.
- Random House Webster’s College Dictionary is a legacy comprehensive dictionary of the English language.
More information about the different resources is available on the Lexicala website.
The following is a list of all the source languages (monolingual cores), and the target languages available for each one.
| Source language | Target languages in Global | Target languages in Password | * Target languages in MultiGloss |
|---|---|---|---|
| Arabic (ar) | de | English + 44 languages | |
| Catalan (ca) | English + 44 languages | ||
| Chinese Simplified (zh) | en, fr, ja | English + 44 languages | |
| Chinese Traditional (tw) | |||
| Croatian (hr) | English + 44 languages | ||
| Czech (cs) | English + 44 languages | ||
| Danish (da) | de, en, es, fr, ko | English + 44 languages | |
| Dutch (nl) | de, en, es, fr | English + 44 languages | |
| English (en) | br, da, es, fr, ja, no, sv | af, ar, az, bg, br, ca, cs, da, de, el, es, et, fa, fi, fr, fy, he, hi, hr, hu, id, is, it, ja, ko, lt, lv, ml, nl, no, pl, prs, ps, pt, ro, ru, sk, sl, sr, sv, th, tr, tw, uk, ur, vi, zh | |
| Estonian (et) | English + 44 languages | ||
| Finnish (fi) | English + 44 languages | ||
| French (fr) | ar, br, da, de, el, en, es, he, it, ja, nl, no, pl, pt, ru, sv, tr | English + 44 languages | |
| Frisian (fy) | English + 44 languages | ||
| German (de) | ar, br, da, en, ja, nl, no, sv, tr | English + 44 languages | |
| Greek (el) | fr | English + 44 languages | |
| Hebrew (he) | en, fr, ko | English + 44 languages | |
| Hindi (hi) | |||
| Hungarian (hu) | English + 44 languages | ||
| Indonesian (id) | English + 44 languages | ||
| Italian (it) | br, en, ja, no | English + 44 languages | |
| Japanese (ja) | de, en, es, fr, zh | English + 44 languages | |
| Korean (ko) | ja | English + 44 languages | |
| Latin (la) | fr | ||
| Latvian (lv) | English + 44 languages | ||
| Malay (ml) | English + 44 languages | ||
| Norwegian (no) | de, en, es, fr, it, ko, pl | English + 44 languages | |
| Polish (pl) | en, fr, no | English + 44 languages | |
| Portuguese Brazil (br) | de, en, es, fr, it | English + 44 languages | |
| Portuguese Portugal (pt) | fr | English + 44 languages | |
| Russian (ru) | fr, ja | English + 44 languages | |
| Slovenian (sl) | English + 44 languages | ||
| Spanish (es) | br, da, en, ja, nl, no, sv | English + 44 languages | |
| Swedish (sv) | de, en, es, fr | English + 44 languages | |
| Thai (th) | English + 44 languages | ||
| Turkish (tr) | de, fr | English + 44 languages | |
| Ukrainian (uk) | English + 44 languages | ||
| * MultiGloss 44 Languages: af, ar, az, bg, br, ca, da, de, el, es, et, fa, fi, fr, fy, he, hi, hr, hu, id, is, it, ja, ko, lt, lv, ms, nl, no, pl, pt, ro, ru, sk, sl, sr, sv, th, tr, tw, uk, ur, vi, zh | |||
Endpoints
See below how to specify which resource to look in, when querying the API for a specific language.
GET /search and GET /search-entries-lite
Query entries with these endpoints. Both accept identical parameters and differ only in the response shape:
* GET /search returns abridged entries containing the entry ID, source language code, headword text, part of speech, and the different senses with their sense ID and definition.
* GET /search-entries-lite returns full entries.
To obtain translations for entries, use the dedicated translation endpoints described below.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| source | string | No | Which resource to look in: global (default), password, multigloss, random. |
| language | string | No | Source language code (e.g. ar, br, cs, da, de, en, es, …). |
| text | string | Yes | The headword to search for. |
| pos | string | No | Part of speech filter (e.g. noun, verb, …). |
| number | string | No | Grammatical number filter (e.g. singular, plural, …). |
| gender | string | No | Grammatical gender filter (e.g. masculine, feminine, …). |
| subcategorization | string | No | Subcategorization filter. |
| monosemous | boolean | No | Restrict results to single-sense entries only. |
| polysemous | boolean | No | Restrict results to multiple-sense entries only. |
| morph | boolean | No | Search the text in both headwords and inflected forms, including supplemental morphological lists (default: false). |
| analyzed | boolean | No | Apply a stemmer algorithm that strips words to their stem and disregards diacritics and case (default: false). |
| antonyms | boolean | No | Search the text as an antonym. |
| synonyms | boolean | No | Search the text as a synonym. |
For example: [Go to Lexicala API at Rapid](https://lexicala1.p.rapidapi.com/search?source=global&language=es&text=azul) *
This query returns all the entries in the Spanish resource of the Global series with the headword “azul”.
The Morph Parameter
Setting morph = true looks for all the inflected forms (as well as headwords) contained both in the dictionary data and in the [external morphological lists](https://lexicala1.p.rapidapi.com/search?source=global&language=en&text=houses&morph=true). *
Searching “houses” will return the entry “house” (noun), even though the word “houses” is not an entry in the English resource (it’s the plural form of “house”).
The Analyzed Parameter
Setting analyzed = true looks for inflected forms by [applying the stemmer](https://lexicala1.p.rapidapi.com/search?source=global&language=en&text=working&analyzed=true). *
This query returns the entries “working” (adj.), “work” (verb), “work” (noun), “hard-working” (adjective), “working class” (noun), “work on” (verb), and any other entry with the stem “work” in its headword.
The stemmer also disregards diacritics and vocalization (e.g. in Arabic and Hebrew) and removes case-sensitivity (uppercase/lowercase).
Antonym and Synonym Search
It is possible to search the headwords for either antonyms or synonyms, or both simultaneously, using the antonyms and synonyms parameters in the table above.
GET /entries-lite/{entry_id}
Retrieve a complete entry by its unique entry ID. The result JSON object contains grammar, IPA, orthography, and a list of available translation languages for each sense.
The result contains the following fields:
– `id` (string) — the unique entry ID
– `source` (string) — the resource from which the entry is taken (`global`, `password`, `multigloss`, `random`)
– `language` (string) — a two-character language code
– `version` (number) — the version of the resource
– `related_entries` (array of strings) — IDs of related entries
– `headword` (object/array of objects) — extensive syntactic and phonetic information on the lemma
– `senses` (array of objects) — disambiguation of the lemma into senses, including syntactic, phonetic and semantic information, with `available_translations` listing which translation languages are available
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| entry_id | string | Yes | The unique entry ID (in the URL path). |
GET /senses-lite/{sense_id}
Retrieve a single sense by its unique sense ID. The response includes the entry headword and the sense data with a list of available translation languages.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| sense_id | string | Yes | The unique sense ID (in the URL path). |
| target_language | string | No | Include translations for this single target language (e.g. fr). |
When a sense is found within a compositional phrase, the response also includes a `compositional_phrase` field with the phrase text.
GET /search-by-definitions
Performs a free-text search in definitions, enabling contextually relevant results.
Supported languages are: ar, br, cs, da, de, el, en, es, fr, he, hi, it, ja, ko, nl, no, pl, pt, ru, sv, th, tr.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| text | string | Yes | The text to search for in definitions. |
| lang | string | No | Filter results to entries in the specified language. The search text itself can be in any language. |
Examples
- Searching for “green fruit” can return results like “apple” (one of its definitions is “a round green or red fruit”) and “avocado” (one of its definitions is “an oval dark green fruit with a large stone”).
- Searching for “thing to sleep on” can return results like “pillow” (one of its definitions is “a soft object that you put your head on when you sleep”) and “bed” (one of its definitions is “a piece of furniture for sleeping”).
The results are returned as objects within the results array, and contain the following fields:
- the unique entry ID
- the source language code
- the headword text
- the part of speech
- the unique sense ID
- the sense definition
GET /fluky-search
Returns a randomly selected entry from the available resources. This is useful for discovering words at random across supported languages.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| source | string | No | Which resource to look in: global (default), password, multigloss, random. |
| language | string | No | Source language code (e.g. ar, br, de, en, es, ja, …). If not specified, the language is chosen randomly. |
GET /nearby-words
Returns words semantically related to a given lemma. Each result includes a relatedness score in [0, 1] — useful for thesaurus-like discovery, vocabulary expansion, and “see also” features.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| text | string | Yes | The source lemma. |
| language | string | Yes | Source language code. |
| pos | string | No | Part of speech filter for the source entry. |
| min-score | integer | No | Drop candidates whose internal combined score is below this threshold. |
| page | integer | No | Page number (default: 1). |
| page-length | integer | No | Results per page (default: 10). |
Each result contains:
– `lemma` — the candidate lemma
– `pos` — its part of speech
– `language` — the language code
– `relatedness` — a `[0, 1]` similarity score
RDF Endpoints
The following endpoints return data in RDF (JSON-LD) format instead of standard JSON. Only the Global series data are available for these endpoints.
GET /search-rdf
Similar to /search, but accepts fewer parameters and returns results in RDF (JSON-LD) form.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| language | string | No | Source language code. |
| text | string | Yes | The headword to search for. |
| morph | boolean | No | Query inflected forms (default: false). |
| analyzed | boolean | No | Apply stemmer algorithm (default: false). |
| page-length | integer | No | Results per page (default: 10). |
Example: This query returns all the entries that have “dog” as their headword, in RDF form. *
GET /rdf
Identical to /entries, but returns results in RDF (JSON-LD) form.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| entry_id | string | Yes | The unique entry ID (in the URL path). |
Example: This query returns the complete entry “great” in the English resource of the Global series, in RDF form. *
Feature Endpoints
Feature endpoints provide granular access to specific lexical data for a given word. They share a common set of parameters, with per-endpoint variations noted below.
Common Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| text | string | Yes | The word to look up. |
| language | string | No | Source language code (e.g. en, fr, de). |
| pos | string | No | Part of speech filter. |
| morph | boolean | No | Query inflected forms (default: false). |
| analyzed | boolean | No | Use language-specific analyzer for broader matching (default: false). |
| page | integer | No | Page number (default: 1). |
| page-length | integer | No | Results per page (default: 10). |
The source parameter is not part of the common set — only a few feature endpoints accept it, and the allowed values differ per endpoint. See each endpoint’s notes below.
GET /definitions
Returns human-readable definitions for each sense of a word.
Accepts the common parameters above, plus:
* source (string, optional) — Resource to query: global (default), password, random. Default: global.
GET /synonyms
Returns alternative words mapped to specific senses. Accepts the common parameters above.
GET /antonyms
Returns opposite words mapped to specific senses. Accepts the common parameters above.
GET /examples
Returns curated real-world sentences demonstrating how the word is used in context. Includes a list of available translation languages for each example.
Accepts the common parameters above, plus:
* source (string, optional) — Resource to query: global (default), password. Default: global.
GET /phrases
Returns a list of idioms, collocations, and common expressions. Includes a list of available translation languages for each phrase. Accepts the common parameters above.
GET /registers
Returns stylistic markers (e.g., Slang, Formal, Archaic, Technical). Accepts the common parameters above.
GET /semantic-categories
Returns subject-matter and domain tags (e.g., Law, Medicine, Sports). Accepts the common parameters above.
GET /subcategorizations
Returns grammatical subcategorization tags mapped to specific senses (e.g., countable / uncountable for nouns, transitive / intransitive for verbs). Accepts the common parameters above.
GET /frequencies
Returns ranking data and usage statistics for the term. Not all entries have frequency data — availability depends on language coverage and the source corpus. Accepts the common parameters above.
GET /pronunciations
Returns IPA transcriptions grouped by word, language, and part of speech.
Accepts the common parameters above, except: the morph and analyzed parameters are not supported by this endpoint — only exact text matching is used.
Translation Endpoints
GET /translate-to
Returns translations for a word into a specific target language.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| text | string | Yes | The word to translate. |
| language | string | Yes | Source language code (e.g. en, fr, de). |
| targetLang | string | Yes | Target language code (e.g. es, fr, de). |
| pos | string | No | Part of speech filter. |
| morph | boolean | No | Query inflected forms (default: false). |
| analyzed | boolean | No | Use language-specific analyzer (default: false). |
| source | string | No | Resource to query: global (default), password, multigloss. |
| page | integer | No | Page number (default: 1). |
| page-length | integer | No | Results per page (default: 10). |
GET /translate-example and GET /translate-phrase
* GET /translate-example returns the translation of a specific example sentence into a target language.
* GET /translate-phrase returns the translation of a specific phrase or idiom into a target language.
Both endpoints accept the same parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
| text | string | Yes | Exact text of the example sentence or phrase. |
| target_language | string | Yes | Target language code (e.g. fr, es, de). |
| language | string | No | Source language code. |
| page | integer | No | Page number (default: 1). |
| page-length | integer | No | Results per page (default: 10). |
For /translate-example, text must match an example sentence as returned by GET /examples. For /translate-phrase, text must match a phrase as returned by GET /phrases.
Utility Endpoints
GET /lemmatize
Given a word form, returns its base lemma(s). Matches against both the headword and inflected forms.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| word | string | Yes | The word form to lemmatize (e.g. ran, running). |
| pos | string | No | Part of speech filter. |
| language | string | No | Source language code. |
| source | string | No | Resource to query (default: global). |
GET /autocomplete
Returns lemma completion suggestions for a given prefix.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| text | string | Yes | The prefix to autocomplete. |
| language | string | Yes | Language code (required because the suggest field has a mandatory language context). |
| source | string | No | Resource to query (default: global). |
GET /did-you-mean
Returns fuzzy spelling suggestions for a given word.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| text | string | Yes | The word to find suggestions for. |
| language | string | No | Source language code. |
| source | string | No | Resource to query (default: global). |
GET /check-profanity
Checks if a word is flagged as profanity in a given language.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| word | string | Yes | The word to check. |
| language | string | Yes | Language code. |
Abbreviation Endpoints
Powered by the STANDS4 abbreviations service.
GET /abbreviations and GET /reverse-abbreviations
* GET /abbreviations looks up the meanings of an abbreviation or acronym (e.g. ASAP -> As Soon As Possible).
* GET /reverse-abbreviations finds abbreviations or acronyms whose definition matches a given phrase (e.g. as soon as possible -> ASAP).
Both endpoints accept the same parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
| text | string | Yes | The abbreviation/acronym (for /abbreviations) or the phrase to search definitions for (for /reverse-abbreviations). |
| category-id | string | No | Restrict to a single STANDS4 category code (e.g. MEDICAL). |
| sort-by | string | No | Sort order: p (popularity, default), a (alphabetical), c (by category). |
| min-score | number | No | Drop results whose relevance score is below this threshold. |
| page | integer | No | Page number (default: 1). |
| page-length | integer | No | Results per page (default: 10). |
For /abbreviations, text is the abbreviation or acronym to look up. For /reverse-abbreviations, text is the phrase to search definitions for.
Each result contains id, term, definition, category_name, parent_category_name, and score.
Pagination
All search and feature endpoints support pagination via the page and page-length parameters. The response includes pagination metadata alongside the results array.
Example response:
{
“n_results”: 50,
“page_number”: 1,
“results_per_page”: 10,
“n_pages”: 5,
“results”: […]
}
Response fields:
* n_results — Total number of matching results across all pages.
* page_number — The current page number.
* results_per_page — The number of results returned on this page.
* n_pages — Total number of available pages.
* results — The page of result objects.
STRUCTURE
Following is a detailed schema of the different elements constituting a complete entry JSON object, divided by type. Note that some elements can be of more than one type.
Headword Object
Strings: text, pos, subcategorization, gender, case, register, number, geographical_usage, mood, tense
Numbers: homograph_number
Arrays: tense, mood, geographical_usage, register, case, subcategorization (arrays of strings), inflections (array of objects)
Objects: alternative_scripts, pronunciation
Sense Object (within the Senses array)
Strings: id, definition, semantic _category, register, range_of_application, subcategorization, geographical_usage, semantic_subcategory, sentiment, see, see_also
Arrays: semantic_category, register, sentiment, geographical_usage, range_of_application, subcategorization, synonyms, antonyms, semantic_subcategory, see_also (arrays of strings), examples, compositional_phrases, inflections, senses (array of objects)
Objects: translations
MultiGloss senses have different fields:
Strings: id, en_headword, en_pos
Arrays: en_examples, translations.
Compositional Phrases Object (within the Compositional Phrases array)
Strings: text, definition, sentiment, register, semantic_category, semantic_subcategory, range_of_application, aspect, pos, geographical_usage
Arrays: synonyms, antonyms, senses, sentiment, register, semantic_category, semantic_subcategory, range_of_application, geographical_usage (arrays of strings), examples (array of objects)
Objects: alternative_scripts, translations
Examples Object (within the Examples array)
Strings: text
Objects: alternative_scripts, translations
Translations Object
field = language code (2 letters) – value is an object (or an array of objects for more than one translation) with the following fields:
Strings: text, range_of_application, collocate, register, semantic_category, semantic_subcategory, sentiment, gender, number, geographical_usage, pos
Arrays: range_of_application, collocate, register, semantic_category, semantic_subcategory, sentiment, geographical_usage (arrays of strings), inflections, pronunciation (array of objects)
Objects: alternative_scripts, pronunciation
Inflections Object (within the Inflections array)
Strings: text, geographical_usage, case, number, gender, register, tense, aspect, subcategorization, mood
Arrays: geographical_usage, case, register, tense, subcategorization, mood (arrays of strings), pronunciation (array of objects)
Objects: alternative_scripts, pronunciation
Pronunciation Object
fields: value (string) – the pronunciation text, geographical_usage (string/array of strings)
Alternative Scripts Object
field: the name of the alternative script with a string value containing the text
RDF STRUCTURE
The API returns the Global series data in RDF format for users who need structured, semantic representation of lexicographic entries. RDF (Resource Description Framework) allows the integration of this data into linked data systems, making it suitable for applications that require a more formal representation of language resources.
This structure is a schematic overview of the RDF elements used in lexicographic entries. For a more detailed explanation, please refer to the documentation at OntoLex-Lexicog.
LexicographicEntry Object
Strings: @id, @type (always lexicog:LexicographicResource), language (the language of the lexicographic resource)
describes Object
Strings: @id, @type (always ontolex:LexicalEntry)
Arrays: form, senses, translations
Objects: entryIn, pos
Form Object
Strings: @id, @type (always ontolex:Form), gender, number
Objects: text (dictionary with language code keys), pronunciation (dictionary with language and phonetic script keys)
Sense Object (within the senses array)
Strings: @id, @type (always ontolex:LexicalSense)
Arrays: examples, compositionalPhrases, translations, reversedRelates
Objects: lexicalizedSense, ofLexicographicComponent, homograph_entry, SenseToEntry
Example Object (within the examples array)
Strings: @id, @type (always lexicog:UsageExample)
Objects: value (dictionary with language keys for multilingual examples)
Translation Object (within the translations array)
Strings: @id, @type (always vartrans:Translation)
Objects: target, source, tranSet
Compositional Phrases Object (within compositionalPhrases)
Strings: @id, @type (always ontolex:LexicalSense)
Arrays: examples, translations
Objects: SenseToEntry, lexicalizedSense
SenseToEntry Object
String: @id, @type (always ontolex:LexicalEntry)
Objects: form, entryIn
entryIn Object
Strings: @id, @type (always lime:Lexicon), limeLanguage
nestedIn Object
Strings: @id, @type (always lexicog:LexicographicResource)
This field is used when an entry is related to another entry. It indicates that the current entry is nested within a broader context or group of entries. For example, the verb abandon might be related to the adjective abandoned. This structure helps in organizing related entries that share semantic or linguistic connections.
ofLexicographicComponent Object
Strings: @id, @type (always lexicog:LexicographicComponent)
Objects: subComponent
This field is used to represent senses that belong specifically to compositional phrases. It allows for the detailed description of a phrase’s meaning.
subComponent Object
Strings: @id, @type (always lexicog:LexicographicComponent)
Objects: describes
homograph_entry Object
Strings: @id, @type (always ontolex:LexicalEntry)
Objects: entryIn
tranSet Object
Strings: @id, @type (always vartrans:translationSet)
lexicalizedSense Object
Strings: @id, @type (always ontolex:LexicalConcept)
Objects: definition, source
reversedRelate Object
Strings: @id, @type (always vartrans:SenseRelation), category (can be lexinfo:synonym or lexinfo:antonym)
WORD FREQUENCY
Most entries in the dataset include a frequency attribute, which indicates the frequency of occurrence in some corpus. These frequency values are derived from SketchEngine.
** Below is a list of the corpora utilized by SketchEngine to calculate frequency values for our dataset
** List of the Corpora:
ar corpus name: Arabic Web 2018 (arTenTen18).
- Corpus info: number of tokens 5,341,978,851, number of words 4,637,956,234
br corpus name: Brazilian Portuguese corpus (Corpus Brasileiro).
- Corpus info: number of tokens 1,133,416,757, number of words 871,117,178
cs corpus name: Czech Web 2017 (csTenTen17).
- Corpus info: number of tokens 12,586,415,546, number of words 10,502,222,474
da corpus name: Danish Web 2020 (daTenTen20).
- Corpus info: number of tokens 4,127,362,161, number of words 3,480,275,804
de corpus name: German Web 2020 (deTenTen20).
- Corpus info: number of tokens 20,999,598,683, number of words 17,512,733,172
el corpus name: Greek Web 2019 (elTenTen19).
- Corpus info: number of tokens 2,782,299,354, number of words 2,342,091,029
en corpus name: English Web 2020 (enTenTen20).
- Corpus info: number of tokens 43,125,207,462, number of words 36,561,273,153
es corpus name: Spanish Web 2018 (esTenTen18).
- Corpus info: number of tokens 19,593,089,777, number of words 16,953,735,742
fr corpus name: French Web 2020 (frTenTen20).
- Corpus info: number of tokens 17,805,103,451, number of words 15,115,914,647
he corpus name: Hebrew Web 2021 (heTenTen21).
- Corpus info: number of tokens 3,183,067,122, number of words 2,775,686,699
hi corpus name: Hindi Web 2017 (hiTenTen17).
- Corpus info: number of tokens 1,375,847,600, number of words 1,228,379,747
it corpus name: Italian Web 2020 (itTenTen20).
- Corpus info: number of tokens 14,514,566,714, number of words 12,451,734,885
ja corpus name: Japanese Web 2011 (jaTenTen11).
- Corpus info: number of tokens 10,321,875,664, number of words 8,432,294,787
ko corpus name: Korean Web 2018 (koTenTen18).
- Corpus info: number of tokens 2,054,520,141, number of words 1,668,851,720
nl corpus name: Dutch Web 2020 (nlTenTen20).
- Corpus info: number of tokens 6,836,979,371, number of words 5,890,009,964
no corpus name: Norwegian Web 2017 (noTenTen17, Bokmål).
- Corpus info: number of tokens 2,787,260,248, number of words 2,461,704,417
pl corpus name: Polish Web 2012 (plTenTen12, RFTagger).
- Corpus info: number of tokens 9,387,142,186, number of words 7,715,835,214
pt corpus name: Portuguese Web 2018 (ptTenTen18).
- Corpus info: number of tokens 8,731,838,327, number of words 7,407,393,731
ru corpus name: Russian Web 2011 (ruTenTen11).
- Corpus info: number of tokens 18,280,486,876, number of words 14,553,856,113
sv corpus name: Swedish Web 2014 (svTenTen14).
- Corpus info: number of tokens 3,889,895,434, number of words 3,401,035,817
th corpus name: Thai Web 2018 (thTenTen18).
- Corpus info: number of tokens 695,928,167, number of words 640,530,227
tr corpus name: Turkish Web 2012 (trTenTen12).
- Corpus info: number of tokens 4,124,133,118, number of words 3,388,418,900
tw corpus name: Chinese Web 2017 (zhTenTen17).
- Traditional corpus info: number of tokens 2,977,351,219, number of words 2,400,405,372
zh corpus name: Chinese Web 2017 (zhTenTen17).
- Simplified corpus info: number of tokens 16,593,146,196, number of words 13,531,331,169
* in order to use the links above, use your X-RapidAPI-Key.
Lexicala API FAQ
We provide data for 50 languages, including the major world languages as well as minor ones. The full language list is available on the documentation page.
We provide data for 50 languages, including the major world languages and some minor ones, e.g., English, Spanish, Chinese, Arabic, German, French, Japanese, Korean, Turkish, Dutch, Russian, etc. The full language list is available on the documentation page.
Our data include extensive semantic, syntactic and grammar information about words and multiword expressions, including pronunciation, alternative scripts, inflected forms, sense disambiguation, definitions, examples of usage, domain and register classification, diverse semantic label s such as synonyms and antonyms, as well as translation equivalents, and more.
Please check the full details in the documentation.
You can test Lexicala API with up to 50 free calls per day. For requirements beyond our Basic Plan, we provide Custom Solutions and High-Volume Access. We offer tailored packages and volume-based pricing designed for your specific needs. Contact our team at api@lexicala.com to find the ideal solution for your application.
Once you have signed up for a Lexicala API account through RapidAPI system, you can start making calls. You should integrate the API into your code, which is done separately from the Lexicala API website. You can also view the requests in your browser by entering your query into the address bar.
Please refer to the guidelines on how to start making calls to the Lexicala API in the documentation.
The data you obtain from Lexicala API may not be stored locally (cached) for any purpose. However, if it is required for your specific needs (such as in offline cases), you are welcome to contact us directly to discuss. Together, we can better understand your needs and devise solutions how to cater to them. In most cases, you would be able to purchase the data in the form of XML or JSON (or JSON-LD) files for direct integration into your system without our server calls. This option may prove to be more efficient and, sometimes, also more economical.
