Creates a new user, either End-User or Service User.
End-User Accounts are assigned to employees. To create an end user account, the accountType field must be NORMAL.
Service User Accounts are a type of account used for bots or applications, rather than end-users. To create a service user account, the accountType field must be SYSTEM.
Client error, see response body for further details.
application/json
401
Unauthorized: Invalid session token.
application/json
403
Forbidden: Caller lacks necessary entitlement.
application/json
500
Server error, see response body for further details.
application/json
post
/v2/admin/user/create
Request Examples
📘 Note - Suspension
Since 20.14, userSystemInfo from the payload includes suspension info:
if user is active, then the suspended attribute is set to false,
if user is suspended, then the suspended attribute is set to true and both suspendedUntil and suspensionReason are as well included in the payload.
Please note that even if the suspendedUntil date is in the past, the user will remain suspended=true until he first logs on the client after the suspension ended. The suspended info are then automatically updated.
See the Suspend User Account endpoint for more information.
🚧 Required Permissions
Calling this endpoint requires the ACCESS_USER_PROVISIONING_API and ACCESS_ADMIN_API privileges.
See Bot Permissions for a list of roles and associated privileges.
The Password Object
The password object is optional for end-user accounts (NORMAL). For example, if your organization utilizes SSO, you may not want to specify the password.
Please note the password object is not used for service accounts (SYSTEM) and therefore cannot be entered in the request payload.
The following code snippets can be used to generate hashed passwords. Two implementations are provided, one using built-in Java classes and the other with Postman.