Contacts
Introduction
Contacts store organization and contact-person details within a ContactList.
The notes field uses the shared Rich Text HTML format. All endpoints require the contact-lists-show permission.
Model Definition
Relations
These relations are included by default. Pass an empty relations value to suppress them.
Search Fields
name- Contact name.phone- General phone number.fax- Fax number.email- General email address.street- Street address.zipcode- Postal code.city- City.notes- Notes content.contact_person_name- Contact person's name.contact_person_position- Contact person's position.contact_person_phone- Contact person's phone number.contact_person_mobile_phone- Contact person's mobile phone number.contact_person_email- Contact person's email address.
Order Directions
asc- Sorts values in ascending order.desc- Sorts values in descending order.
Uppercase ASC and DESC are also accepted.
CSV Columns
contact_list- Contact list name resolved tocontact_list_id.name- Contact name.phone- General phone number.fax- Fax number.email- General email address.street- Street address.zipcode- Postal code.city- City.notes- Notes content.contact_person_name- Contact person's name.contact_person_position- Contact person's position.contact_person_phone- Contact person's phone number.contact_person_mobile_phone- Contact person's mobile phone number.contact_person_email- Contact person's email address.
List
List Contacts.
Definition
GET /api/contacts
Request Keys
selects
string
All fields
Comma-separated fields to return.
search_text
string
-
Text used to filter the selected field.
limit
integer
No limit
Maximum number of contacts. Minimum 1.
order_field
string
name
Field used for ordering.
Behavior
Contact-list department and user assignments do not restrict this endpoint. Contacts created by the reserved intratool Admin account are omitted.
Example Request
Example Response
Show
Show one Contact.
Definition
GET /api/contacts/{id}
Route Parameters
id
integer
Contact ID.
Request Keys
selects
string
All fields
Comma-separated fields to return.
Behavior
Contact-list department and user assignments do not restrict this endpoint.
Example Request
Example Response
Create
Create a new Contact.
Definition
POST /api/contacts
Request Keys
name*
string
-
Contact name.
phone
string | null
null
General phone number.
fax
string | null
null
Fax number.
email
string | null
null
Valid general email address.
street
string | null
null
Street address.
zipcode
string | null
null
Postal code.
city
string | null
null
City.
contact_person_name
string | null
null
Contact person's name.
contact_person_position
string | null
null
Contact person's position.
contact_person_phone
string | null
null
Contact person's phone number.
contact_person_mobile_phone
string | null
null
Contact person's mobile phone number.
contact_person_email
string | null
null
Contact person's email address.
Keys with * are required.
Behavior
Requires
contact-lists-create-contactsorcontact-lists-administration-rights.The authenticated user is stored as
user_id.Empty optional contact values are normalized to
null.
Example Request
Example Response
Update
Update an existing Contact.
Definition
PUT /api/contacts/{id}
Route Parameters
id
integer
Contact ID.
Request Keys
name
string
Contact name.
phone
string | null
General phone number.
fax
string | null
Fax number.
email
string | null
Valid general email address.
street
string | null
Street address.
zipcode
string | null
Postal code.
city
string | null
City.
contact_person_name
string | null
Contact person's name.
contact_person_position
string | null
Contact person's position.
contact_person_phone
string | null
Contact person's phone number.
contact_person_mobile_phone
string | null
Contact person's mobile phone number.
contact_person_email
string | null
Contact person's email address.
Behavior
Requires
contact-lists-edit-all-contacts, or ownership together withcontact-lists-edit-own-contacts. Administration rights satisfy either check.Empty optional contact values are normalized to
null.
Example Request
Example Response
Delete
Delete an existing Contact.
Definition
DELETE /api/contacts/{id}
Route Parameters
id
integer
Contact ID.
Behavior
Requires
contact-lists-delete-all-contacts, or ownership together withcontact-lists-delete-own-contacts. Administration rights satisfy either check.The contact is soft-deleted.
Example Request
Example Response
Download Import Template
Download a CSV template containing the supported contact columns.
Definition
GET /api/contacts/import-template
Request Keys
name
string
name
Header name for the name CSV column.
phone
string
phone
Header name for the phone CSV column.
fax
string
fax
Header name for the fax CSV column.
email
string
email
Header name for the email CSV column.
street
string
street
Header name for the street CSV column.
zipcode
string
zipcode
Header name for the zipcode CSV column.
city
string
city
Header name for the city CSV column.
notes
string
notes
Header name for the notes CSV column.
contact_person_name
string
contact_person_name
Header name for the contact_person_name CSV column.
contact_person_position
string
contact_person_position
Header name for the contact_person_position CSV column.
contact_person_phone
string
contact_person_phone
Header name for the contact_person_phone CSV column.
contact_person_mobile_phone
string
contact_person_mobile_phone
Header name for the contact_person_mobile_phone CSV column.
contact_person_email
string
contact_person_email
Header name for the contact_person_email CSV column.
Behavior
This compatibility endpoint uses application-session authentication instead of the API bearer-token guard.
The response downloads
intratool-kontaktdaten-vorlage.csvwith one header row. Provided request values replace the matching default column names.
Example Request
Example Response
Parse CSV
Parse an uploaded contacts CSV file into proposed create, update, and delete operations.
Definition
POST /api/contacts/csv
Request Keys
contact_data_csv*
file
-
CSV or plain-text file with a header row.
update_contacts
boolean
false
Include matching contacts in update_contacts.
delete_contacts
boolean
false
Include contacts whose names are absent from the file in delete_contacts.
name
string
name
Header mapped to the name CSV column.
phone
string
phone
Header mapped to the phone CSV column.
fax
string
fax
Header mapped to the fax CSV column.
email
string
email
Header mapped to the email CSV column.
street
string
street
Header mapped to the street CSV column.
zipcode
string
zipcode
Header mapped to the zipcode CSV column.
city
string
city
Header mapped to the city CSV column.
notes
string
notes
Header mapped to the notes CSV column.
contact_person_name
string
contact_person_name
Header mapped to the contact_person_name CSV column.
contact_person_position
string
contact_person_position
Header mapped to the contact_person_position CSV column.
contact_person_phone
string
contact_person_phone
Header mapped to the contact_person_phone CSV column.
contact_person_mobile_phone
string
contact_person_mobile_phone
Header mapped to the contact_person_mobile_phone CSV column.
contact_person_email
string
contact_person_email
Header mapped to the contact_person_email CSV column.
Keys with * are required.
Behavior
The endpoint detects the delimiter and source encoding. Rows without a mapped
nameare ignored.A
contact_listvalue resolves by exact list name. Existing contacts match bynameand, when resolved,contact_list_id.The response is a preview and does not persist any create, update, or delete operation.
With
delete_contacts=true, deletion candidates are selected across all contact lists by contact name only, not just the lists represented in the file.The example assumes
ContactListID1is namedProfessional Networkand contains Ada Lovelace as Contact ID1and Grace Hopper as Contact ID2, with no other contacts present.
Example Request
Example Response
Last updated