ContactLists
Introduction
ContactLists group Contacts. Assignments to Departments and Users restrict which lists appear in list results.
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 Types
contact-lists- Filters lists byname.contacts- Filters the includedcontactsrelation by contact data without removing top-level lists.
Order Directions
asc- Sorts values in ascending order.desc- Sorts values in descending order.
Uppercase ASC and DESC are also accepted.
List
List visible ContactLists.
Definition
GET /api/contact-lists
Request Keys
selects
string
All fields
Comma-separated fields to return.
search_text
string
-
Text used by the selected search behavior.
limit
integer
No limit
Maximum number of lists. Minimum 1.
order_field
string
name
Field used for ordering.
Behavior
Users with
contact-lists-administration-rightsreceive every non-deleted list except lists created by the reserved intratool Admin account.Other users receive lists they created themselves. For other lists, each configured department and user restriction must match; an unconfigured restriction does not limit visibility.
search_type=contactsaffects the includedcontactsrelation only. Include that relation to receive the matching contacts.
Example Request
Example Response
Show
Show one ContactList.
Definition
GET /api/contact-lists/{id}
Route Parameters
id
integer
Contact list ID.
Request Keys
selects
string
All fields
Comma-separated fields to return.
Behavior
The endpoint resolves the ID independently of the department and user assignment filters applied by List.
Example Request
Example Response
Create
Create a new ContactList.
Definition
POST /api/contact-lists
Request Keys
name*
string
-
Unique list name.
sort_number
integer
End of list
Requested list position.
department_ids
string | null
null
Comma-separated department IDs that may receive the list.
user_ids
string | null
null
Comma-separated user IDs that may receive the list.
Keys with * are required.
Behavior
Requires
contact-lists-create-contact-listsorcontact-lists-administration-rights.The authenticated user is stored as
user_id.sort_numberis normalized into the existing sequence. Omission appends the list.Department and user IDs are attached after creation. Empty assignment values are normalized to no assignments.
Example Request
Example Response
Update
Update an existing ContactList.
Definition
PUT /api/contact-lists/{id}
Route Parameters
id
integer
Contact list ID.
Request Keys
name
string
Unique list name.
sort_number
integer
Requested list position.
department_ids
string | null
Comma-separated department IDs; an empty value clears assignments.
user_ids
string | null
Comma-separated user IDs; an empty value clears assignments.
Behavior
Requires
contact-lists-edit-all-contact-lists, or ownership together withcontact-lists-edit-own-contact-lists. Administration rights satisfy either check.Changing
sort_numberreorders the remaining lists.Omitted assignment keys preserve their current values; provided values replace the complete affected assignment set.
Example Request
Example Response
Delete
Delete an existing ContactList.
Definition
DELETE /api/contact-lists/{id}
Route Parameters
id
integer
Contact list ID.
Behavior
Requires
contact-lists-delete-all-contact-lists, or ownership together withcontact-lists-delete-own-contact-lists. Administration rights satisfy either check.The list and all contained contacts are soft-deleted. Remaining lists are reordered.
Example Request
Example Response
Last updated