pub struct GetGroupsIdMembersQuery {Show 14 fields
pub limit: Option<i64>,
pub role_ids: Option<Vec<i64>>,
pub person_id: Option<Vec<i64>>,
pub group_member_statuses: Option<Vec<String>>,
pub allowed_chat_users_only: Option<bool>,
pub allowed_chat_writers_only: Option<bool>,
pub query: Option<String>,
pub comment: Option<String>,
pub member_start_date_after: Option<Value>,
pub member_start_date_before: Option<Value>,
pub order_fields: Option<Vec<String>>,
pub order_directions: Option<Vec<String>>,
pub person_fields: Option<Vec<String>>,
pub include: Option<Vec<String>>,
}Expand description
Query parameters for GET /groups/{groupId}/members.
Fields§
§limit: Option<i64>Maximum number of memberships per page.
role_ids: Option<Vec<i64>>Filter by role definition IDs (Role.id from GET /roles), matching groupTypeRoleId on memberships. Multiple IDs match any of the selected roles.
person_id: Option<Vec<i64>>Filter by person IDs. These are the IDs in person.domainIdentifier, not membership record IDs.
group_member_statuses: Option<Vec<String>>Filter by membership status, independently of the member’s role. Multiple values match any selected status. Omit this filter to include all visible statuses.
Allowed values: active, requested, to_delete, waiting.
allowed_chat_users_only: Option<bool>If true, return only group members, that are allowed to chat in this group
allowed_chat_writers_only: Option<bool>If true, return only group members that are allowed to write in the chat.
query: Option<String>Search the first and last names of the persons belonging to the group.
comment: Option<String>Return memberships whose comment contains the supplied text.
member_start_date_after: Option<Value>Filter by a membership start date strictly after this value. Memberships without a start date do not match. Use YYYY-MM-DD; UTC timestamps are also accepted for compatibility.
member_start_date_before: Option<Value>Filter by a membership start date strictly before this value. Memberships without a start date do not match. Use YYYY-MM-DD; UTC timestamps are also accepted for compatibility.
order_fields: Option<Vec<String>>Fields used to sort the member list. Use person_ for person fields and member_ for membership properties or custom member fields. For example: person_lastName or member_groupTypeRoleId. Without this parameter, results are ordered by role type, role sort key, last name, first name and person ID.
order_directions: Option<Vec<String>>Sort directions corresponding by position to orderFields. Supply one direction per sort field. Built-in fields default to ASC when their direction is omitted.
Allowed values: ASC, DESC.
person_fields: Option<Vec<String>>Additional person-field keys to include in each member’s personFields object, for example firstName. Person-field permissions apply; membership-specific fields are returned separately in fields.
include: Option<Vec<String>>Additional member-list data. newsletter and tags add properties to each member; aggregations adds meta.aggregations.fields with numeric group member field aggregates over all filtered members, across all pages.
Allowed values: aggregations, newsletter, tags.