---
title: "Update/Add Custom Fields"
method: PATCH
path: "/cards/{cardId}/custom-fields"
tags: ["Cards"]
---

# Update/Add Custom Fields

`PATCH /cards/{cardId}/custom-fields`

Update the default values of [custom fields](/docs/custom-fields-on-transactions) related to a card or add new ones by `label`. All [custom fields](/docs/custom-fields-on-transactions) need to be provided, by not providing a custom field, the default value of that custom field will be removed, i.e. set to `null`. Updates of existing custom fields may happen via `id` or `label`. Adding new fields is only possible by providing a currently unused `label`. Note: the `label` needs to be unique per organization.

## Path parameters

- `cardId` string, uuid, required

## Request body

- object
  - `customFields` CustomFields — unresolved $ref

## Response `202`

Accepted

- object[] — The [custom fields](/docs/custom-fields-on-transactions) set on this card after the update. These [custom fields](/docs/custom-fields-on-transactions) are used as default values for every transaction made with this card. If no [custom fields](/docs/custom-fields-on-transactions) are assigned to the card, we return an empty list.
  - `id` string, uuid, required — The id of the custom field used on this card.
  - `label` string, required — The label of the custom field used on this card.
  - `defaultValue` string, nullable — The default value of the custom field on this card. This default value will be copied to every transaction made with this card.

## Other responses

- `400` — unresolved $ref
- `401` — unresolved $ref
- `403` — unresolved $ref
- `404` — unresolved $ref
- `429` — unresolved $ref
- `500` — unresolved $ref

---

[API](https://skmtc.dev/getpliant/apis/pliant-customer-api.md) · [All operations](https://skmtc.dev/getpliant/apis/pliant-customer-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/getpliant/pliant-customer-api/revisions/f3f589cfa718/schema)