Skip to main content
PATCH
Update several Users

Introduction

This endpoint updates several users in one call, for example to move people to a new department or manager, or to sync a field from your HRIS. Use it instead of one Update a User call per user. Please note that:
  1. You can update up to 100 users per call. To update more, split them into several calls.
  2. Each item identifies a user by its uid and accepts the same attributes as Update a User. Only the attributes you pass are changed.
  3. Each user can appear only once per call.
  4. Each user is updated on its own: if one user fails (for example because of an invalid value), the others are still updated. The response tells you, for each user, whether it was updated or why it failed, so you can retry only the failed ones.
  5. The whole call is rejected, with no user updated, when the payload is invalid (no items, more than 100 items, an item without uid, a uid listed twice), when a uid does not match any user of your company, or when your role cannot manage users.
  6. Fields that are disabled or that your role cannot edit are ignored, as with a single update.
  7. The response does not contain the updated users. Retrieve a User to read their new values.

Example payload

Example response

Usage

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
items
object[]
required

The Users to update, each identified by its UID and carrying the same attributes as the single User update.

Required array length: 1 - 100 elements

Response

Successful: each item reports whether its User was updated

results
object[]

The outcome of each item, in the order they were sent. Entries are outcomes, not Users: fetch a User to read its updated attributes.