email_templates library
The v4 email templates family: its endpoints, bound class, path templates and views.
Import it with a prefix, import 'package:exsited/email_templates.dart' as email_templates;,
because families declare the same top-level names and a Dart export can
neither rename nor prefix them.
Classes
- EmailTemplatesResource
- The email templates endpoints with client already applied.
- EmailTemplatesUrls
- SettingsEmailTemplate
-
The settings email template body, under
email_template. - SettingsEmailTemplateList
-
One page of
SettingsEmailTemplaterecords, underdata.
Functions
-
createSettingsEmailTemplate(
ExsitedClient client, Object payload, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< SettingsEmailTemplate> > -
POST /api/{api_version}/settings/email_templates -
deleteSettingsEmailTemplate(
ExsitedClient client, Object emailTemplateId, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< Object?> > -
DELETE /api/{api_version}/settings/email_templates/{email_template_id} -
getSettingsEmailTemplate(
ExsitedClient client, Object emailTemplateId, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< SettingsEmailTemplate> > -
GET /api/{api_version}/settings/email_templates/{email_template_id} -
getSettingsEmailTemplates(
ExsitedClient client, {Map< String, Object?> ? queryParams, bool? raiseOnError, String? responseFormat}) → Future<ApiResponse< SettingsEmailTemplateList> > -
GET /api/{api_version}/settings/email_templates -
updateSettingsEmailTemplate(
ExsitedClient client, Object emailTemplateId, Object payload, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< SettingsEmailTemplate> > -
PATCH /api/{api_version}/settings/email_templates/{email_template_id}