document_templates library
The v4 document templates family: its endpoints, bound class, path templates and views.
Import it with a prefix, import 'package:exsited/document_templates.dart' as document_templates;,
because families declare the same top-level names and a Dart export can
neither rename nor prefix them.
Classes
- DocumentTemplatesResource
- The document templates endpoints with client already applied.
- DocumentTemplatesUrls
- SettingsDocumentTemplate
-
The settings document template body, under
document_template. - SettingsDocumentTemplateList
-
One page of
SettingsDocumentTemplaterecords, underdata.
Functions
-
createSettingsDocumentTemplate(
ExsitedClient client, Object payload, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< SettingsDocumentTemplate> > -
POST /api/{api_version}/settings/document_templates -
deleteSettingsDocumentTemplate(
ExsitedClient client, Object documentTemplateId, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< Object?> > -
DELETE /api/{api_version}/settings/document_templates/{document_template_id} -
getSettingsDocumentTemplate(
ExsitedClient client, Object documentTemplateId, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< SettingsDocumentTemplate> > -
GET /api/{api_version}/settings/document_templates/{document_template_id} -
getSettingsDocumentTemplates(
ExsitedClient client, {Map< String, Object?> ? queryParams, bool? raiseOnError, String? responseFormat}) → Future<ApiResponse< SettingsDocumentTemplateList> > -
GET /api/{api_version}/settings/document_templates -
updateSettingsDocumentTemplate(
ExsitedClient client, Object documentTemplateId, Object payload, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< SettingsDocumentTemplate> > -
PATCH /api/{api_version}/settings/document_templates/{document_template_id}