---
title: "Update a custom field"
method: PUT
path: "/v3/custom-fields/{id}"
tags: ["Custom Fields"]
---

# Update a custom field

`PUT /v3/custom-fields/{id}`

<small>_Requires the `contacts:write` scope (or a broader one that includes it)._</small>

Updates an existing custom field

## Path parameters

- `id` integer, required

## Request body

- object
  - `title` string, required — Custom field name
  - `fieldType` 'text' | 'number', required — Custom field type
  - `metadata` string, nullable — Optional metadata for the field (e.g., dropdown options)

## Response `200`

Custom field updated successfully

- object — A user-defined field for storing additional data on contacts.
  - `id` integer — Custom field ID
  - `title` string — Custom field name
  - `fieldType` 'text' | 'number' — Custom field type
  - `metadata` string, nullable — Optional metadata for the field (e.g., dropdown options)
  - `orgWide` boolean — Whether the field is shared across the organization

## Other responses

- `400` — Validation failure on the route param or request body, or a business rule rejection (e.g. invalid metadata for the chosen field type).
- `401` — Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme.
- `403` — User lacks required feature scope to modify custom fields
- `404` — Custom field not found
- `409` — Duplicate field name
- `429` — Too Many Requests

---

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