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

Weblate users API

Added in version 4.0.

Weblate users API is one of 22 APIs that Weblate publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 16 operations across 7 paths, and defines 61 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, http:.

16 operations 7 paths 61 schemas 3 DELETE6 GET2 PATCH3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://hosted.weblate.org/api/
Authentication
API Key, API Key, API Key
Resource Areas
1

Authentication & Security 3

Weblate users 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 16

Across 7 paths, the API surfaces 16 operations — 3 DELETE, 6 GET, 2 PATCH, 3 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

users 16

Added in version 4.0.

GET
/api/users/
List of users if you have permissions to see manage users. Without a permission you get to see only your own details.
api_users_list 5 params → 400401403404405406423429
POST
/api/users/
Create a new user.
api_users_create body → 400401403404405406415423
GET
/api/users/{username}/
Return information about users.
api_users_retrieve 1 param → 400401403404405406423429
PUT
/api/users/{username}/
Change the user parameters.
api_users_update 1 param body → 400401403404405406415423
PATCH
/api/users/{username}/
Change the user parameters.
api_users_partial_update 1 param body → 400401403404405406415423
DELETE
/api/users/{username}/
Delete all user information and mark the user inactive.
api_users_destroy 1 param → 400401403404405406423429
GET
/api/users/{username}/contributions/
List translation contributions of a user.
api_users_contributions_list 6 params → 400401403404405406423429
POST
/api/users/{username}/groups/
Associate groups with a user.
api_users_groups_create 1 param body → 400401403404405406415423
DELETE
/api/users/{username}/groups/
Remove a user from a group.
api_users_groups_destroy 1 param body → 400401403404405406415423
GET
/api/users/{username}/notifications/
List subscriptions of a user.
api_users_notifications_list 6 params → 400401403404405406423429
POST
/api/users/{username}/notifications/
Associate subscriptions with a user.
api_users_notifications_create 6 params body → 400401403404405406415423
GET
/api/users/{username}/notifications/{subscription_id}/
Get a subscription associated with a user.
api_users_notifications_retrieve 2 params → 400401403404405406423429
PUT
/api/users/{username}/notifications/{subscription_id}/
Edit a subscription associated with a user.
api_users_notifications_update 2 params body → 400401403404405406415423
PATCH
/api/users/{username}/notifications/{subscription_id}/
Edit a subscription associated with a user.
api_users_notifications_partial_update 2 params body → 400401403404405406415423
DELETE
/api/users/{username}/notifications/{subscription_id}/
Delete a subscription associated with a user.
api_users_notifications_destroy 2 params → 400401403404405406423429
GET
/api/users/{username}/statistics/
List statistics of a user.
api_users_statistics_retrieve 1 param → 400401403404405406423429

Schemas 61

The contract defines 61 schemas that model the data the API accepts and returns. The most detailed are Component (93 properties), Project (61 properties), Translation (33 properties), PatchedFullUser (16 properties). Each schema is shown below with its type and property counts.

