---
title: "Rename profile by ID or name"
method: PATCH
path: "/profiles/{id_or_name}"
tags: ["Profiles"]
---

# Rename profile by ID or name

`PATCH /profiles/{id_or_name}`

Update a profile's name. Names must be unique within the logical project; during the default-project migration, unscoped profiles and profiles in the org default project are treated as the same project. Duplicate-name conflicts are checked before update but are best-effort because there is no backing unique index. Renaming a profile while a browser session references it by name may prevent that session's changes from saving; prefer renaming when the profile is not in use.

## Path parameters

- `id_or_name` string, required

## Request body

- ProfileUpdateRequest
  - `name` string, required — New profile name. Must be unique within the logical project; during the default-project migration, unscoped profiles and profiles in the org default project are treated as the same project.

## Response `200`

Profile updated

- Profile — Browser profile metadata.
  - `id` string, required — Unique identifier for the profile
  - `name` string, nullable — Optional, easier-to-reference name for the profile
  - `created_at` string, date-time, required — Timestamp when the profile was created
  - `updated_at` string, date-time — Timestamp when the profile was last updated
  - `last_used_at` string, date-time — Timestamp when the profile was last used

## Other responses

- `400` — Bad Request – invalid input
- `401` — Unauthorized – missing or invalid authorization token
- `403` — Forbidden – insufficient permissions or plan
- `404` — Resource not found
- `409` — Conflict – resource already exists
- `500` — Internal Server Error

---

[API](https://skmtc.net/kernel/apis/kernel-api.md) · [All operations](https://skmtc.net/kernel/apis/kernel-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/kernel/kernel-api/versions/9e8ce9fcf5e1/schema)