communication_profiles library
The v4 communication profiles family: its endpoints, bound class, path templates and views.
Import it with a prefix, import 'package:exsited/communication_profiles.dart' as communication_profiles;,
because families declare the same top-level names and a Dart export can
neither rename nor prefix them.
Classes
- CommunicationProfilesResource
- The communication profiles endpoints with client already applied.
- CommunicationProfilesUrls
- SettingsCommunicationProfile
-
The settings communication profile body, under
communication_profile. - SettingsCommunicationProfileList
-
One page of
SettingsCommunicationProfilerecords, underdata.
Functions
-
createSettingsCommunicationProfile(
ExsitedClient client, Object payload, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< Object?> > -
POST /api/{api_version}/settings/communication_profiles -
deleteSettingsCommunicationProfile(
ExsitedClient client, Object communicationProfileId, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< Object?> > -
DELETE /api/{api_version}/settings/communication_profiles/{communication_profile_id} -
getSettingsCommunicationProfile(
ExsitedClient client, Object communicationProfileId, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< SettingsCommunicationProfile> > -
GET /api/{api_version}/settings/communication_profiles/{communication_profile_id} -
getSettingsCommunicationProfiles(
ExsitedClient client, {Map< String, Object?> ? queryParams, bool? raiseOnError, String? responseFormat}) → Future<ApiResponse< SettingsCommunicationProfileList> > -
GET /api/{api_version}/settings/communication_profiles -
updateSettingsCommunicationProfile(
ExsitedClient client, Object communicationProfileId, Object payload, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< Object?> > -
PATCH /api/{api_version}/settings/communication_profiles/{communication_profile_id}