How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

LINDAT MorphoDiTa API

Public keyless REST API for morphological analysis, morphological generation, part-of-speech tagging and tokenization, principally for Czech, operated by UFAL at Charles University. The OpenAPI here is derived by API Evangelist from the service's published REST API reference and verified against live responses.

LINDAT MorphoDiTa API is one of 17 APIs that Charles University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Natural Language Processing, Morphology, and Research. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 5 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://lindat.mff.cuni.cz/services/morphodita/api.

5 operations 5 paths 2 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://lindat.mff.cuni.cz/services/morphodita/api
Terms of Service
Resource Areas
1

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 5 GET. Each is listed below with its method, path, parameters, and response codes.

morphodita 5

Morphological analysis, generation, tagging and tokenization operations

GET
/models
List available MorphoDiTa models
listMorphoDiTaModels → 200
GET
/tag
Part-of-speech tag and lemmatize the supplied text
tagText 7 params → 200
GET
/analyze
Perform morphological analysis of the supplied text
analyzeText 7 params → 200
GET
/generate
Perform morphological generation from supplied lemmas
generateForms 5 params → 200
GET
/tokenize
Tokenize the supplied text
tokenizeTextMorphoDiTa 3 params → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are ServiceResponse (3 properties), ModelList (2 properties). Each schema is shown below with its type and property counts.

ModelList
object
2 properties 2 required
ServiceResponse
object
Common LINDAT web-service response envelope.
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

charles-morphodita-api-openapi.yml Raw ↑

Other APIs Charles University publishes across the network.

LINDAT Translation Languages API
LINDAT Translation Models API
LINDAT Translation Root API
LINDAT UDPipe API
LINDAT NameTag API
LINDAT Korektor API
CU Digital Repository OAI-PMH
CU Research Publications Repository OAI-PMH
LINDAT/CLARIAH-CZ Repository OAI-PMH
LINDAT/CLARIAH-CZ Repository REST API
Charles University Shibboleth Identity Provider
DataCite Registrant — Charles University (CUNI)
Where this information came from

This is an independent, third-party profile of LINDAT MorphoDiTa API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.