additional_codes library
The v4 additional codes family: its endpoints, bound class, path templates and views.
Import it with a prefix, import 'package:exsited/additional_codes.dart' as additional_codes;,
because families declare the same top-level names and a Dart export can
neither rename nor prefix them.
Classes
- AdditionalCodesResource
- The additional codes endpoints with client already applied.
- AdditionalCodesUrls
- SettingsAdditionalCode
-
The settings additional code body, under
additional_code. - SettingsAdditionalCodeList
-
One page of
SettingsAdditionalCoderecords, underdata.
Functions
-
createSettingsAdditionalCode(
ExsitedClient client, Object payload, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< SettingsAdditionalCode> > -
POST /api/{api_version}/settings/additional_codes -
deleteSettingsAdditionalCode(
ExsitedClient client, Object additionalCodeId, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< Object?> > -
DELETE /api/{api_version}/settings/additional_codes/{additional_code_id} -
getSettingsAdditionalCode(
ExsitedClient client, Object additionalCodeId, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< SettingsAdditionalCode> > -
GET /api/{api_version}/settings/additional_codes/{additional_code_id} -
getSettingsAdditionalCodes(
ExsitedClient client, {Map< String, Object?> ? queryParams, bool? raiseOnError, String? responseFormat}) → Future<ApiResponse< SettingsAdditionalCodeList> > -
GET /api/{api_version}/settings/additional_codes -
updateSettingsAdditionalCode(
ExsitedClient client, Object additionalCodeId, Object payload, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< Object?> > -
PATCH /api/{api_version}/settings/additional_codes/{additional_code_id}