id when you assign a role.
The call is authorized by the workspace API key’s USER_MANAGEMENT_API scope. It does not run as the person who created the key, so it keeps working after that admin leaves the workspace.
Base URL
Prerequisites
- API Key with the
USER_MANAGEMENT_APIscope - The API key must be created by a workspace admin
Behavior
- System roles come first, in this order:
member,editor,admin.kindissystem.nameis Member, Editor, or Admin.descriptionis empty.idis that lowercase role name. - Custom roles follow, oldest first.
kindiscustom. Deleted custom roles are left out. - Each role has
id,kind,name, anddescription. Permission settings are not included. - The call takes no query parameters.
Langdock intentionally blocks browser-origin requests to protect your API key and ensure your applications remain secure. For more information, please see our guide on API Key Best Practices.