---
title: "Rename a custom data column in campaign contacts"
method: PATCH
path: "/campaigns/call/{campaignscalllistuuid}/numbers/columns/rename"
tags: ["campaigns"]
---

# Rename a custom data column in campaign contacts

`PATCH /campaigns/call/{campaignscalllistuuid}/numbers/columns/rename`

Renames an existing custom column in all contacts' `social_data` field. The new name must not conflict with any existing field name (in or outside of `social_data`). Provide `old_name` and `new_name` in the request body. This operation is logged in the campaign's audit log (see `GET .../logs`).

**Permission:** No specific permission required. A valid API key is sufficient.

## Path parameters

- `campaignscalllistuuid` string, uuid, required

## Request body

- CampaignCalllistNumberRenameColumn
  - `old_name` string, required — Name of the column to rename
  - `new_name` string, required — New column name

## Response `200`

Successful operation

## Other responses

- `400` — Invalid request (empty old_name, empty new_name). Column old_name doesn't exist. Column new_name already exists.
- `401` — Token unauthorized
- `404` — Campaign not found
- `500` — Internal server error

---

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