Create or Update Field
Creates a custom field on contacts or companies, or updates the one of that name, under the rules of the lemlist app.
Authorizations
Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
Body
Entity the field belongs to.
contact, company Key to write the field with on POST /contacts or POST /companies. Starts with a lowercase letter, followed by letters and digits only. Identifies the field to update; never changes afterwards.
400^[a-z][a-zA-Z0-9]*$Field data type. On an existing field, only text or multilineText may differ from the stored type (a conversion), and a phone or user field keeps its type.
text, multilineText, number, date, select, boolean, phone, user, url Display name of the field, as shown in lemlist. Cannot contain an HTML tag (<...>). Optional: defaults to name on creation, unchanged when omitted on an update.
400Select fields only. On creation, the options (at least one). On an update, options to add when missing; the present ones and the others are kept, so the same list replays. Distinct and non-empty; compared as in the app, regardless of case and surrounding spaces (gold matches an existing Gold), and stored without surrounding spaces.
Select fields only, on an update: { "current value": "new value" }. The option keeps its identity, so the contacts or companies holding the current value are rewritten to the new one.
Show child attributes
Show child attributes
Select fields only, on an update: options to drop. The contacts or companies holding one are cleared. At least one option must remain.
Was this page helpful?