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

Label Studio subpackage_users API

The subpackage_users API from Label Studio — 7 operation(s) for subpackage_users.

Label Studio subpackage_users API is one of 74 APIs that Label Studio publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 12 operations across 7 paths, and defines 13 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

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

12 operations 7 paths 13 schemas 1 DELETE6 GET3 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://app.humansignal.com/api
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Label Studio subpackage_users API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Token).

  • Token — The token (or API key) must be passed as a request header. You can find your user token on the User Account page in Label Studio. Example: curl https://label-s…

Paths & Operations 12

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

subpackage_users 12
GET
/api/current-user
✨ Get current user info
get-current-user 1 param → 200
PATCH
/api/current-user
✨ Update current user
update-current-user 1 param body → 200
GET
/api/current-user/hotkeys/
Get user hotkeys
get-hotkeys 1 param → 200
PATCH
/api/current-user/hotkeys/
Update user hotkeys
update-hotkeys 1 param body → 200
POST
/api/current-user/reset-token/
Reset user token
reset-token 1 param → 201
GET
/api/current-user/token
Get user token
get-token 1 param → 200
GET
/api/current-user/whoami
Retrieve my user
whoami 1 param → 200
GET
/api/users/
List users
list 2 params → 200
POST
/api/users/
Create new user
create 1 param body → 201
GET
/api/users/{id}/
Get user info
get 2 params → 200
DELETE
/api/users/{id}/
Delete user
delete 2 params → 200
PATCH
/api/users/{id}/
Update user details
update 2 params body → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are WhoAmIUser (20 properties), LseUser (18 properties), LseUserAPI (16 properties), WhoAmILseFields (14 properties). Each schema is shown below with its type and property counts.

TrialRoleEnum
string
annotator - Annotator annotatorteammanager - Annotator Team Manager businessanalyst - Business Analyst businessordatateamleadership - Business Or Data Team Lea…
OnboardingStateEnum
string
notstarted - Not Started signup - Signup trialsignup - Trial Signup firsttutorial - First Tutorial inappguidance - In App Guidance complete - Complete
users_reset_token_Response_201
object
1 property
PatchedHotkeysRequest
object
1 property
LseUser
object
A ModelSerializer that takes additional arguments for "fields", "omit" and "expand" in order to control which fields are displayed, and whether to replace simp…
18 properties 10 required
OrganizationMembership
object
3 properties 3 required
WhoAmILseFields
object
14 properties 4 required
LseUserAPI
object
A ModelSerializer that takes additional arguments for "fields", "omit" and "expand" in order to control which fields are displayed, and whether to replace simp…
16 properties 8 required
LseFields
object
13 properties 3 required
Hotkeys
object
1 property 1 required
users_get_token_Response_200
object
1 property
PatchedLseUserSerializerUpdateRequest
object
A ModelSerializer that takes additional arguments for "fields", "omit" and "expand" in order to control which fields are displayed, and whether to replace simp…
12 properties
WhoAmIUser
object
A ModelSerializer that takes additional arguments for "fields", "omit" and "expand" in order to control which fields are displayed, and whether to replace simp…
20 properties 12 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

label-studio-subpackage-users-api-openapi.yml Raw ↑

Other APIs Label Studio publishes across the network.

Label Studio subpackage_actions API
Label Studio subpackage_activityLogs API
Label Studio subpackage_annotationHistory API
Label Studio subpackage_annotationReviews API
Label Studio subpackage_annotations API
Label Studio subpackage_billing API
Label Studio subpackage_comments API
Label Studio subpackage_dimensions API
Label Studio subpackage_exportStorage API
Label Studio subpackage_exportStorage.subpackage_exportStorage/azure API
Label Studio subpackage_exportStorage.subpackage_exportStorage/azureSpi API
Label Studio subpackage_exportStorage.subpackage_exportStorage/databricks API
Where this information came from

This is an independent, third-party profile of Label Studio subpackage_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.