---
title: "Updating an existing Custom Field Value"
method: PUT
path: "/custom_field_values/{id}"
tags: ["Custom Field Values"]
---

# Updating an existing Custom Field Value

`PUT /custom_field_values/{id}`

## Request

- Base URL: `https://api.mavenlink.com/api/v1`
- URL: `https://api.mavenlink.com/api/v1/custom_field_values/{id}`
- Auth: none declared

Updates an existing value for the specified custom field. Up to 100 values can be updated at one time.


This endpoint returns structured Custom Field Value objects.
As with all Kantata OX API endpoints, the returned data will be referenced in sorted order in the `results` array
and will be indexed by ID in the `custom_field_values` top-level JSON key.
Please see our [Response Format](#section/Response-Format) section for more information.

## Path parameters

- `id` integer, required

## Query parameters

- `include` string

## Request body

- object
  - `custom_field_value` object
    - `value` string, required: The new value that replaces the existing value for the specified custom field. These value types are updated in the following formats: | Value Type | Format | Sample | | -------------------- |:----------------------------------------:| --------------:| | `string` | `<text_string>` | `"foo"` | | `date` | `<ISO_8601 Date Format>` | `"2014-02-25"` | | `number` | `<integer_value>` | `13` | | `currency` | `[<int_value_in_cents>, <currency_code>]`| `[998, "USD"]` | | `single` and `multi` | `[<choice_ids>]` | `[1, 2, 4]` | For [single or multi choice](/tag/Custom-Field-Choices) Custom Fields, you can think of selected choice(s) as a list, even with only 1 selected choice. The list of values in your request becomes the new list of selected choices. And the new choices all have new, unique choice IDs. ##### Note: The `write_access` [permission setting on each custom field](https://knowledge.kantata.com/hc/en-us/articles/202924760#see) determines the minimum permission needed to edit the value of each custom field. * Editing `Workspace` (Project), `Resource`, and `Story` (Task) custom fields are project-specific changes, so permissions are set at the project level: - `project_collaboration` - `time_logging` - `financial` - `project_admin` (default) Most account-level permissions supercede project-level permissions. Therefore, Account Administrators are able to edit all Project, Resource, and Task custom fields and values across the account, regardless of project participation or `write_access` settings. * Editing `Estimate`, `WorkspaceGroup` (Group), and `User` custom fields are account-wide changes, so permissions are set at the account level: - `account_collaboration` - `project_creator` - `project_lead` - `reports_viewer` - `reports_viewer_with_cost` - `account_admin` (default).

## Response `200`

Custom Field Value has been updated.

- object
  - `count` integer
  - `meta` object
    - `count` integer
    - `page_count` integer
    - `page_number` integer
    - `page_size` integer
  - `results` object[]
    - `key` string
    - `id` string
  - `custom_field_values` object
  - `external_references` object
  - `custom_fields` object
  - `users` object
  - `custom_field_choices` object
  - `stories` object
  - `workspaces` object
  - `workspace_groups` object

## Other responses

- `400`: Bad Request
- `401`: Unauthorized request
- `403`: Forbidden request
- `404`: Page Not Found
- `422`: Unprocessable Entity
- `503`: Service is unavailable

---

[API](https://skmtc.dev/kantata/apis/kantata-ox-api-documentation.md) - [All operations](https://skmtc.dev/kantata/apis/kantata-ox-api-documentation/llms.txt) - [OpenAPI document](https://skmtc.dev/kantata/apis/kantata-ox-api-documentation/revisions/9d4ebed2fa98?raw)