---
title: "Update metadata value"
method: PUT
path: "/documents/{document}/metadata-values/{metadataValue}"
tags: ["Document Operations"]
---

# Update metadata value

`PUT /documents/{document}/metadata-values/{metadataValue}`

<small>Requires an API token with the **Document Manager** role.</small>

Updates the value of a [metadata](/#metadata) field for a [document](/#documents).

> Alternatively: if your use case involves updating multiple metadata fields, and you have all the new values
> available at once, the [bulk update metadata values](/operations/v1.documents.metadata-values.bulk-update)
> request is likely to be a better fit.

## Value format

The content of the `value` parameter must follow the same rules as described in the [Add metadata value to
document](/operations/v1.documents.metadata-values.store) documentation.

## Path parameters

- `document` string, required
- `metadataValue` string, required

## Request body

- object
  - `value` union — The new value for the field
    - unknown[]
      - unknown
    - boolean
    - string

## Response `200`

`MetadataValueResource`

- object
  - `data` MetadataValueResource, required
    - `uuid` string, required
    - `metadata` MetadataResource, required
      - `uuid` string, required
      - `type` 'system_autofilled' | 'system_computed' | 'system' | 'system_reference' | 'account', required
      - `value_type` 'id' | 'uuid' | 'bool' | 'date' | 'duration' | 'email' | 'list' | 'number' | 'currency' | 'currency_duration' | 'clause' | 'select' | 'multi_select' | 'text' | 'textarea' | 'timestamp' | 'array' | 'enum', required
      - `name` string, required
      - `display_name` string, required
      - `settings` MultiFieldSettingsResource, required
        - `currencies` string[], required — For `currency` or `currency_duration` fields, defines the currencies that can be assigned to the field's values
      - `select_values` string[], nullable, required — When `value_type` is `select`, defines the possible values for the metadata's value
      - `always_exists` boolean, required
      - `description` string, nullable, required
      - `keywords` string, nullable, required — Keywords to help with metadata identification.
      - `prompt` string, nullable, required — An AI prompt used for metadata extraction.
      - `is_contract_value` boolean, required — If true, this metadata will be included in the calculated "contract value" if it is present in a document. Only relevant when the value type is one of: `currency`, `currency_duration`
      - `relevant_document_type_uuids` string[], nullable, required — UUIDs of document types this metadata is relevant for. `null` means not relevant to any. `[]` means relevant to all.
    - `reference_dynamic_field_uuid` string, nullable, required
    - `value_source` 'user' | 'ai_analysis' | 'computed' | 'autofilled' | 'dynamic_field' | 'linked_document', required
    - `value` union, required — The metadata's value
      - string
      - boolean
      - unknown[]
        - unknown
    - `value_currency_monthly` string, nullable, required
    - `value_currency_yearly` string, nullable, required
    - `computed_status` 'missing_information' | 'conflicting_information' | 'not_applicable' | 'computed', required
    - `computed_value` union, required
      - string
      - boolean
      - unknown[]
        - unknown
    - `is_attached` boolean, required
    - `computed_at` string, date-time, nullable, required

## Other responses

- `401` — Unauthenticated
- `403` — Authorization error
- `404` — Not found
- `422` — Validation error

---

[API](https://skmtc.dev/fynk/apis/fynk-api-reference.md) · [All operations](https://skmtc.dev/fynk/apis/fynk-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/fynk/fynk-api-reference/revisions/9657a6757f59/schema)