Create a User
Create a new user in your organization
POST
POST /v1/users
Create a User
Create a new user in your organization.Permissions
Starting in OpenMetadata 2.0.3, assigning a user to a closed team (isJoinable: false) during creation requires an administrator.
Body Parameters
POST /v1/users
Returns
Returns the created user object with all specified properties and system-generated fields.Response
Create or Update (PUT)
UsePUT /v1/users instead of POST to perform an upsert. If a user with the same fullyQualifiedName already exists, it will be updated; otherwise, a new user is created. The request body is the same as POST.
PUT will not return a 409 conflict error if the entity already exists — it will update the existing entity instead.Bulk Create or Update (PUT)
UsePUT /v1/users/bulk to create or update multiple users in a single request. The request body is an array of create request objects.
Domains
Only administrators can set a user’sdomains when creating a user with POST or PUT. Other callers, including bots, get 403. Naming no domains always works.
Allowed Email Domains
WhenallowedEmailDomains is set, creating a user whose email domain is not allowed returns 400 with a message that names the rejected domain and the allowed ones:
- Endpoints checked:
POST /api/v1/users,PUT /api/v1/usersonly when the request creates the user, and CSV import rows that create a user. - CSV import: A row outside the allowed domains is rejected, including in a dry run. The other rows still import, so the result
statusispartialSuccess. It isfailurewhen every row is rejected. - Updates: Updating an existing user is never checked, including a PUT to a user that already exists and CSV rows that update an existing user. You cannot change a user’s email address with PATCH or PUT.
- Skipped: The check does not apply to bots, to users that the server creates itself such as the bootstrap admins, or when the authentication provider is
basicoropenmetadata.