---
title: "Update your own profile"
method: PATCH
path: "/v1/{account_id}/users/{user_id}"
tags: ["Users"]
---

# Update your own profile

`PATCH /v1/{account_id}/users/{user_id}`

## Request

- Base URL: `https://api.curviate.com`
- URL: `https://api.curviate.com/v1/{account_id}/users/{user_id}`
- Auth: HTTP bearer

Updates the caller's own profile fields. Only first_name, last_name, bio, headline, skills, picture, and background_picture are accepted; any other field is rejected. Profile changes can take a short while to appear on LinkedIn; rapid successive edits may not all be applied.

## Path parameters

- `account_id` string, required
- `user_id` string, required

## Request body

- object
  - `first_name` string: New first name.
  - `last_name` string: New last name.
  - `bio` union: New text for your profile's About section.
    - ''
    - string
  - `headline` string: Your profile headline (the short line shown under your name).
  - `skills` object[]: Skills to add to your profile. Add-only, this does not remove or reorder existing skills.
    - `name` string, required: The skill name to add.
    - `id` string: Optional skill parameter id, from GET /v1/{account_id}/search/parameters?type=SKILL.
  - `picture` object: New profile photo (base64).
    - `content` string, required: Base64-encoded file bytes.
    - `content_type` string, required: File MIME type (e.g. image/png, image/jpeg).
    - `filename` string, required: File name.
  - `background_picture` object: New cover/banner photo (base64).
    - `content` string, required: Base64-encoded file bytes.
    - `content_type` string, required: File MIME type (e.g. image/png, image/jpeg).
    - `filename` string, required: File name.

## Response `200`

The profile was updated. The exact response shape beyond the discriminator is not yet fully documented, additional fields may appear.

- object
  - `object` 'user_updated', required: Response type discriminator.
  - `safety_warning` SafetyWarning: Present on a successful response when this account crossed an account-safety ceiling while the affected budget row is on the default warn posture. The action still happened. Field-identical to the BUDGET_EXHAUSTED error body except that blocked is false and hint.message describes the outcome, so one branch handles both postures and switching the account to enforce is a configuration change rather than a client rewrite.
    - `row` string, nullable, required: The budget row that breached, for example profile_views or pending_invites. Null when the breach is not about a row: an activity_window warning on an action that spends no budget of its own (editing a message, dismissing a notification, a Recruiter or Sales Navigator admin action) is still governed by the hours the account works in. Read hint.parameter for what to change; whenever this is null it names posture, because the activity window edges are set per action type and this action has none, so the levers that reach it are the account timezone and posture.
    - `reset_at` string, nullable, required: The instant the refusal lifts: the window roll on a ceiling refusal, the next window open on an activity-window one. Null in the two cases no clock frees, the pending_invites gauge and InMail credits (row inmail).
    - `hint` object, required
      - `parameter` string, required: The settable parameter on PATCH /v1/{account_id}/safety-policy.
      - `message` string, required: What the condition is and what changing that parameter would do. This is the one field whose text differs from the BUDGET_EXHAUSTED refusal: here it says the action went through, and on a ceiling breach how far past the ceiling this row now stands, rather than telling you to set posture to warn when it already is. Branch on parameter, reason and blocked, never on this text.
    - `reason` 'ceiling' | 'activity_window', required: Which rule was crossed. ceiling means the row's configured limit is spent; activity_window means the account is outside the hours it works in, which is a different fact with a different remedy. hint.parameter names the right setting for each.
    - `blocked` boolean, required: Always false here. True on the BUDGET_EXHAUSTED refusal carrying the same payload.

## Other responses

- `400`: An unsupported field was supplied (only first_name, last_name, bio, description, picture, background_picture are accepted), or a supplied value is malformed.
- `401`: Missing or invalid API key.
- `404`: The account_id does not belong to this tenant. An id whose connection was replaced or removed also stops resolving here, and it is already absent from the list, so re-read `GET /v1/accounts` for the current id.
- `413`: Payload too large. Three triggers, smallest first: the platform's own ceiling on total request size, which rejects bodies from roughly 1 MB and is the one most callers hit; then the caps enforced here, 5 MiB per attachment and 9 MiB for the whole request body. Base64 inflates a file by about 33 percent, so a 5 MiB file costs about 6.7 MiB of the body budget. Send fewer or smaller attachments; retrying the same request unchanged will not help.
- `415`: Unsupported content type, send application/json.
- `422`: The account is restricted and cannot be updated.
- `429`: Rate limited, slow down and retry after the hinted delay.
- `500`: Internal error.
- `502`: A temporary error occurred. Please try again.
- `503`: Service unavailable.
- `504`: Gateway timeout.

---

[API](https://skmtc.dev/curviate/apis/curviate-api.md) · [All operations](https://skmtc.dev/curviate/apis/curviate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/curviate/apis/curviate-api/revisions/eab848801d95?raw)