Metabolon Users API
The Users API from Metabolon — 90 operation(s) for users.
Operations 90
GET
/api/v1/users/current/learning-center-links
Returns Learning Center launch links authorized for the current user from Portal DB permissions and backend branch config.
#
POST
/api/v1/users/current/eula-acceptance
Accepts the End User License Agreement for the current user
#
GET
/api/v2/users/current/learning-center-links
Returns Learning Center launch links authorized for the current user from Portal DB permissions and backend branch config.
#
POST
/api/v2/users/current/eula-acceptance
Accepts the End User License Agreement for the current user
#
GET
/api/v1/admin/users
Retrieves all users which details contains this string in an email, firstname or lastname
#
POST
/api/v1/admin/users/user/upsert
Adds or updates a user without assigning a project. When updating an existing user (e.g. when email is changed), set OriginalEmail to the user's current email so the backend can fi
#
GET
/api/v1/admin/users/search/{text}
Retrieves all users which details contains this string in an email, firstname or lastname
#
GET
/api/v1/admin/users/projects/search/{text}
Retrieves all projects which details contains this string
#
GET
/api/v1/admin/users/roles/search/{text}
Retrieves all roles which details contains this string
#
GET
/api/v1/admin/users/roles/permissions/catalog
Returns the default permission catalog used to validate role permission changes.
#
GET
/api/v1/admin/users/roles/definitions/default
Returns role names defined in the default role definitions.
#
POST
/api/v1/admin/users/roles/reset
Restores all database roles to the default role definitions, removing roles not in the defaults and their user assignments.
#
GET
/api/v1/admin/users/roles/{roleName}/permissions
Returns permissions currently assigned to a role in the database.
#
POST
/api/v1/admin/users/roles/{roleName}/permissions/reset
Restores a single role's permissions to the default role definitions.
#
POST
/api/v1/admin/users/roles/{roleName}/permissions/add
Adds a permission to a role from the default permission catalog.
#
GET
/api/v1/admin/users/salesforce/{email}
Returns resolved Salesforce login status for Access Management (Employee, Legacy, Contact, etc.).
#
GET
/api/v1/admin/users/talent-lms/{email}
Returns Learning Center branch access and TalentLMS sync status for a Portal user.
#
GET
/api/v1/admin/users/talent-lms/queue
Returns how many Portal users are currently due for TalentLMS reconciliation.
#
GET
/api/v1/admin/users/talent-lms/failures
Returns Portal users whose latest TalentLMS sync is in a failed state.
#
POST
/api/v1/admin/users/talent-lms/sync
Queues eligible Portal users and reconciles all due TalentLMS users.
#
POST
/api/v1/admin/users/talent-lms/{email}/reconcile
Manually reconciles a Portal user's TalentLMS branch membership from Portal permissions.
#
GET
/api/v1/admin/users/registration-eligibility/{email}
Checks whether a new non-employee user may be added for the given email (same rules as upsert auto-approval).
#
GET
/api/v1/admin/users/salesforce/pending
Lists users in the Portal waiting room for Salesforce approval.
#
GET
/api/v1/admin/users/salesforce/pending/search/{text}
Searches users in the Portal waiting room for Salesforce approval.
#
GET
/api/v1/admin/users/salesforce/pending/count
Returns how many users are currently in the Salesforce approval waiting room.
#
POST
/api/v1/admin/users/salesforce/pending/sync
Discovers pending Salesforce leads and reconciles the waiting room (including approval emails).
#
POST
/api/v1/admin/users/salesforce/{email}/approve
Marks the user as Salesforce-approved using Leads only. A Contact is treated as already approved (no change); an existing Lead has its Portal Access Status set to Approved; if no S
#
GET
/api/v2/admin/users
Retrieves all users which details contains this string in an email, firstname or lastname
#
POST
/api/v2/admin/users/user/upsert
Adds or updates a user without assigning a project. When updating an existing user (e.g. when email is changed), set OriginalEmail to the user's current email so the backend can fi
#
GET
/api/v2/admin/users/search/{text}
Retrieves all users which details contains this string in an email, firstname or lastname
#
GET
/api/v2/admin/users/projects/search/{text}
Retrieves all projects which details contains this string
#
GET
/api/v2/admin/users/roles/search/{text}
Retrieves all roles which details contains this string
#
GET
/api/v2/admin/users/roles/permissions/catalog
Returns the default permission catalog used to validate role permission changes.
#
GET
/api/v2/admin/users/roles/definitions/default
Returns role names defined in the default role definitions.
#
POST
/api/v2/admin/users/roles/reset
Restores all database roles to the default role definitions, removing roles not in the defaults and their user assignments.
#
GET
/api/v2/admin/users/roles/{roleName}/permissions
Returns permissions currently assigned to a role in the database.
#
POST
/api/v2/admin/users/roles/{roleName}/permissions/reset
Restores a single role's permissions to the default role definitions.
#
POST
/api/v2/admin/users/roles/{roleName}/permissions/add
Adds a permission to a role from the default permission catalog.
#
GET
/api/v2/admin/users/salesforce/{email}
Returns resolved Salesforce login status for Access Management (Employee, Legacy, Contact, etc.).
#
GET
/api/v2/admin/users/talent-lms/{email}
Returns Learning Center branch access and TalentLMS sync status for a Portal user.
#
GET
/api/v2/admin/users/talent-lms/queue
Returns how many Portal users are currently due for TalentLMS reconciliation.
#
GET
/api/v2/admin/users/talent-lms/failures
Returns Portal users whose latest TalentLMS sync is in a failed state.
#
POST
/api/v2/admin/users/talent-lms/sync
Queues eligible Portal users and reconciles all due TalentLMS users.
#
POST
/api/v2/admin/users/talent-lms/{email}/reconcile
Manually reconciles a Portal user's TalentLMS branch membership from Portal permissions.
#
GET
/api/v2/admin/users/registration-eligibility/{email}
Checks whether a new non-employee user may be added for the given email (same rules as upsert auto-approval).
#
GET
/api/v2/admin/users/salesforce/pending
Lists users in the Portal waiting room for Salesforce approval.
#
GET
/api/v2/admin/users/salesforce/pending/search/{text}
Searches users in the Portal waiting room for Salesforce approval.
#
GET
/api/v2/admin/users/salesforce/pending/count
Returns how many users are currently in the Salesforce approval waiting room.
#
POST
/api/v2/admin/users/salesforce/pending/sync
Discovers pending Salesforce leads and reconciles the waiting room (including approval emails).
#
POST
/api/v2/admin/users/salesforce/{email}/approve
Marks the user as Salesforce-approved using Leads only. A Contact is treated as already approved (no change); an existing Lead has its Portal Access Status set to Approved; if no S
#