---
title: "PATCH (rename) a Segment"
method: PATCH
path: "/segments/{segment_id}/name"
tags: ["Segments"]
---

# PATCH (rename) a Segment

`PATCH /segments/{segment_id}/name`

Use this method to update an existing segment `name` with a new unique name in the request body. For more use case information, see [Rename a Segment](/api_guide/segment_rename.html) in the API guide.

## Path parameters

- `segment_id` integer, required

## Request body

- SegmentName
  - `name` string, required — The segment's unique descriptive name.

## Response `200`

The segment name was successfully updated.

- SegmentDetail
  - `name` string — The segment's unique descriptive name.
  - `segment_criteria` string — The segment's contact selection criteria formatted as single-string escaped JSON.
  - `segment_id` integer — The system generated number that uniquely identifies the segment.
  - `created_at` string, date-time — The system generated date and time (ISO-8601) that the segment was created.
  - `edited_at` string, date-time — The system generated date and time (ISO-8601) that the segment's <code>name</code> or <code> segment_criteria</code> was last updated.

## Other responses

- `400` — Bad request. Either the JSON was malformed or there was a data validation error.
- `401` — The Access Token used is invalid.
- `403` — Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
- `404` — The requested resource was not found.
- `409` — Conflict. The resource you are creating or updating conflicts with an existing resource.
- `415` — Unsupported Media Type.
- `500` — There was a problem with our internal service.

---

[API](https://skmtc.net/cc/apis/appconnect-v3.md) · [All operations](https://skmtc.net/cc/apis/appconnect-v3/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cc/appconnect-v3/versions/4b4a534c818d/schema)