Zendesk Support has a variety of custom fields for tickets, organizations, and users. When updating one of these, the following question often comes up: What types of values are expected in the different kinds of custom fields?
The Zendesk developer documentation highlights how you can submit an update to a ticket under Setting custom field values. We use the same types of values for User fields and Organizations. The key difference between tickets vs users and organizations is that when updating the field, you must use the field key instead of the field id number. The expected value is the same. See the table below.
|Custom Field Type||Expected value(s)|
|Credit card||Valid credit card string/number|
|Date||ISO 8601 strings. Example:
|Decimal||String composed of numbers. May contain an optional decimal point (
|Drop-down list (tagger)||Tag value for the desired option. You can use the API to List ticket field options, which includes each option's tag value|
|Integer||String composed of integers|
|Multi-line Text||String. Line break characters allowed|
|Regular Expression (Regex)||String that matches the Regex pattern found in the custom field settings|
|Multi-select||Array that contains one or more tag values belonging to the field's options (