Skip to content

Users API

DETAILS: Tier: Free, Premium, Ultimate Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

You can manage your account and manage other users by using the REST API.

List users

Get a list of users.

Takes pagination parameters page and per_page to restrict the list of users.

As a regular user

GET /users

Supported attributes:

Attribute Type Required Description
username string no Get a single user with a specific username.
search string no Search for a username.
active boolean no Filters only active users. Default is false.
external boolean no Filters only external users. Default is false.
blocked boolean no Filters only blocked users. Default is false.
humans boolean no Filters only regular users that are not bot or internal users. Default is false.
created_after DateTime no Returns users created after specified time.
created_before DateTime no Returns users created before specified time.
exclude_active boolean no Filters only non active users. Default is false.
exclude_external boolean no Filters only non external users. Default is false.
exclude_humans boolean no Filters only bot or internal users. Default is false.
exclude_internal boolean no Filters only non internal users. Default is false.
without_project_bots boolean no Filters user without project bots. Default is false.

Example response:

[
  {
    "id": 1,
    "username": "john_smith",
    "name": "John Smith",
    "state": "active",
    "locked": false,
    "avatar_url": "http://localhost:3000/uploads/user/avatar/1/cd8.jpeg",
    "web_url": "http://localhost:3000/john_smith"
  },
  {
    "id": 2,
    "username": "jack_smith",
    "name": "Jack Smith",
    "state": "blocked",
    "locked": false,
    "avatar_url": "http://gravatar.com/../e32131cd8.jpeg",
    "web_url": "http://localhost:3000/jack_smith"
  }
]

This endpoint supports keyset pagination. In GitLab 17.0 and later, keyset pagination is required for responses of 50,000 and above.

You can also use ?search= to search for users by name, username, or public email. For example, /users?search=John. When you search for a:

  • Public email, you must use the full email address to get an exact match. A search might return a partial match. For example, if you search for the email on@example.com, the search can return both on@example.com and jon@example.com.
  • Name or username, you do not have to get an exact match because this is a fuzzy search.

In addition, you can lookup users by username:

GET /users?username=:username

For example:

GET /users?username=jack_smith

NOTE: Username search is case insensitive.

In addition, you can filter users based on the states blocked and active. It does not support active=false or blocked=false.

GET /users?active=true
GET /users?blocked=true

In addition, you can search for external users only with external=true. It does not support external=false.

GET /users?external=true

GitLab supports bot users such as the alert bot or the support bot. You can exclude the following types of internal users from the users' list with the exclude_internal=true parameter:

  • Alert bot
  • Support bot

However, this action does not exclude bot users for projects or bot users for groups.

GET /users?exclude_internal=true

In addition, to exclude external users from the users' list, you can use the parameter exclude_external=true.

GET /users?exclude_external=true

To exclude bot users for projects and bot users for groups, you can use the parameter without_project_bots=true.

GET /users?without_project_bots=true

As an administrator

DETAILS: Tier: Free, Premium, Ultimate Offering: GitLab Self-Managed, GitLab Dedicated

  • The created_by field in the response was introduced in GitLab 15.6.
  • The scim_identities field in the response introduced in GitLab 16.1.
  • The auditors field in the response introduced in GitLab 16.2.
  • The email_reset_offered_at field in the response introduced in GitLab 16.7.
