---
title: "Update Profile"
method: PATCH
path: "/v1/users/me"
---

# Update Profile

`PATCH /v1/users/me`

## Request

- Base URL: `https://api.mireye.com`
- URL: `https://api.mireye.com/v1/users/me`
- Auth: none declared
- TypeScript: <https://skmtc.dev/mireye/apis/mireye-earth/docs/v1/users/me/patch.ts> (a function with typed inputs; its response is checked against the schema)

## Request body

- ProfilePatch: The user-editable profile, as PATCH /v1/users/me accepts it. extra="forbid" fails the WHOLE save on an unknown key, not just that key — so the onboarding modal asking three questions against a one-field schema 422'd every non-empty submit and lost the organization with it. The two onboarding answers are first-class here now. Keep in step with account_store.PROFILE_FIELDS, which is what actually persists them.
  - `organization` string, nullable
  - `referral_source` string, nullable
  - `use_case` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/mireye/apis/mireye-earth.md) - [All operations](https://skmtc.dev/mireye/apis/mireye-earth/llms.txt) - [OpenAPI document](https://skmtc.dev/mireye/apis/mireye-earth/revisions/d8410ba83654?raw)