Heinzelnisse supports a REST-API which can be used free of charge. Usage terms are covered under: GPL-v2
. The API is used internally in the App
and therefore considered stable. To be informed about usage changes, e.g. over-usage countermeasures (API-keys), please write an email to firstname.lastname@example.org .
The Heinzelnisse REST-API can be called under https://heinzelnisse.info/searchResults?
The API support the following options:
searchItem=* the word to search for
dictExactSearch=on| only search for the complete word
dictDeNoSearch=on| search from German (DE) to Norwegian (NO). Corresponds to the
deTrans attribute in the response.
dictNoDeSearch=on| search from Norwegian (NO) to German (DE). Corresponds to the
noTrans attribute in the response.
dictPhoneticSearch=on| find suggestions for phonetically similar words (e.g. fandom=phantom), or conjugated/declinated words (e.g vergas=vergessen). Corresponds to the
noPhonetics attribute in the response.
wikiSearch=on| find results from the wiki. Corresponds to the
wikiPageNames attribute in the response.
forumKeywordSearch=on| find results in the forum. Corresponds to the
forumQuestions attribute in the response.
dictNynorskSearch=on| find similar words in the nynorsk dictionary
dictBokmaalSearch=checked| find similar words in the bokmål dictionary
type=json return json (only option)
setOption=on| use these options (or use defaults)
The response of a typical query like API-Link
The most important attributes are
with lists of the following objects:
This describes (among others) the
in the original language
and additional information
and the translation
A fast and typical query to find the translations from a german text, e.g. to find the word
The list of words
are in particularly useful, when the given word can not be found, or does not give the desired results. In these cases, the desired word in the
list should be used as searchItem. Example:
will not give any
"dePhonetics": [ "Vergaser", "vergessen" ],
which should lead to the query in the first example.