Skip to main content
PUT
Bulk full-replace and/or soft-delete of compliance custom field definitions in a single transaction.

Headers

X-Delogue-Api
string

Body

id
integer<int64>
required

Unique identifier of the compliance custom field to update. Required on every bulk item.

name
null | string

Display name of the field. Required on a full replace; on PATCH it is preserved when the patch does not touch it.

userDefinedId
null | string

Customer-defined identifier for the field. Null clears the stored value; on PATCH omit it to preserve the current value.

state
null | enum<string>

Target lifecycle state of the field. Required on a full replace and, on PATCH, preserved when the patch does not touch it.

Available options:
active,
inactive,
deleted
position

Read-only. Sending a non-null value is rejected with a 400 validation error; omit it or send null.

internalOnly
boolean

When true, the field is visible to brand users only. On a full replace, an omitted value resets it to false.

isMandatory
boolean

When true, the field must be filled in before submission. On a full replace, an omitted value resets it to false.

isMultiLine
boolean

When true, a text-type field renders as a multi-line text area. On a full replace, an omitted value resets it to false.

isSortByAllowedValueId
boolean

When true, allowed values sort by insertion order rather than alphabetically. On a full replace, an omitted value resets it to false.

maxChar

Maximum character length allowed for a text-type field. Null clears the limit.

allowedDecimals

Number of decimal places allowed for a numeric-type field. Null clears the setting.

parentCustomFieldId
null | integer<int64>

Identifier of the parent field for a nestedAllowedValue child. Null clears the parent link.

allowedValues
null | object[]

Full replacement list of selectable options for allowedValue and nestedAllowedValue fields. Omit or send null to clear all existing options.

Response

OK

status
enum<string>
required

The coarse outcome of the request, indicating whether it succeeded or failed.

Available options:
success,
error
code
string
required

The specific machine-readable outcome code, such as ok on success or the most specific error code on failure. Always lowercase on the wire.

data
null | object[]
required

The response payload, either a single object for a by-id read or an array for a bulk operation. Omitted from the body when there is no value.