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: 15.07.2022). Routes that are in development are available to try but not yet thoroughly tested and subject to changes, while those in design can be browsed for (provisional) specifications but are not yet implemented. The routes that are not read-only have restricted access.

Route	Status	Read-only	Description
/search/form/	in development	yes	search for word forms by string
/retrieve/lexeme/:lexeme_id/	in development	yes	get a lexeme's data from its idno
/search/lexeme/	in design	yes	search for a lexeme
/search-batch/search/lexical-unit/	in design	yes	batch search for lexical units
/retrieve/lexical-unit-forms-status/lexemes/	in design	yes	get the forms of a lexical unit's parts,component with statuseslexemes
/process/string-to-tokens/	in designdevelopment	yes	parse a Slovene string to get a list of tokens
/create/lexeme/	in development	no	get or create a lexeme based on defining properties
/create-batch/create/lexical-unit/	in design	no	batch get or create lexical units
/detach/lexical-unit/	in development	no	detach a lexical unit from a resource