API routes
The API is being designed and developed, with priority on current needs. Specifications are available in redoc (which is better formatted visually) and swagger (which allows you to try the API via the interface).
Here is a list of the current routes (last update: 14.10.2022). All routes are available with POST, while some of them also have GET or batch POST alternatives (ref). The routes that are not read-only have restricted access.
| Route | Read-only | Description |
|---|---|---|
| /search/lexical-unit/ | yes | search for lexical units |
| /retrieve/lexical-unit-lexemes/ | yes | get the lexical unit's component lexemes |
| /get-or-create/lexical-unit/ | no | get or create a lexical unit based on properties and components |
| /search/lexeme/ | yes | search for lexemes |
| /retrieve/lexeme/ | yes | get a lexeme |
| /get-or-create/lexeme/ | no | get or create a lexeme based on defining properties |
| /search/form/ | yes | search for word forms by string |
| /get-or-create/resource/ | no | get or create a dictionary or other resource |
| /search/resource/ | yes | search or list resources available |
| /attach/lexical-unit/ | no | attach a lexical unit to a resource |
| /detach/lexical-unit/ | no | detach a lexical unit from a resource |
| /process/string-to-tokens/ | yes | parse a Slovene string to get a list of tokens |