[
  {
    "id": 1,
    "username": "john_smith",
    "name": "John Smith",
    "state": "active",
    "locked": false,
    "avatar_url": "http://localhost:3000/uploads/user/avatar/1/cd8.jpeg",
    "web_url": "http://localhost:3000/john_smith"
  },
  {
    "id": 2,
    "username": "jack_smith",
    "name": "Jack Smith",
    "state": "blocked",
    "locked": false,
    "avatar_url": "http://gravatar.com/../e32131cd8.jpeg",
    "web_url": "http://localhost:3000/jack_smith"
  }
]
```0

You can use all [parameters available for everyone](#as-a-regular-user) plus these additional attributes
available only for administrators.

Supported attributes:

| Attribute          | Type    | Required | Description |
|:-------------------|:--------|:---------|:------------|
| `extern_uid`       | string  | no       | Get a single user with a specific external authentication provider UID. |
| `provider`         | string  | no       | The external provider. |
| `order_by`         | string  | no       | Return users ordered by `id`, `name`, `username`, `created_at`, or `updated_at` fields. Default is `id` |
| `sort`             | string  | no       | Return users sorted in `asc` or `desc` order. Default is `desc` |
| `two_factor`       | string  | no       | Filter users by Two-factor authentication. Filter values are `enabled` or `disabled`. By default it returns all users |
| `without_projects` | boolean | no       | Filter users without projects. Default is `false`, which means that all users are returned, with and without projects. |
| `admins`           | boolean | no       | Return only administrators. Default is `false` |
| `auditors`         | boolean | no       | Return only auditor users. Default is `false`. If not included, it returns all users. Premium and Ultimate only. |
| `saml_provider_id` | number  | no       | Return only users created by the specified SAML provider ID. If not included, it returns all users. Premium and Ultimate only. |
| `skip_ldap`        | boolean | no       | Skip LDAP users. Premium and Ultimate only. |

Example response:

```json
[
  {
    "id": 1,
    "username": "john_smith",
    "name": "John Smith",
    "state": "active",
    "locked": false,
    "avatar_url": "http://localhost:3000/uploads/user/avatar/1/cd8.jpeg",
    "web_url": "http://localhost:3000/john_smith"
  },
  {
    "id": 2,
    "username": "jack_smith",
    "name": "Jack Smith",
    "state": "blocked",
    "locked": false,
    "avatar_url": "http://gravatar.com/../e32131cd8.jpeg",
    "web_url": "http://localhost:3000/jack_smith"
  }
]
```1

Users on [GitLab Premium or Ultimate](https://about.gitlab.com/pricing/) also see the
`shared_runners_minutes_limit`, `extra_shared_runners_minutes_limit`, `is_auditor`, and `using_license_seat` parameters.

```json
[
  {
    "id": 1,
    "username": "john_smith",
    "name": "John Smith",
    "state": "active",
    "locked": false,
    "avatar_url": "http://localhost:3000/uploads/user/avatar/1/cd8.jpeg",
    "web_url": "http://localhost:3000/john_smith"
  },
  {
    "id": 2,
    "username": "jack_smith",
    "name": "Jack Smith",
    "state": "blocked",
    "locked": false,
    "avatar_url": "http://gravatar.com/../e32131cd8.jpeg",
    "web_url": "http://localhost:3000/jack_smith"
  }
]
```2

Users on [GitLab Premium or Ultimate](https://about.gitlab.com/pricing/) also see
the `group_saml` provider option and `provisioned_by_group_id` parameter:

```json
[
  {
    "id": 1,
    "username": "john_smith",
    "name": "John Smith",
    "state": "active",
    "locked": false,
    "avatar_url": "http://localhost:3000/uploads/user/avatar/1/cd8.jpeg",
    "web_url": "http://localhost:3000/john_smith"
  },
  {
    "id": 2,
    "username": "jack_smith",
    "name": "Jack Smith",
    "state": "blocked",
    "locked": false,
    "avatar_url": "http://gravatar.com/../e32131cd8.jpeg",
    "web_url": "http://localhost:3000/jack_smith"
  }
]
```3

You can also use `?search=` to search for users by name, username, or email. For example, `/users?search=John`. When you search for a:

- Email, you must use the full email address to get an exact match. As an administrator, you can search for both public and private email addresses.
- Name or username, you do not have to get an exact match because this is a fuzzy search.

You can lookup users by external UID and provider:

```json
[
  {
    "id": 1,
    "username": "john_smith",
    "name": "John Smith",
    "state": "active",
    "locked": false,
    "avatar_url": "http://localhost:3000/uploads/user/avatar/1/cd8.jpeg",
    "web_url": "http://localhost:3000/john_smith"
  },
  {
    "id": 2,
    "username": "jack_smith",
    "name": "Jack Smith",
    "state": "blocked",
    "locked": false,
    "avatar_url": "http://gravatar.com/../e32131cd8.jpeg",
    "web_url": "http://localhost:3000/jack_smith"
  }
]
```4

For example:

```json
[
  {
    "id": 1,
    "username": "john_smith",
    "name": "John Smith",
    "state": "active",
    "locked": false,
    "avatar_url": "http://localhost:3000/uploads/user/avatar/1/cd8.jpeg",
    "web_url": "http://localhost:3000/john_smith"
  },
  {
    "id": 2,
    "username": "jack_smith",
    "name": "Jack Smith",
    "state": "blocked",
    "locked": false,
    "avatar_url": "http://gravatar.com/../e32131cd8.jpeg",
    "web_url": "http://localhost:3000/jack_smith"
  }
]
```5

Users on [GitLab Premium or Ultimate](https://about.gitlab.com/pricing/) have the `scim` provider available:

```json
[
  {
    "id": 1,
    "username": "john_smith",
    "name": "John Smith",
    "state": "active",
    "locked": false,
    "avatar_url": "http://localhost:3000/uploads/user/avatar/1/cd8.jpeg",
    "web_url": "http://localhost:3000/john_smith"
  },
  {
    "id": 2,
    "username": "jack_smith",
    "name": "Jack Smith",
    "state": "blocked",
    "locked": false,
    "avatar_url": "http://gravatar.com/../e32131cd8.jpeg",
    "web_url": "http://localhost:3000/jack_smith"
  }
]
```6

You can search users by creation date time range with:

```json
[
  {
    "id": 1,
    "username": "john_smith",
    "name": "John Smith",
    "state": "active",
    "locked": false,
    "avatar_url": "http://localhost:3000/uploads/user/avatar/1/cd8.jpeg",
    "web_url": "http://localhost:3000/john_smith"
  },
  {
    "id": 2,
    "username": "jack_smith",
    "name": "Jack Smith",
    "state": "blocked",
    "locked": false,
    "avatar_url": "http://gravatar.com/../e32131cd8.jpeg",
    "web_url": "http://localhost:3000/jack_smith"
  }
]
```7

You can search for users without projects with: `/users?without_projects=true`

You can filter by [custom attributes](custom_attributes.md) with:

```json
[
  {
    "id": 1,
    "username": "john_smith",
    "name": "John Smith",
    "state": "active",
    "locked": false,
    "avatar_url": "http://localhost:3000/uploads/user/avatar/1/cd8.jpeg",
    "web_url": "http://localhost:3000/john_smith"
  },
  {
    "id": 2,
    "username": "jack_smith",
    "name": "Jack Smith",
    "state": "blocked",
    "locked": false,
    "avatar_url": "http://gravatar.com/../e32131cd8.jpeg",
    "web_url": "http://localhost:3000/jack_smith"
  }
]
```8

You can include the users' [custom attributes](custom_attributes.md) in the response with:

```json
[
  {
    "id": 1,
    "username": "john_smith",
    "name": "John Smith",
    "state": "active",
    "locked": false,
    "avatar_url": "http://localhost:3000/uploads/user/avatar/1/cd8.jpeg",
    "web_url": "http://localhost:3000/john_smith"
  },
  {
    "id": 2,
    "username": "jack_smith",
    "name": "Jack Smith",
    "state": "blocked",
    "locked": false,
    "avatar_url": "http://gravatar.com/../e32131cd8.jpeg",
    "web_url": "http://localhost:3000/jack_smith"
  }
]
```9

You can use the `created_by` parameter to see if a user account was created:

- [Manually by an administrator](../user/profile/account/create_accounts.md#create-users-in-admin-area).
- As a [project bot user](../user/project/settings/project_access_tokens.md#bot-users-for-projects).

If the returned value is `null`, the account was created by a user who registered an account themselves.

## Get a single user

Get a single user.

### As a regular user

Get a single user as a regular user.

Prerequisites:

- You must be signed in to use this endpoint.

```plaintext
GET /users?username=:username
```0

Supported attributes:

| Attribute | Type    | Required | Description |
|:----------|:--------|:---------|:------------|
| `id`      | integer | yes      | ID of a user |

Example response:

```plaintext
GET /users?username=:username
```1

### As an administrator

DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed, GitLab Dedicated

> - The `created_by` field in the response was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/93092) in GitLab 15.6.
> - The `email_reset_offered_at` field in the response [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/137610) in GitLab 16.7.

Get a single user as an administrator.

```plaintext
GET /users?username=:username
```2

Supported attributes:

| Attribute | Type    | Required | Description |
|:----------|:--------|:---------|:------------|
| `id`      | integer | yes      | ID of a user |

Example response:

```plaintext
GET /users?username=:username
```3

NOTE:
The `plan` and `trial` parameters are only available on GitLab Enterprise Edition.

Users on [GitLab Premium or Ultimate](https://about.gitlab.com/pricing/) also see
the `shared_runners_minutes_limit`, `is_auditor`, and `extra_shared_runners_minutes_limit` parameters.

```plaintext
GET /users?username=:username
```4

Users on [GitLab.com Premium or Ultimate](https://about.gitlab.com/pricing/) also
see the `group_saml` option and `provisioned_by_group_id` parameter:

```plaintext
GET /users?username=:username
```5

Users on [GitLab.com Premium or Ultimate](https://about.gitlab.com/pricing/) also
see the `scim_identities` parameter:

```plaintext
GET /users?username=:username
```6

Administrators can use the `created_by` parameter to see if a user account was created:

- [Manually by an administrator](../user/profile/account/create_accounts.md#create-users-in-admin-area).
- As a [project bot user](../user/project/settings/project_access_tokens.md#bot-users-for-projects).

If the returned value is `null`, the account was created by a user who registered an account themselves.

You can include the user's [custom attributes](custom_attributes.md) in the response with:

```plaintext
GET /users?username=:username
```7

## Get the current user

Get the current user.

### As a regular user

Get your user details.

```plaintext
GET /users?username=:username
```8

Example response:

```plaintext
GET /users?username=:username
```9

Users on [GitLab Premium or Ultimate](https://about.gitlab.com/pricing/) also see the `shared_runners_minutes_limit`, `extra_shared_runners_minutes_limit` parameters.

### As an administrator

DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed, GitLab Dedicated

> - The `created_by` field in the response was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/93092) in GitLab 15.6.
> - The `email_reset_offered_at` field in the response [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/137610) in GitLab 16.7.

Get your user details, or the details of another user.

```plaintext
GET /users?username=jack_smith
```0

Supported attributes:

| Attribute | Type    | Required | Description |
|:----------|:--------|:---------|:------------|
| `sudo`    | integer | no       | ID of a user to make the call in their place |

```plaintext
GET /users?username=jack_smith
```1

Users on [GitLab Premium or Ultimate](https://about.gitlab.com/pricing/) also see these
parameters:

- `shared_runners_minutes_limit`
- `extra_shared_runners_minutes_limit`
- `is_auditor`
- `provisioned_by_group_id`
- `using_license_seat`

## Create a user

DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed, GitLab Dedicated

> - Ability to create an auditor user was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/366404) in GitLab 15.3.

Create a user.

Prerequisites:

- You must be an administrator.

When you create a user, you must specify at least one of the following:

- `password`
- `reset_password`
- `force_random_password`

If `reset_password` and `force_random_password` are both `false`, then `password` is required.

`force_random_password` and `reset_password` take priority over `password`. Also, `reset_password` and
`force_random_password` can be used together.

NOTE:
`private_profile` defaults to the value of the
[Set profiles of new users to private by default](../administration/settings/account_and_limit_settings.md#set-profiles-of-new-users-to-private-by-default) setting.
`bio` defaults to `""` instead of `null`.

```plaintext
GET /users?username=jack_smith
```2

Supported attributes:

| Attribute                            | Required | Description |
|:-------------------------------------|:---------|:------------|
| `admin`                              | No       | User is an administrator. Valid values are `true` or `false`. Defaults to false. |
| `auditor`                            | No       | User is an auditor. Valid values are `true` or `false`. Defaults to false. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/366404) in GitLab 15.3. Premium and Ultimate only. |
| `avatar`                             | No       | Image file for user's avatar |
| `bio`                                | No       | User's biography |
| `can_create_group`                   | No       | User can create top-level groups - true or false |
| `color_scheme_id`                    | No       | User's color scheme for the file viewer (for more information, see the [user preference documentation](../user/profile/preferences.md#change-the-syntax-highlighting-theme)) |
| `commit_email`                       | No       | User's commit email address |
| `email`                              | Yes      | Email       |
| `extern_uid`                         | No       | External UID |
| `external`                           | No       | Flags the user as external - true or false (default) |
| `extra_shared_runners_minutes_limit` | No       | Can be set by administrators only. Additional compute minutes for this user. Premium and Ultimate only. |
| `force_random_password`              | No       | Set user password to a random value - true or false (default) |
| `group_id_for_saml`                  | No       | ID of group where SAML has been configured |
| `linkedin`                           | No       | LinkedIn    |
| `location`                           | No       | User's location |
| `name`                               | Yes      | Name        |
| `note`                               | No       | Administrator notes for this user |
| `organization`                       | No       | Organization name |
| `password`                           | No       | Password    |
| `private_profile`                    | No       | User's profile is private - true or false. The default value is determined by [a setting](../administration/settings/account_and_limit_settings.md#set-profiles-of-new-users-to-private-by-default). |
| `projects_limit`                     | No       | Number of projects user can create |
| `pronouns`                           | No       | User's pronouns |
| `provider`                           | No       | External provider name |
| `public_email`                       | No       | User's public email address |
| `reset_password`                     | No       | Send user password reset link - true or false(default) |
| `shared_runners_minutes_limit`       | No       | Can be set by administrators only. Maximum number of monthly compute minutes for this user. Can be `nil` (default; inherit system default), `0` (unlimited), or `> 0`. Premium and Ultimate only. |
| `skip_confirmation`                  | No       | Skip confirmation - true or false (default) |
| `skype`                              | No       | Skype ID    |
| `theme_id`                           | No       | GitLab theme for the user (for more information, see the [user preference documentation](../user/profile/preferences.md#change-the-color-theme) for more information) |
| `twitter`                            | No       | X (formerly Twitter) account |
| `discord`                            | No       | Discord account |
| `username`                           | Yes      | Username    |
| `view_diffs_file_by_file`            | No       | Flag indicating the user sees only one file diff per page |
| `website_url`                        | No       | Website URL |

## Modify a user

DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed, GitLab Dedicated

> - Ability to modify an auditor user was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/366404) in GitLab 15.3.

Modify an existing user.

Prerequisites:

- You must be an administrator.

The `email` field is the user's primary email address. You can only change this field to an already-added secondary
email address for that user. To add more email addresses to the same user, use the [add email endpoint](user_email_addresses.md#add-an-email-address).

```plaintext
GET /users?username=jack_smith
```3

Supported attributes:

| Attribute                            | Required | Description |
|:-------------------------------------|:---------|:------------|
| `admin`                              | No       | User is an administrator. Valid values are `true` or `false`. Defaults to false. |
| `auditor`                            | No       | User is an auditor. Valid values are `true` or `false`. Defaults to false. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/366404) in GitLab 15.3.(default) Premium and Ultimate only. |
| `avatar`                             | No       | Image file for user's avatar |
| `bio`                                | No       | User's biography |
| `can_create_group`                   | No       | User can create groups - true or false |
| `color_scheme_id`                    | No       | User's color scheme for the file viewer (for more information, see the [user preference documentation](../user/profile/preferences.md#change-the-syntax-highlighting-theme) for more information) |
| `commit_email`                       | No       | User's commit email. Set to `_private` to use the private commit email. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/375148) in GitLab 15.5. |
| `email`                              | No       | Email       |
| `extern_uid`                         | No       | External UID |
| `external`                           | No       | Flags the user as external - true or false (default) |
| `extra_shared_runners_minutes_limit` | No       | Can be set by administrators only. Additional compute minutes for this user. Premium and Ultimate only. |
| `group_id_for_saml`                  | No       | ID of group where SAML has been configured |
| `id`                                 | Yes      | ID of the user |
| `linkedin`                           | No       | LinkedIn    |
| `location`                           | No       | User's location |
| `name`                               | No       | Name        |
| `note`                               | No       | Administration notes for this user |
| `organization`                       | No       | Organization name |
| `password`                           | No       | Password    |
| `private_profile`                    | No       | User's profile is private - true or false. |
| `projects_limit`                     | No       | Limit projects each user can create |
| `pronouns`                           | No       | Pronouns    |
| `provider`                           | No       | External provider name |
| `public_email`                       | No       | Public email of the user (must be already verified) |
| `shared_runners_minutes_limit`       | No       | Can be set by administrators only. Maximum number of monthly compute minutes for this user. Can be `nil` (default; inherit system default), `0` (unlimited) or `> 0`. Premium and Ultimate only. |
| `skip_reconfirmation`                | No       | Skip reconfirmation - true or false (default) |
| `skype`                              | No       | Skype ID    |
| `theme_id`                           | No       | GitLab theme for the user (for more information, see the [user preference documentation](../user/profile/preferences.md#change-the-color-theme) for more information) |
| `twitter`                            | No       | X (formerly Twitter) account |
| `discord`                            | No       | Discord account |
| `username`                           | No       | Username    |
| `view_diffs_file_by_file`            | No       | Flag indicating the user sees only one file diff per page |
| `website_url`                        | No       | Website URL |

If you update a user's password, they are forced to change it when they next sign in.

Returns a `404` error, even in cases where a `409` (Conflict) would be more appropriate.
For example, when renaming the email address to an existing one.

## Delete a user

DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed, GitLab Dedicated

Delete a user.

Prerequisites:

- You must be an administrator.

Returns:

- `204 No Content` status code if the operation was successful.
- `404` if the resource was not found.
- `409` if the user cannot be soft deleted.

```plaintext
GET /users?username=jack_smith
```4

Supported attributes:

| Attribute     | Type    | Required | Description |
|:--------------|:--------|:---------|:------------|
| `id`          | integer | yes      | ID of a user |
| `hard_delete` | boolean | no       | If true, contributions that would usually be [moved to Ghost User](../user/profile/account/delete_account.md#associated-records) are deleted instead, and also groups owned solely by this user. |

## Get your user status

Get your user status.

Prerequisites:

- You must be authenticated.

```plaintext
GET /users?username=jack_smith
```5

Example request:

```plaintext
GET /users?username=jack_smith
```6

Example response:

```plaintext
GET /users?username=jack_smith
```7

## Get the status of a user

Get the status of a user. You can access this endpoint without authentication.

```plaintext
GET /users?username=jack_smith
```8

Supported attributes:

| Attribute        | Type   | Required | Description |
|:-----------------|:-------|:---------|:------------|
| `id_or_username` | string | yes      | ID or username of the user to get a status of |

Example request:

```plaintext
GET /users?username=jack_smith
```9

Example response:

```plaintext
GET /users?active=true
```0

## Set your user status

Set your user status.

Prerequisites:

- You must be authenticated.

```plaintext
GET /users?active=true
```1

Supported attributes:

| Attribute            | Type   | Required | Description |
|:---------------------|:-------|:---------|:------------|
| `emoji`              | string | no       | Name of the emoji to use as status. If omitted `speech_balloon` is used. Emoji name can be one of the specified names in the [Gemojione index](https://github.com/bonusly/gemojione/blob/master/config/index.json). |
| `message`            | string | no       | Message to set as a status. It can also contain emoji codes. Cannot exceed 100 characters. |
| `clear_status_after` | string | no       | Automatically clean up the status after a given time interval, allowed values: `30_minutes`, `3_hours`, `8_hours`, `1_day`, `3_days`, `7_days`, `30_days` |

Difference between `PUT` and `PATCH`:

- When using `PUT` any parameters that are not passed are set to `null` and therefore cleared.
- When using `PATCH` any parameters that are not passed are ignored. Explicitly pass `null` to clear a field.

Example request:

```plaintext
GET /users?active=true
```2

Example response:

```plaintext
GET /users?active=true
```3

## Get your user preferences

Get your user preferences.

Prerequisites:

- You must be authenticated.

```plaintext
GET /users?active=true
```4

Example response:

```plaintext
GET /users?active=true
```5

## Update your user preferences

Update your user preferences.

Prerequisites:

- You must be authenticated.

```plaintext
GET /users?active=true
```6

```plaintext
GET /users?active=true
```7

Supported attributes:

| Attribute                        | Required | Description |
|:---------------------------------|:---------|:------------|
| `view_diffs_file_by_file`        | Yes      | Flag indicating the user sees only one file diff per page. |
| `show_whitespace_in_diffs`       | Yes      | Flag indicating the user sees whitespace changes in diffs. |
| `pass_user_identities_to_ci_jwt` | Yes      | Flag indicating the user passes their external identities as CI information. This attribute does not contain enough information to identify or authorize the user in an external system. The attribute is internal to GitLab, and must not be passed to third-party services. For more information and examples, see [Token Payload](../ci/secrets/id_token_authentication.md#token-payload). |

## Upload an avatar for yourself

> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/148130) in GitLab 17.0.

Upload an avatar for yourself.

Prerequisites:

- You must be authenticated.

```plaintext
GET /users?active=true
```8

Supported attributes:

| Attribute | Type   | Required | Description |
|:----------|:-------|:---------|:------------|
| `avatar`  | string | Yes      | The file to be uploaded. The ideal image size is 192 x 192 pixels. The maximum file size allowed is 200 KiB. |

To upload an avatar from your file system, use the `--form` argument. This causes
cURL to post data using the header `Content-Type: multipart/form-data`. The
`file=` parameter must point to an image file on your file system and be
preceded by `@`. For example:

Example request:

```plaintext
GET /users?active=true
```9

Example response:

```plaintext
GET /users?blocked=true
```0

Returns:

- `200` if successful.
- `400 Bad Request` for file sizes greater than 200 KiB.

## Get a count of your assigned issues, merge requests, and reviews

Get a count of your assigned issues, merge requests, and reviews.

Prerequisites:

- You must be authenticated.

Supported attributes:

| Attribute                         | Type   | Description |
|:----------------------------------|:-------|:------------|
| `assigned_issues`                 | number | Number of issues that are open and assigned to the current user. |
| `assigned_merge_requests`         | number | Number of merge requests that are active and assigned to the current user. |
| `merge_requests`                  | number | [Deprecated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/50026) in GitLab 13.8. Equivalent to and replaced by `assigned_merge_requests`. |
| `review_requested_merge_requests` | number | Number of merge requests that the current user has been requested to review. |
| `todos`                           | number | Number of pending to-do items for current user. |

```plaintext
GET /users?blocked=true
```1

Example request:

```plaintext
GET /users?blocked=true
```2

Example response:

```plaintext
GET /users?blocked=true
```3

## Get a count of a user's projects, groups, issues, and merge requests

Get a list of a user's count of:

- Projects.
- Groups.
- Issues.
- Merge requests.

Administrators can query any user, but non-administrators can only query themselves.

```plaintext
GET /users?blocked=true
```4

Supported attributes:

| Attribute | Type    | Required | Description |
|:----------|:--------|:---------|:------------|
| `id`      | integer | yes      | ID of a user |

Example response:

```plaintext
GET /users?blocked=true
```5

## List a user's activity

DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed, GitLab Dedicated

Prerequisites:

- You must be an administrator to view the activity of users with private profiles.

Get the last activity date for users with public profiles, sorted from oldest to newest.

The activities that update the user event timestamps (`last_activity_on` and `current_sign_in_at`) are:

- Git HTTP/SSH activities (such as clone, push)
- User logging in to GitLab
- User visiting pages related to dashboards, projects, issues, and merge requests
- User using the API
- User using the GraphQL API

By default, it shows the activity for users with public profiles in the last 6 months, but this can be
amended by using the `from` parameter.

```plaintext
GET /users?blocked=true
```6

Supported attributes:

| Attribute | Type   | Required | Description |
|:----------|:-------|:---------|:------------|
| `from`    | string | no       | Date string in the format `YEAR-MM-DD`. For example, `2016-03-11`. Defaults to 6 months ago. |

Example request:

```plaintext
GET /users?blocked=true
```7

Example response:

```plaintext
GET /users?blocked=true
```8

`last_activity_at` is deprecated. Use `last_activity_on` instead.

## List projects and groups that a user is a member of

DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed, GitLab Dedicated

Prerequisites:

- You must be an administrator.

Lists all projects and groups a user is a member of.

Returns the `source_id`, `source_name`, `source_type`, and `access_level` of a membership.
Source can be of type `Namespace` (representing a group) or `Project`. The response represents only direct memberships. Inherited memberships, for example in subgroups, are not included.
Access levels are represented by an integer value. For more details, read about the meaning of [access level values](access_requests.md#valid-access-levels).

```plaintext
GET /users?blocked=true
```9

Supported attributes:

| Attribute | Type    | Required | Description |
|:----------|:--------|:---------|:------------|
| `id`      | integer | yes      | ID of a specified user |
| `type`    | string  | no       | Filter memberships by type. Can be either `Project` or `Namespace` |

Example request:

```plaintext
GET /users?external=true
```0

Example response:

```plaintext
GET /users?external=true
```1

Returns:

- `200 OK` on success.
- `404 User Not Found` if user can't be found.
- `403 Forbidden` when not requested by an administrator.
- `400 Bad Request` when requested type is not supported.

## Disable two-factor authentication for a user

DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed, GitLab Dedicated

> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/295260) in GitLab 15.2.

Prerequisites:

- You must be an administrator.

Disables two-factor authentication (2FA) for the specified user.

Administrators cannot disable 2FA for their own user account or other administrators using the API. Instead, they can disable an
administrator's 2FA [using the Rails console](../security/two_factor_authentication.md#for-a-single-user).

```plaintext
GET /users?external=true
```2

Supported attributes:

| Attribute | Type    | Required | Description |
|:----------|:--------|:---------|:------------|
| `id`      | integer | yes      | ID of the user |

Example request:

```plaintext
GET /users?external=true
```3

Returns:

- `204 No content` on success.
- `400 Bad request` if two factor authentication is not enabled for the specified user.
- `403 Forbidden` if not authenticated as an administrator.
- `404 User Not Found` if user cannot be found.

## Create a runner linked to a user

DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, GitLab Self-Managed, GitLab Dedicated

Create a runner linked to the current user.

Prerequisites:

- You must be an administrator or have the Owner role for the target namespace or project.
- For `instance_type`, you must be an administrator of the GitLab instance.
- For `group_type` or `project_type` with an Owner role, an administrator must not have enabled [restrict runner registration](../administration/settings/continuous_integration.md#restrict-runner-registration-by-all-users-in-an-instance).
- An access token with the `create_runner` scope.

Be sure to copy or save the `token` in the response, the value cannot be retrieved again.

```plaintext
GET /users?external=true
```4

Supported attributes:

| Attribute          | Type         | Required | Description |
|:-------------------|:-------------|:---------|:------------|
| `runner_type`      | string       | yes      | Specifies the scope of the runner; `instance_type`, `group_type`, or `project_type`. |
| `group_id`         | integer      | no       | The ID of the group that the runner is created in. Required if `runner_type` is `group_type`. |
| `project_id`       | integer      | no       | The ID of the project that the runner is created in. Required if `runner_type` is `project_type`. |
| `description`      | string       | no       | Description of the runner. |
| `paused`           | boolean      | no       | Specifies if the runner should ignore new jobs. |
| `locked`           | boolean      | no       | Specifies if the runner should be locked for the current project. |
| `run_untagged`     | boolean      | no       | Specifies if the runner should handle untagged jobs. |
| `tag_list`         | string array | no       | A list of runner tags. |
| `access_level`     | string       | no       | The access level of the runner; `not_protected` or `ref_protected`. |
| `maximum_timeout`  | integer      | no       | Maximum timeout that limits the amount of time (in seconds) that runners can run jobs. |
| `maintenance_note` | string       | no       | Free-form maintenance notes for the runner (1024 characters). |

Example request:

```plaintext
GET /users?external=true
```5

Example response:

```plaintext
GET /users?external=true
```6

## Delete authentication identity from a user

DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed, GitLab Dedicated

Delete a user's authentication identity using the provider name associated with that identity.

Prerequisites:

- You must be an administrator.

```plaintext
GET /users?external=true
```7

Supported attributes:

| Attribute  | Type    | Required | Description |
|:-----------|:--------|:---------|:------------|
| `id`       | integer | yes      | ID of a user |
| `provider` | string  | yes      | External provider name |