---
title: "Modifying a User"
method: PATCH
path: "/v1/users/{actorId}"
tags: ["Users"]
---

# Modifying a User

`PATCH /v1/users/{actorId}`

You can `PATCH` JSON data to update User details. Not all user information is modifiable; right now, the following fields may be updated:

* `displayName` sets the friendly display name the web interface uses to refer to the user.

* `email` sets the email address associated with the account.

When user details are updated, the `updatedAt` field will be automatically updated.

## Path parameters

- `actorId` string, required

## Response `200`

OK

- object
  - `createdAt` string, required — ISO date format
  - `displayName` string, required — All `Actor`s, regardless of type, have a display name
  - `id` number, required
  - `type` 'user' | 'field_key' | 'public_link' | 'singleUse', required — the Type of this Actor; typically this will be `user`.
  - `updatedAt` string — ISO date format
  - `deletedAt` string — ISO date format
  - `email` string, required — Only `User`s have email addresses associated with them

## Other responses

- `400` — Bad Request

## Changes

- **2025-12-20** `022694254f0d` — 1 info
  - api operation id `Modifying a User` removed and replaced with `modifyUser`
- **2025-10-27** `b11b54eea487` — 1 info
  - removed the non-success response with the status `403`
- **2025-03-13** `e8c2858fd4eb` — 2 info
  - api operation id `modifyUser` removed and replaced with `Modifying a User`
  - added the non-success response with the status `403`

[Change history](https://skmtc.dev/getodk/apis/odk-central-api/changes/v1/users/:actorId/patch.md)

---

[API](https://skmtc.dev/getodk/apis/odk-central-api.md) · [All operations](https://skmtc.dev/getodk/apis/odk-central-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/getodk/odk-central-api/revisions/d4f5ba77f644/schema)