FieldValueRequestDTO
Write-variant of FieldValueDTO — used inside a LeadCreateRequestDTO or
ContactRequestDTO fields[] item to create or update a single CRM field value.
Tri-state per key. Each key is interpreted by its presence in the item:
omitted → the attribute is left unchanged; present with a value → updated; explicit
null → cleared. id is the exception: it is the CRM field identifier and must
always be sent so the value can be matched to its field.
Multi-select on write. When sending a multi-select field, put the selected
values in valueList ({ "id": 1, "valueList": ["A", "B"] }). The API expands each
value into its own entry before processing.
NUMBER fields. Send the amount in number, not value. As a fallback, a
numeric string sent in value is parsed into number — but number is what's
actually stored, so prefer sending it directly. If the field's format is
CURRENCY, currencyId is also required; omitting it (or leaving number
unresolvable) is rejected with an error naming the field.
CRM field identifier this value belongs to. Always required.
1Simple value (as text)
VIPMultiple values (for multi-select fields).
["VIP","New"]Field value type enum.
Possible values: [STREET, DISTRICT, DEFAULT]
DEFAULTDEFAULTField type (lowercased, e.g. text, select)
selectWhich entity a field/value belongs to.
LED— the leadCONTACT— the contact
Possible values: [LED, CONTACT]
LEDGeo coordinate: longitude (for location fields)
69.2401Geo coordinate: latitude (for location fields)
41.2995Value for NUMBER fields. Required (directly or via the value fallback) when the field's type is NUMBER.
1500.5Currency ID. Required when the NUMBER field's format is CURRENCY.
24{
"id": 1,
"value": "VIP",
"valueList": [
"VIP",
"New"
],
"valueType": "DEFAULT",
"type": "select",
"infoType": "LED",
"longitude": 69.2401,
"latitude": 41.2995,
"number": 1500.5,
"currencyId": 24
}