Weblate memory API
Added in version 4.14.
Weblate memory API is one of 21 APIs that Weblate publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include memory. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 4 operations across 3 paths, and defines 34 schemas. It is described by OpenAPI 3.1.1.
Requests are made against a single base URL, http:.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Weblate memory API declares
3 security schemes
for authenticating requests.
An API key is passed in the header as Bearer (bearerAuth).
An API key is passed in the cookie as sessionid (cookieAuth).
An API key is passed in the header as Token (tokenAuth).
bearerAuth— Token-based authentication with required prefix Bearer. - Each user has a personal access token which they can get from their respective user profile. These to…cookieAuth— Session-based authentication used when user is signed in.tokenAuth— Token-based authentication with required prefix Token. - Each user has a personal access token which they can get from their respective user profile. These tok…
Paths & Operations 4
Across 3 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Added in version 4.14.
Schemas 34
The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are Memory (9 properties), MemoryLookupMatch (6 properties), PaginatedMemoryList (4 properties), Error404 (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Weblate 12
Other APIs Weblate publishes across the network.