CommitPolicyEnum
integer
0 - Commit all translations regardless of quality 20 - Skip translations marked as needing editing 30 - Only include approved translations
Error406
object
3 properties 3 required
Error400
object
3 properties 3 required
LanguagePlural
object
5 properties 2 required
ErrorResponse400TypeEnum
string
validationerror - Validation Error clienterror - Client Error
MergeStyleEnum
string
merge - Merge rebase - Rebase mergenoff - Merge without fast-forward
NewLangEnum
string
contact - Contact maintainers url - Point to translation instructions URL add - Create new language file none - Disable adding new translations
Error415
object
3 properties 3 required
Error423
object
3 properties 3 required
ErrorCode500Enum
string
error - Error
ErrorResponse423
object
2 properties 2 required
PriorityEnum
integer
60 - Very high 80 - High 100 - Medium 120 - Low 140 - Very low
SourceEnum
integer
0 - Default plural 1 - gettext plural formula 3 - CLDR plural with zero 4 - CLDR v38+ plural 5 - Android plural 6 - Qt Linguist plural 2 - Manually entered for…
UserGroupRequest
object
2 properties 1 required
ErrorResponse429
object
2 properties 2 required
UserGroupDeleteRequest
object
1 property 1 required
ErrorResponse415
object
2 properties 2 required
ServerErrorEnum
string
servererror - Server Error
LanguageCodeStyleEnum
string
- Default based on the file format posix - POSIX style using underscore as a separator posixlowercase - POSIX style using underscore as a separator, lower case…
BlankEnum
PatchedFullUser
object
16 properties
PaginatedFullUserList
object
4 properties 2 required
Project
object
61 properties 30 required
ClientErrorEnum
string
clienterror - Client Error
UserStatistics
object
5 properties 5 required
ErrorResponse400
object
2 properties 2 required
VcsEnum
string
gerrit - Gerrit git - Git git-force-push - Git with force push local - No remote repository mercurial - Mercurial subversion - Subversion
ErrorResponse405
object
2 properties 2 required
FullUser
object
16 properties 11 required
NotificationEnum
string
RepositoryNotification - Operation was performed in the repository LockNotification - Component was locked or unlocked LicenseNotification - License was change…
PatchedNotification
object
6 properties
PaginatedTranslationList
object
4 properties 2 required
Error500
object
3 properties 3 required
ErrorCode406Enum
string
notacceptable - Not Acceptable
FileFormatEnum
string
apple-xliff - XLIFF 1.2 with Apple extensions appstore - App store metadata files arb - ARB file aresource - Android String Resource asciidoc - AsciiDoc file a…
Error404
object
3 properties 3 required
Notification
object
6 properties 6 required
Error405
object
3 properties 3 required
PaginatedNotificationList
object
4 properties 2 required
ErrorCode403Enum
string
permissiondenied - Permission Denied
Error401
object
3 properties 3 required
ErrorCode405Enum
string
methodnotallowed - Method Not Allowed
FrequencyEnum
integer
0 - No notification 1 - Instant notification 2 - Daily digest 3 - Weekly digest 4 - Monthly digest
ErrorResponse401
object
2 properties 2 required
ErrorCode415Enum
string
unsupportedmediatype - Unsupported Media Type
ErrorCode401Enum
string
authenticationfailed - Authentication Failed notauthenticated - Not Authenticated
DirectionEnum
string
- Automatically detect text direction ltr - Left to right rtl - Right to left
ColorEnum
string
navy - Navy blue - Blue aqua - Aqua teal - Teal olive - Olive green - Green lime - Lime yellow - Yellow orange - Orange red - Red maroon - Maroon fuchsia - Fuc…
Error429
object
3 properties 3 required
Error403
object
3 properties 3 required
ErrorCode429Enum
string
throttled - Throttled
ErrorResponse404
object
2 properties 2 required
Language
object
10 properties 6 required
ErrorCode423Enum
string
repository-locked - Repository Locked component-locked - Component Locked unknown-locked - Unknown Locked
ErrorResponse500
object
2 properties 2 required
ErrorResponse406
object
2 properties 2 required
Translation
object
33 properties 31 required
NotificationScopeEnum
integer
0 - All 10 - Watched 20 - Administered 30 - Project 40 - Component
Component
object
93 properties 34 required
ErrorResponse403
object
2 properties 2 required
ErrorCode404Enum
string
notfound - Not Found

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

weblate-users-api-openapi.yml Raw ↑

Other APIs Weblate publishes across the network.

Weblate addons API
Weblate categories API
Weblate changes API
Weblate component-lists API
Weblate components API
Weblate contributions API
Weblate groups API
Weblate hooks API
Weblate languages API
Weblate memory API
Weblate metrics API
Weblate projects API
Where this information came from

This is an independent, third-party profile of Weblate users 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.