Fields

Contact Person Fields

Field name	Meaning	Bytes	Mandatory	Writable
id	Unique ID of the contact	4
account_id	Account associated with the contact	4
active	Indicates whether the contact is included in standard operations (searches, for example)	1		•
gender	Gender (m,f,n)	1	•	•
first_name	First name	32		•
last_name	Last name	64	•	•
location_id	Unique ID of the contact's location	4		•
phone	Phone number	32		•
fax	Fax number	32		•
mobile_phone	Mobile phone number	32		•
email	E-mail address	128		•
job_title	Position / field of work	64		•
want_email	Contact accepts e-mails (if deactivated, newsletters, inquiry confirmations, etc. will also not be sent)	1		•
want_phonecall	Contact person accepts phone calls	1		•
want_snailmail	Contact person accepts letters	1		•
language	Code of one of the languages defined in the settings, e.g. en	8	•	•
login	user name, e.g. for logging into the website	128		•
custom1 - custom10	Custom field 1 to 10	80		•
title	One of the configured academic titles, or empty	10		•
updated_at	Point in time of last change

When calling the contacts web service you can have account and location data included in the results. This account and location data also includes the updated_at field. However, the accounts and locations web services do not return this field.

Fields of a Contact Person’s Diary Entries

The individual diary entries of contact persons are only accessible via the web interface of the OMC.

Field name	Meaning	Bytes	Mandatory	Writable
id	Unique ID of the diary entry	8
account_id	ID of the account to which the entry belongs	4
contact_id	ID of the contact to which the entry belongs	4
internal	Always true for individual diary entries	1
created_at	Creation time
created_by	Origin of the entry, e.g. webservice	32
updated_at	Date and time the entry was last updated
updated_by	User who updated the entry, or webservice	32
diary_type	Diary entry type, e.g. web	10		•
title	Title or subject	250	•	•
notes	Additional information about the entry	∞		•