Weblate components API
The components API from Weblate — 17 operation(s) for components.
Weblate components API is one of 21 APIs that Weblate publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include components. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 25 operations across 17 paths, and defines 74 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 components 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 25
Across 17 paths, the API surfaces 25 operations — 3 DELETE, 14 GET, 1 PATCH, 6 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Schemas 74
The contract defines 74 schemas that model the data the API accepts and returns. The most detailed are PatchedComponent (93 properties), Component (93 properties), Project (61 properties), Statistics (37 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.