Create a custom field
Defines a new field. Send a label; the key is derived from it.
type is one of text, number, date, select. A select needs options, at least one and at most 50, and a value is then checked against them, case-insensitively.
A label whose key would collide with a standard contact variable, such as name, phone or timezone, is refused: a custom field is applied to the call’s variables after the engine’s own, so it would silently overwrite the lead’s real name or number in the prompt. caller_pref is refused for the same reason and matters most, since it is the contact’s memory.
Cookie-auth callers must send the x-csrf-token header.
Required API key scope: contacts:write.
Authorizations
Send your API key as Authorization: Bearer YOUR_API_KEY.
Query Parameters
The sub-account. It is the only thing that identifies the tenant on these routes, and it is re-checked against your access on every call. A sub-account that keeps its contacts in a CRM answers 400.
Body
The field.
