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 Translation Languages API

Source and target language operations of the LINDAT Machine Translation API, operated by the Institute of Formal and Applied Linguistics (UFAL) at Charles University. Translation is performed by posting text to a language pair. Refined by API Evangelist from the upstream Swagger 2.0 specification published by the service itself.

LINDAT Translation Languages 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 Language and Machine Translation. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

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

3 operations 2 paths 6 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://lindat.mff.cuni.cz/services/translation/api/v2
Resource Areas
1

Paths & Operations 3

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

languages 3

Operations with source and target languages

GET
/languages/
Returns a list of available languages
get_language_collection → 200
POST
/languages/
Translate input from src lang to tgt lang
post_language_collection 2 params body → 200415
GET
/languages/{language}
Returns a language resource object
get_language_item 1 param → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Link (8 properties), LanguageResourceLinks (4 properties), LanguageLinks (3 properties), LanguageResource (3 properties). Each schema is shown below with its type and property counts.

LanguageResourceLinks
object
4 properties
LanguageResource
object
3 properties
LanguageLinks
object
3 properties
Link
object
8 properties
EmbeddedLanguages
object
1 property
LanguagesResource
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

charles-languages-api-openapi.yml Raw ↑

Other APIs Charles University publishes across the network.

LINDAT Translation Models API
LINDAT Translation Root API
LINDAT UDPipe API
LINDAT NameTag API
LINDAT MorphoDiTa 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 Translation Languages 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.