JSON API
Read-only machine access to the released terminology under /api/v1.
A read-only JSON API is available for integration into other systems. It serves released entries only — the same ones the website shows. There are no write operations.
Endpoints
| Endpoint | Returns |
|---|---|
GET /api/v1/search?q=&source=&target=&mode= |
Search, paginated. mode is normal, fuzzy or fulltext. |
GET /api/v1/entries/{id} |
One concept in full: all languages, synonyms, attributes. |
GET /api/v1/suggest?q= |
Type-ahead suggestions for an input field. |
GET /api/v1/languages |
The available languages with their codes. |
GET /api/v1/openapi.yaml |
The full interface description (OpenAPI 3). |
Responses follow the usual data / meta / links shape; lists are paginated.
Addressed by ID
Unlike the website, the API addresses a concept by its numeric ID, not by its readable address. The ID never changes — the API is a contract for machines, not a readable address.
A concept that is not released answers 404, not an empty record: the API does not reveal whether an unpublished entry exists.
Usage limits
The API is rate-limited (60 requests per minute and IP address by default). The
remaining allowance is in the X-RateLimit-* headers of every response. Access
from a browser on another domain requires that domain to be allow-listed.