@emilgroup/insurance-sdk-node 1.24.0 → 1.24.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (56) hide show
  1. package/.openapi-generator/FILES +0 -3
  2. package/README.md +2 -2
  3. package/api/leads-api.ts +0 -105
  4. package/api/premium-formulas-api.ts +0 -107
  5. package/api/products-api.ts +4 -122
  6. package/dist/api/leads-api.d.ts +0 -56
  7. package/dist/api/leads-api.js +0 -93
  8. package/dist/api/premium-formulas-api.d.ts +0 -57
  9. package/dist/api/premium-formulas-api.js +0 -93
  10. package/dist/api/products-api.d.ts +4 -68
  11. package/dist/api/products-api.js +3 -103
  12. package/dist/models/create-lead-policy-request-dto.d.ts +1 -1
  13. package/dist/models/create-lead-request-dto.d.ts +7 -7
  14. package/dist/models/create-premium-formula-request-dto.d.ts +0 -12
  15. package/dist/models/get-product-request-dto.d.ts +4 -10
  16. package/dist/models/grpc-patch-lead-request-dto.d.ts +1 -1
  17. package/dist/models/grpc-update-lead-request-dto.d.ts +7 -7
  18. package/dist/models/index.d.ts +0 -3
  19. package/dist/models/index.js +0 -3
  20. package/dist/models/list-leads-response-class.d.ts +0 -12
  21. package/dist/models/list-policies-response-class.d.ts +0 -12
  22. package/dist/models/patch-lead-request-dto.d.ts +1 -1
  23. package/dist/models/policy-object-dto.d.ts +1 -1
  24. package/dist/models/premium-formula-class.d.ts +0 -12
  25. package/dist/models/shared-create-lead-policy-request-dto.d.ts +1 -1
  26. package/dist/models/shared-lead-policy-object-dto.d.ts +1 -1
  27. package/dist/models/shared-update-premium-formula-request-dto.d.ts +0 -12
  28. package/dist/models/update-lead-request-dto.d.ts +7 -7
  29. package/dist/models/update-premium-formula-request-dto.d.ts +0 -12
  30. package/models/create-lead-policy-request-dto.ts +1 -1
  31. package/models/create-lead-request-dto.ts +7 -7
  32. package/models/create-premium-formula-request-dto.ts +0 -12
  33. package/models/get-product-request-dto.ts +4 -10
  34. package/models/grpc-patch-lead-request-dto.ts +1 -1
  35. package/models/grpc-update-lead-request-dto.ts +7 -7
  36. package/models/index.ts +0 -3
  37. package/models/list-leads-response-class.ts +0 -12
  38. package/models/list-policies-response-class.ts +0 -12
  39. package/models/patch-lead-request-dto.ts +1 -1
  40. package/models/policy-object-dto.ts +1 -1
  41. package/models/premium-formula-class.ts +0 -12
  42. package/models/shared-create-lead-policy-request-dto.ts +1 -1
  43. package/models/shared-lead-policy-object-dto.ts +1 -1
  44. package/models/shared-update-premium-formula-request-dto.ts +0 -12
  45. package/models/update-lead-request-dto.ts +7 -7
  46. package/models/update-premium-formula-request-dto.ts +0 -12
  47. package/package.json +1 -1
  48. package/dist/models/create-lead-sync-response-class.d.ts +0 -24
  49. package/dist/models/create-lead-sync-response-class.js +0 -15
  50. package/dist/models/empty-response-class.d.ts +0 -24
  51. package/dist/models/empty-response-class.js +0 -15
  52. package/dist/models/swap-premium-formulas-order-requestt-dto.d.ts +0 -30
  53. package/dist/models/swap-premium-formulas-order-requestt-dto.js +0 -15
  54. package/models/create-lead-sync-response-class.ts +0 -30
  55. package/models/empty-response-class.ts +0 -30
  56. package/models/swap-premium-formulas-order-requestt-dto.ts +0 -36
@@ -34,7 +34,7 @@ export interface CreateLeadRequestDto {
34
34
  */
35
35
  'productVersionId'?: number;
36
36
  /**
37
- * The account code is used in cases where the account has been created before the lead. The create lead request should include either the \'accountCode\' or \'account\'. The account code will be validated if the \'validate\' flag is set to true.
37
+ * The account code is used in cases where the account has been created before the lead. The create lead request should include either the \'accountCode\' or \'account\'. The account code will be validated if the \'validate\' flag is set to true.
38
38
  * @type {string}
39
39
  * @memberof CreateLeadRequestDto
40
40
  */
@@ -52,31 +52,31 @@ export interface CreateLeadRequestDto {
52
52
  */
53
53
  'policy': SharedCreateLeadPolicyRequestDto;
54
54
  /**
55
- * Bank account details, to be used for direct debit payments, the created bank account will be attached to the lead for later use, such as paying claims. The bank account content will be validated if the \'validate\' flag is set to true.
55
+ * Bank account details, to be used for direct debit payments, the created bank account will be attached to the lead for later use, such as paying claims. The bank account content will be validated if the \'validate\' flag is set to true.
56
56
  * @type {CreateBankAccountRequestDto}
57
57
  * @memberof CreateLeadRequestDto
58
58
  */
59
59
  'bankAccount'?: CreateBankAccountRequestDto;
60
60
  /**
61
- * Optional custom data for the lead. This field is useful for edge cases where the lead requires additional data for the risk carrier, such as creating an application in the risk carrier platform or performing a premium calculation. The custom data should include three main entities: \'data\', \'provider\', and \'productCode\'. The \'data\' entity contains information used in the risk carrier platform, the \'provider\' field contains the name of the provider (usually the risk carrier\'s name), the provider must be supported in EMIL, The \'productCode\' field contains the product code in EMIL
61
+ * Optional custom data for the lead. This field is useful for edge cases where the lead requires additional data for the risk carrier, such as creating an application in the risk carrier platform or performing a premium calculation. The custom data should include three main entities: \'data\', \'provider\', and \'productCode\'. The \'data\' entity contains information used in the risk carrier platform, the \'provider\' field contains the name of the provider (usually the risk carrier\'s name), the provider must be supported in EMIL, The \'productCode\' field contains the product code in EMIL
62
62
  * @type {object}
63
63
  * @memberof CreateLeadRequestDto
64
64
  */
65
65
  'customData'?: object;
66
66
  /**
67
- * Used to pass pre-uploaded documents to the lead. By providing the codes of the uploaded documents, they will be attached to the lead. The uploaded document content will be validated if the \'validate\' flag is set to true.
67
+ * Used to pass pre-uploaded documents to the lead. By providing the codes of the uploaded documents, they will be attached to the lead. The uploaded document content will be validated if the \'validate\' flag is set to true.
68
68
  * @type {UploadedDocumentDto}
69
69
  * @memberof CreateLeadRequestDto
70
70
  */
71
71
  'uploadedDocument'?: UploadedDocumentDto;
72
72
  /**
73
- * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
73
+ * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
74
74
  * @type {string}
75
75
  * @memberof CreateLeadRequestDto
76
76
  */
77
77
  'status'?: string;
78
78
  /**
79
- * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
79
+ * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
80
80
  * @type {Array<PremiumOverrideRequestDto>}
81
81
  * @memberof CreateLeadRequestDto
82
82
  */
@@ -88,7 +88,7 @@ export interface CreateLeadRequestDto {
88
88
  */
89
89
  'paymentMethod'?: CreatePaymentMethodRequestDto;
90
90
  /**
91
- * The validation indicator, with a default value of true, serves as a toggle. When set to false, it allows the bypassing of validation—a useful option for saving leads for later processing. This feature provides flexibility by enabling users to choose whether to enforce validation checks during the current stage or defer them for a subsequent time.
91
+ * The validation indicator, with a default value of true, serves as a toggle. When set to false, it allows the bypassing of validation—a useful option for saving leads for later processing. This feature provides flexibility by enabling users to choose whether to enforce validation checks during the current stage or defer them for a subsequent time.
92
92
  * @type {boolean}
93
93
  * @memberof CreateLeadRequestDto
94
94
  */
@@ -63,18 +63,6 @@ export interface CreatePremiumFormulaRequestDto {
63
63
  * @memberof CreatePremiumFormulaRequestDto
64
64
  */
65
65
  'visibility'?: CreatePremiumFormulaRequestDtoVisibilityEnum;
66
- /**
67
- * Name of the variable this Premium item value is referenced by in the other items formulas.
68
- * @type {string}
69
- * @memberof CreatePremiumFormulaRequestDto
70
- */
71
- 'variableName'?: string;
72
- /**
73
- * order index for the Premium item, used to define the order the items are calculated in.
74
- * @type {number}
75
- * @memberof CreatePremiumFormulaRequestDto
76
- */
77
- 'order': number;
78
66
  }
79
67
  export declare const CreatePremiumFormulaRequestDtoTypeEnum: {
80
68
  readonly Time: "time";
@@ -16,23 +16,17 @@
16
16
  */
17
17
  export interface GetProductRequestDto {
18
18
  /**
19
- * Unique identifier referencing the product.
19
+ * Product id
20
20
  * @type {number}
21
21
  * @memberof GetProductRequestDto
22
22
  */
23
23
  'id': number;
24
24
  /**
25
- * Unique identifier of the product that this object belongs to.
26
- * @type {object}
27
- * @memberof GetProductRequestDto
28
- */
29
- 'code': object;
30
- /**
31
- * A slug is a human-readable, unique identifier, used to identify a resource instead of a less human-readable identifier like an id.
32
- * @type {object}
25
+ * Product code
26
+ * @type {string}
33
27
  * @memberof GetProductRequestDto
34
28
  */
35
- 'slug': object;
29
+ 'code': string;
36
30
  /**
37
31
  * Fields to expand response by
38
32
  * @type {string}
@@ -40,7 +40,7 @@ export interface GrpcPatchLeadRequestDto {
40
40
  */
41
41
  'policy'?: CreateLeadPolicyRequestDto;
42
42
  /**
43
- * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
43
+ * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
44
44
  * @type {string}
45
45
  * @memberof GrpcPatchLeadRequestDto
46
46
  */
@@ -40,37 +40,37 @@ export interface GrpcUpdateLeadRequestDto {
40
40
  */
41
41
  'policy': CreateLeadPolicyRequestDto;
42
42
  /**
43
- * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
43
+ * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
44
44
  * @type {string}
45
45
  * @memberof GrpcUpdateLeadRequestDto
46
46
  */
47
47
  'status': string;
48
48
  /**
49
- * Bank account details, to be used for direct debit payments, the created bank account will be attached to the lead for later use, such as paying claims. The bank account content will be validated if the \'validate\' flag is set to true.
49
+ * Bank account details, to be used for direct debit payments, the created bank account will be attached to the lead for later use, such as paying claims. The bank account content will be validated if the \'validate\' flag is set to true.
50
50
  * @type {CreateBankAccountRequestDto}
51
51
  * @memberof GrpcUpdateLeadRequestDto
52
52
  */
53
53
  'bankAccount'?: CreateBankAccountRequestDto;
54
54
  /**
55
- * Optional custom data for the lead. This field is useful for edge cases where the lead requires additional data for the risk carrier, such as creating an application in the risk carrier platform or performing a premium calculation. The custom data should include three main entities: \'data\', \'provider\', and \'productCode\'. The \'data\' entity contains information used in the risk carrier platform, the \'provider\' field contains the name of the provider (usually the risk carrier\'s name), the provider must be supported in EMIL, The \'productCode\' field contains the product code in EMIL
55
+ * Optional custom data for the lead. This field is useful for edge cases where the lead requires additional data for the risk carrier, such as creating an application in the risk carrier platform or performing a premium calculation. The custom data should include three main entities: \'data\', \'provider\', and \'productCode\'. The \'data\' entity contains information used in the risk carrier platform, the \'provider\' field contains the name of the provider (usually the risk carrier\'s name), the provider must be supported in EMIL, The \'productCode\' field contains the product code in EMIL
56
56
  * @type {object}
57
57
  * @memberof GrpcUpdateLeadRequestDto
58
58
  */
59
59
  'customData'?: object;
60
60
  /**
61
- * Used to pass pre-uploaded documents to the lead. By providing the codes of the uploaded documents, they will be attached to the lead. The uploaded document content will be validated if the \'validate\' flag is set to true.
61
+ * Used to pass pre-uploaded documents to the lead. By providing the codes of the uploaded documents, they will be attached to the lead. The uploaded document content will be validated if the \'validate\' flag is set to true.
62
62
  * @type {UploadedDocumentDto}
63
63
  * @memberof GrpcUpdateLeadRequestDto
64
64
  */
65
65
  'uploadedDocument'?: UploadedDocumentDto;
66
66
  /**
67
- * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
67
+ * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
68
68
  * @type {Array<PremiumOverrideRequestDto>}
69
69
  * @memberof GrpcUpdateLeadRequestDto
70
70
  */
71
71
  'premiumOverride'?: Array<PremiumOverrideRequestDto>;
72
72
  /**
73
- * The account code is used in cases where the account has been created before the lead. The create lead request should include either the \'accountCode\' or \'account\'. The account code will be validated if the \'validate\' flag is set to true.
73
+ * The account code is used in cases where the account has been created before the lead. The create lead request should include either the \'accountCode\' or \'account\'. The account code will be validated if the \'validate\' flag is set to true.
74
74
  * @type {string}
75
75
  * @memberof GrpcUpdateLeadRequestDto
76
76
  */
@@ -82,7 +82,7 @@ export interface GrpcUpdateLeadRequestDto {
82
82
  */
83
83
  'paymentMethod'?: CreatePaymentMethodRequestDto;
84
84
  /**
85
- * The validation indicator, with a default value of true, serves as a toggle. When set to false, it allows the bypassing of validation—a useful option for saving leads for later processing. This feature provides flexibility by enabling users to choose whether to enforce validation checks during the current stage or defer them for a subsequent time.
85
+ * The validation indicator, with a default value of true, serves as a toggle. When set to false, it allows the bypassing of validation—a useful option for saving leads for later processing. This feature provides flexibility by enabling users to choose whether to enforce validation checks during the current stage or defer them for a subsequent time.
86
86
  * @type {boolean}
87
87
  * @memberof GrpcUpdateLeadRequestDto
88
88
  */
@@ -12,7 +12,6 @@ export * from './create-lead-request-dto';
12
12
  export * from './create-lead-response-class';
13
13
  export * from './create-lead-status-request-dto';
14
14
  export * from './create-lead-status-response-class';
15
- export * from './create-lead-sync-response-class';
16
15
  export * from './create-named-range-request-dto';
17
16
  export * from './create-named-range-response-class';
18
17
  export * from './create-named-request-s3-data-class';
@@ -28,7 +27,6 @@ export * from './create-product-response-class';
28
27
  export * from './csv-product-factor-dto';
29
28
  export * from './delete-request-dto';
30
29
  export * from './delete-response-class';
31
- export * from './empty-response-class';
32
30
  export * from './get-insured-object-response-class';
33
31
  export * from './get-lead-response-class';
34
32
  export * from './get-lead-status-response-class';
@@ -105,7 +103,6 @@ export * from './store-product-factors-request-dto';
105
103
  export * from './store-product-factors-response-class';
106
104
  export * from './suspend-policy-request-dto';
107
105
  export * from './suspend-policy-response-class';
108
- export * from './swap-premium-formulas-order-requestt-dto';
109
106
  export * from './terminate-policy-request-dto';
110
107
  export * from './terminate-policy-response-class';
111
108
  export * from './timeslice-class';
@@ -28,7 +28,6 @@ __exportStar(require("./create-lead-request-dto"), exports);
28
28
  __exportStar(require("./create-lead-response-class"), exports);
29
29
  __exportStar(require("./create-lead-status-request-dto"), exports);
30
30
  __exportStar(require("./create-lead-status-response-class"), exports);
31
- __exportStar(require("./create-lead-sync-response-class"), exports);
32
31
  __exportStar(require("./create-named-range-request-dto"), exports);
33
32
  __exportStar(require("./create-named-range-response-class"), exports);
34
33
  __exportStar(require("./create-named-request-s3-data-class"), exports);
@@ -44,7 +43,6 @@ __exportStar(require("./create-product-response-class"), exports);
44
43
  __exportStar(require("./csv-product-factor-dto"), exports);
45
44
  __exportStar(require("./delete-request-dto"), exports);
46
45
  __exportStar(require("./delete-response-class"), exports);
47
- __exportStar(require("./empty-response-class"), exports);
48
46
  __exportStar(require("./get-insured-object-response-class"), exports);
49
47
  __exportStar(require("./get-lead-response-class"), exports);
50
48
  __exportStar(require("./get-lead-status-response-class"), exports);
@@ -121,7 +119,6 @@ __exportStar(require("./store-product-factors-request-dto"), exports);
121
119
  __exportStar(require("./store-product-factors-response-class"), exports);
122
120
  __exportStar(require("./suspend-policy-request-dto"), exports);
123
121
  __exportStar(require("./suspend-policy-response-class"), exports);
124
- __exportStar(require("./swap-premium-formulas-order-requestt-dto"), exports);
125
122
  __exportStar(require("./terminate-policy-request-dto"), exports);
126
123
  __exportStar(require("./terminate-policy-response-class"), exports);
127
124
  __exportStar(require("./timeslice-class"), exports);
@@ -28,16 +28,4 @@ export interface ListLeadsResponseClass {
28
28
  * @memberof ListLeadsResponseClass
29
29
  */
30
30
  'nextPageToken': string;
31
- /**
32
- * Items per page.
33
- * @type {number}
34
- * @memberof ListLeadsResponseClass
35
- */
36
- 'itemsPerPage': number;
37
- /**
38
- * Total amount of items.
39
- * @type {number}
40
- * @memberof ListLeadsResponseClass
41
- */
42
- 'totalItems': number;
43
31
  }
@@ -28,16 +28,4 @@ export interface ListPoliciesResponseClass {
28
28
  * @memberof ListPoliciesResponseClass
29
29
  */
30
30
  'nextPageToken': string;
31
- /**
32
- * Items per page.
33
- * @type {number}
34
- * @memberof ListPoliciesResponseClass
35
- */
36
- 'itemsPerPage': number;
37
- /**
38
- * Total amount of items.
39
- * @type {number}
40
- * @memberof ListPoliciesResponseClass
41
- */
42
- 'totalItems': number;
43
31
  }
@@ -40,7 +40,7 @@ export interface PatchLeadRequestDto {
40
40
  */
41
41
  'policy'?: CreateLeadPolicyRequestDto;
42
42
  /**
43
- * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
43
+ * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
44
44
  * @type {string}
45
45
  * @memberof PatchLeadRequestDto
46
46
  */
@@ -22,7 +22,7 @@ export interface PolicyObjectDto {
22
22
  */
23
23
  'insuredObjectId'?: number;
24
24
  /**
25
- * Insured object name. Human readable identifier of insured object. Can be used instead of insuredObjectId
25
+ * Insured object name. Human readable identifier of insured object. Can be used instead of insuredObjectId
26
26
  * @type {string}
27
27
  * @memberof PolicyObjectDto
28
28
  */
@@ -69,18 +69,6 @@ export interface PremiumFormulaClass {
69
69
  * @memberof PremiumFormulaClass
70
70
  */
71
71
  'visibility'?: string;
72
- /**
73
- * Name of the variable this Premium item value is referenced by in the other items formulas.
74
- * @type {string}
75
- * @memberof PremiumFormulaClass
76
- */
77
- 'variableName'?: string;
78
- /**
79
- * order index for the Premium item, used to define the order the items are calculated in.
80
- * @type {number}
81
- * @memberof PremiumFormulaClass
82
- */
83
- 'order': number;
84
72
  /**
85
73
  * Time at which the object was created.
86
74
  * @type {string}
@@ -42,7 +42,7 @@ export interface SharedCreateLeadPolicyRequestDto {
42
42
  */
43
43
  'policyObjects'?: Array<SharedLeadPolicyObjectDto>;
44
44
  /**
45
- * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
45
+ * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
46
46
  * @type {PremiumOverrideRequestDto}
47
47
  * @memberof SharedCreateLeadPolicyRequestDto
48
48
  */
@@ -22,7 +22,7 @@ export interface SharedLeadPolicyObjectDto {
22
22
  */
23
23
  'insuredObjectId'?: number;
24
24
  /**
25
- * Insured object name. Human readable identifier of insured object. Can be used instead of insuredObjectId
25
+ * Insured object name. Human readable identifier of insured object. Can be used instead of insuredObjectId
26
26
  * @type {string}
27
27
  * @memberof SharedLeadPolicyObjectDto
28
28
  */
@@ -63,18 +63,6 @@ export interface SharedUpdatePremiumFormulaRequestDto {
63
63
  * @memberof SharedUpdatePremiumFormulaRequestDto
64
64
  */
65
65
  'visibility'?: SharedUpdatePremiumFormulaRequestDtoVisibilityEnum;
66
- /**
67
- * Name of the variable this Premium item value is referenced by in the other items formulas.
68
- * @type {string}
69
- * @memberof SharedUpdatePremiumFormulaRequestDto
70
- */
71
- 'variableName'?: string;
72
- /**
73
- * order index for the Premium item, used to define the order the items are calculated in.
74
- * @type {number}
75
- * @memberof SharedUpdatePremiumFormulaRequestDto
76
- */
77
- 'order': number;
78
66
  /**
79
67
  * Internal unique identifier for the object. You should not have to use this, use code instead.
80
68
  * @type {number}
@@ -40,37 +40,37 @@ export interface UpdateLeadRequestDto {
40
40
  */
41
41
  'policy': CreateLeadPolicyRequestDto;
42
42
  /**
43
- * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
43
+ * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
44
44
  * @type {string}
45
45
  * @memberof UpdateLeadRequestDto
46
46
  */
47
47
  'status': string;
48
48
  /**
49
- * Bank account details, to be used for direct debit payments, the created bank account will be attached to the lead for later use, such as paying claims. The bank account content will be validated if the \'validate\' flag is set to true.
49
+ * Bank account details, to be used for direct debit payments, the created bank account will be attached to the lead for later use, such as paying claims. The bank account content will be validated if the \'validate\' flag is set to true.
50
50
  * @type {CreateBankAccountRequestDto}
51
51
  * @memberof UpdateLeadRequestDto
52
52
  */
53
53
  'bankAccount'?: CreateBankAccountRequestDto;
54
54
  /**
55
- * Optional custom data for the lead. This field is useful for edge cases where the lead requires additional data for the risk carrier, such as creating an application in the risk carrier platform or performing a premium calculation. The custom data should include three main entities: \'data\', \'provider\', and \'productCode\'. The \'data\' entity contains information used in the risk carrier platform, the \'provider\' field contains the name of the provider (usually the risk carrier\'s name), the provider must be supported in EMIL, The \'productCode\' field contains the product code in EMIL
55
+ * Optional custom data for the lead. This field is useful for edge cases where the lead requires additional data for the risk carrier, such as creating an application in the risk carrier platform or performing a premium calculation. The custom data should include three main entities: \'data\', \'provider\', and \'productCode\'. The \'data\' entity contains information used in the risk carrier platform, the \'provider\' field contains the name of the provider (usually the risk carrier\'s name), the provider must be supported in EMIL, The \'productCode\' field contains the product code in EMIL
56
56
  * @type {object}
57
57
  * @memberof UpdateLeadRequestDto
58
58
  */
59
59
  'customData'?: object;
60
60
  /**
61
- * Used to pass pre-uploaded documents to the lead. By providing the codes of the uploaded documents, they will be attached to the lead. The uploaded document content will be validated if the \'validate\' flag is set to true.
61
+ * Used to pass pre-uploaded documents to the lead. By providing the codes of the uploaded documents, they will be attached to the lead. The uploaded document content will be validated if the \'validate\' flag is set to true.
62
62
  * @type {UploadedDocumentDto}
63
63
  * @memberof UpdateLeadRequestDto
64
64
  */
65
65
  'uploadedDocument'?: UploadedDocumentDto;
66
66
  /**
67
- * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
67
+ * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
68
68
  * @type {Array<PremiumOverrideRequestDto>}
69
69
  * @memberof UpdateLeadRequestDto
70
70
  */
71
71
  'premiumOverride'?: Array<PremiumOverrideRequestDto>;
72
72
  /**
73
- * The account code is used in cases where the account has been created before the lead. The create lead request should include either the \'accountCode\' or \'account\'. The account code will be validated if the \'validate\' flag is set to true.
73
+ * The account code is used in cases where the account has been created before the lead. The create lead request should include either the \'accountCode\' or \'account\'. The account code will be validated if the \'validate\' flag is set to true.
74
74
  * @type {string}
75
75
  * @memberof UpdateLeadRequestDto
76
76
  */
@@ -82,7 +82,7 @@ export interface UpdateLeadRequestDto {
82
82
  */
83
83
  'paymentMethod'?: CreatePaymentMethodRequestDto;
84
84
  /**
85
- * The validation indicator, with a default value of true, serves as a toggle. When set to false, it allows the bypassing of validation—a useful option for saving leads for later processing. This feature provides flexibility by enabling users to choose whether to enforce validation checks during the current stage or defer them for a subsequent time.
85
+ * The validation indicator, with a default value of true, serves as a toggle. When set to false, it allows the bypassing of validation—a useful option for saving leads for later processing. This feature provides flexibility by enabling users to choose whether to enforce validation checks during the current stage or defer them for a subsequent time.
86
86
  * @type {boolean}
87
87
  * @memberof UpdateLeadRequestDto
88
88
  */
@@ -63,18 +63,6 @@ export interface UpdatePremiumFormulaRequestDto {
63
63
  * @memberof UpdatePremiumFormulaRequestDto
64
64
  */
65
65
  'visibility'?: UpdatePremiumFormulaRequestDtoVisibilityEnum;
66
- /**
67
- * Name of the variable this Premium item value is referenced by in the other items formulas.
68
- * @type {string}
69
- * @memberof UpdatePremiumFormulaRequestDto
70
- */
71
- 'variableName'?: string;
72
- /**
73
- * order index for the Premium item, used to define the order the items are calculated in.
74
- * @type {number}
75
- * @memberof UpdatePremiumFormulaRequestDto
76
- */
77
- 'order': number;
78
66
  }
79
67
  export declare const UpdatePremiumFormulaRequestDtoTypeEnum: {
80
68
  readonly Time: "time";
@@ -47,7 +47,7 @@ export interface CreateLeadPolicyRequestDto {
47
47
  */
48
48
  'policyObjects'?: Array<SharedLeadPolicyObjectDto>;
49
49
  /**
50
- * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
50
+ * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
51
51
  * @type {PremiumOverrideRequestDto}
52
52
  * @memberof CreateLeadPolicyRequestDto
53
53
  */
@@ -39,7 +39,7 @@ export interface CreateLeadRequestDto {
39
39
  */
40
40
  'productVersionId'?: number;
41
41
  /**
42
- * The account code is used in cases where the account has been created before the lead. The create lead request should include either the \'accountCode\' or \'account\'. The account code will be validated if the \'validate\' flag is set to true.
42
+ * The account code is used in cases where the account has been created before the lead. The create lead request should include either the \'accountCode\' or \'account\'. The account code will be validated if the \'validate\' flag is set to true.
43
43
  * @type {string}
44
44
  * @memberof CreateLeadRequestDto
45
45
  */
@@ -57,31 +57,31 @@ export interface CreateLeadRequestDto {
57
57
  */
58
58
  'policy': SharedCreateLeadPolicyRequestDto;
59
59
  /**
60
- * Bank account details, to be used for direct debit payments, the created bank account will be attached to the lead for later use, such as paying claims. The bank account content will be validated if the \'validate\' flag is set to true.
60
+ * Bank account details, to be used for direct debit payments, the created bank account will be attached to the lead for later use, such as paying claims. The bank account content will be validated if the \'validate\' flag is set to true.
61
61
  * @type {CreateBankAccountRequestDto}
62
62
  * @memberof CreateLeadRequestDto
63
63
  */
64
64
  'bankAccount'?: CreateBankAccountRequestDto;
65
65
  /**
66
- * Optional custom data for the lead. This field is useful for edge cases where the lead requires additional data for the risk carrier, such as creating an application in the risk carrier platform or performing a premium calculation. The custom data should include three main entities: \'data\', \'provider\', and \'productCode\'. The \'data\' entity contains information used in the risk carrier platform, the \'provider\' field contains the name of the provider (usually the risk carrier\'s name), the provider must be supported in EMIL, The \'productCode\' field contains the product code in EMIL
66
+ * Optional custom data for the lead. This field is useful for edge cases where the lead requires additional data for the risk carrier, such as creating an application in the risk carrier platform or performing a premium calculation. The custom data should include three main entities: \'data\', \'provider\', and \'productCode\'. The \'data\' entity contains information used in the risk carrier platform, the \'provider\' field contains the name of the provider (usually the risk carrier\'s name), the provider must be supported in EMIL, The \'productCode\' field contains the product code in EMIL
67
67
  * @type {object}
68
68
  * @memberof CreateLeadRequestDto
69
69
  */
70
70
  'customData'?: object;
71
71
  /**
72
- * Used to pass pre-uploaded documents to the lead. By providing the codes of the uploaded documents, they will be attached to the lead. The uploaded document content will be validated if the \'validate\' flag is set to true.
72
+ * Used to pass pre-uploaded documents to the lead. By providing the codes of the uploaded documents, they will be attached to the lead. The uploaded document content will be validated if the \'validate\' flag is set to true.
73
73
  * @type {UploadedDocumentDto}
74
74
  * @memberof CreateLeadRequestDto
75
75
  */
76
76
  'uploadedDocument'?: UploadedDocumentDto;
77
77
  /**
78
- * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
78
+ * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
79
79
  * @type {string}
80
80
  * @memberof CreateLeadRequestDto
81
81
  */
82
82
  'status'?: string;
83
83
  /**
84
- * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
84
+ * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
85
85
  * @type {Array<PremiumOverrideRequestDto>}
86
86
  * @memberof CreateLeadRequestDto
87
87
  */
@@ -93,7 +93,7 @@ export interface CreateLeadRequestDto {
93
93
  */
94
94
  'paymentMethod'?: CreatePaymentMethodRequestDto;
95
95
  /**
96
- * The validation indicator, with a default value of true, serves as a toggle. When set to false, it allows the bypassing of validation—a useful option for saving leads for later processing. This feature provides flexibility by enabling users to choose whether to enforce validation checks during the current stage or defer them for a subsequent time.
96
+ * The validation indicator, with a default value of true, serves as a toggle. When set to false, it allows the bypassing of validation—a useful option for saving leads for later processing. This feature provides flexibility by enabling users to choose whether to enforce validation checks during the current stage or defer them for a subsequent time.
97
97
  * @type {boolean}
98
98
  * @memberof CreateLeadRequestDto
99
99
  */
@@ -68,18 +68,6 @@ export interface CreatePremiumFormulaRequestDto {
68
68
  * @memberof CreatePremiumFormulaRequestDto
69
69
  */
70
70
  'visibility'?: CreatePremiumFormulaRequestDtoVisibilityEnum;
71
- /**
72
- * Name of the variable this Premium item value is referenced by in the other items formulas.
73
- * @type {string}
74
- * @memberof CreatePremiumFormulaRequestDto
75
- */
76
- 'variableName'?: string;
77
- /**
78
- * order index for the Premium item, used to define the order the items are calculated in.
79
- * @type {number}
80
- * @memberof CreatePremiumFormulaRequestDto
81
- */
82
- 'order': number;
83
71
  }
84
72
 
85
73
  export const CreatePremiumFormulaRequestDtoTypeEnum = {
@@ -21,23 +21,17 @@
21
21
  */
22
22
  export interface GetProductRequestDto {
23
23
  /**
24
- * Unique identifier referencing the product.
24
+ * Product id
25
25
  * @type {number}
26
26
  * @memberof GetProductRequestDto
27
27
  */
28
28
  'id': number;
29
29
  /**
30
- * Unique identifier of the product that this object belongs to.
31
- * @type {object}
32
- * @memberof GetProductRequestDto
33
- */
34
- 'code': object;
35
- /**
36
- * A slug is a human-readable, unique identifier, used to identify a resource instead of a less human-readable identifier like an id.
37
- * @type {object}
30
+ * Product code
31
+ * @type {string}
38
32
  * @memberof GetProductRequestDto
39
33
  */
40
- 'slug': object;
34
+ 'code': string;
41
35
  /**
42
36
  * Fields to expand response by
43
37
  * @type {string}
@@ -45,7 +45,7 @@ export interface GrpcPatchLeadRequestDto {
45
45
  */
46
46
  'policy'?: CreateLeadPolicyRequestDto;
47
47
  /**
48
- * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
48
+ * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
49
49
  * @type {string}
50
50
  * @memberof GrpcPatchLeadRequestDto
51
51
  */
@@ -45,37 +45,37 @@ export interface GrpcUpdateLeadRequestDto {
45
45
  */
46
46
  'policy': CreateLeadPolicyRequestDto;
47
47
  /**
48
- * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
48
+ * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
49
49
  * @type {string}
50
50
  * @memberof GrpcUpdateLeadRequestDto
51
51
  */
52
52
  'status': string;
53
53
  /**
54
- * Bank account details, to be used for direct debit payments, the created bank account will be attached to the lead for later use, such as paying claims. The bank account content will be validated if the \'validate\' flag is set to true.
54
+ * Bank account details, to be used for direct debit payments, the created bank account will be attached to the lead for later use, such as paying claims. The bank account content will be validated if the \'validate\' flag is set to true.
55
55
  * @type {CreateBankAccountRequestDto}
56
56
  * @memberof GrpcUpdateLeadRequestDto
57
57
  */
58
58
  'bankAccount'?: CreateBankAccountRequestDto;
59
59
  /**
60
- * Optional custom data for the lead. This field is useful for edge cases where the lead requires additional data for the risk carrier, such as creating an application in the risk carrier platform or performing a premium calculation. The custom data should include three main entities: \'data\', \'provider\', and \'productCode\'. The \'data\' entity contains information used in the risk carrier platform, the \'provider\' field contains the name of the provider (usually the risk carrier\'s name), the provider must be supported in EMIL, The \'productCode\' field contains the product code in EMIL
60
+ * Optional custom data for the lead. This field is useful for edge cases where the lead requires additional data for the risk carrier, such as creating an application in the risk carrier platform or performing a premium calculation. The custom data should include three main entities: \'data\', \'provider\', and \'productCode\'. The \'data\' entity contains information used in the risk carrier platform, the \'provider\' field contains the name of the provider (usually the risk carrier\'s name), the provider must be supported in EMIL, The \'productCode\' field contains the product code in EMIL
61
61
  * @type {object}
62
62
  * @memberof GrpcUpdateLeadRequestDto
63
63
  */
64
64
  'customData'?: object;
65
65
  /**
66
- * Used to pass pre-uploaded documents to the lead. By providing the codes of the uploaded documents, they will be attached to the lead. The uploaded document content will be validated if the \'validate\' flag is set to true.
66
+ * Used to pass pre-uploaded documents to the lead. By providing the codes of the uploaded documents, they will be attached to the lead. The uploaded document content will be validated if the \'validate\' flag is set to true.
67
67
  * @type {UploadedDocumentDto}
68
68
  * @memberof GrpcUpdateLeadRequestDto
69
69
  */
70
70
  'uploadedDocument'?: UploadedDocumentDto;
71
71
  /**
72
- * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
72
+ * Premium Override is utilized to override the premium calculation. The premium formulas will be disregarded when this object is present. The premium override content will be validated if the \'validate\' flag is set to true.
73
73
  * @type {Array<PremiumOverrideRequestDto>}
74
74
  * @memberof GrpcUpdateLeadRequestDto
75
75
  */
76
76
  'premiumOverride'?: Array<PremiumOverrideRequestDto>;
77
77
  /**
78
- * The account code is used in cases where the account has been created before the lead. The create lead request should include either the \'accountCode\' or \'account\'. The account code will be validated if the \'validate\' flag is set to true.
78
+ * The account code is used in cases where the account has been created before the lead. The create lead request should include either the \'accountCode\' or \'account\'. The account code will be validated if the \'validate\' flag is set to true.
79
79
  * @type {string}
80
80
  * @memberof GrpcUpdateLeadRequestDto
81
81
  */
@@ -87,7 +87,7 @@ export interface GrpcUpdateLeadRequestDto {
87
87
  */
88
88
  'paymentMethod'?: CreatePaymentMethodRequestDto;
89
89
  /**
90
- * The validation indicator, with a default value of true, serves as a toggle. When set to false, it allows the bypassing of validation—a useful option for saving leads for later processing. This feature provides flexibility by enabling users to choose whether to enforce validation checks during the current stage or defer them for a subsequent time.
90
+ * The validation indicator, with a default value of true, serves as a toggle. When set to false, it allows the bypassing of validation—a useful option for saving leads for later processing. This feature provides flexibility by enabling users to choose whether to enforce validation checks during the current stage or defer them for a subsequent time.
91
91
  * @type {boolean}
92
92
  * @memberof GrpcUpdateLeadRequestDto
93
93
  */
package/models/index.ts CHANGED
@@ -12,7 +12,6 @@ export * from './create-lead-request-dto';
12
12
  export * from './create-lead-response-class';
13
13
  export * from './create-lead-status-request-dto';
14
14
  export * from './create-lead-status-response-class';
15
- export * from './create-lead-sync-response-class';
16
15
  export * from './create-named-range-request-dto';
17
16
  export * from './create-named-range-response-class';
18
17
  export * from './create-named-request-s3-data-class';
@@ -28,7 +27,6 @@ export * from './create-product-response-class';
28
27
  export * from './csv-product-factor-dto';
29
28
  export * from './delete-request-dto';
30
29
  export * from './delete-response-class';
31
- export * from './empty-response-class';
32
30
  export * from './get-insured-object-response-class';
33
31
  export * from './get-lead-response-class';
34
32
  export * from './get-lead-status-response-class';
@@ -105,7 +103,6 @@ export * from './store-product-factors-request-dto';
105
103
  export * from './store-product-factors-response-class';
106
104
  export * from './suspend-policy-request-dto';
107
105
  export * from './suspend-policy-response-class';
108
- export * from './swap-premium-formulas-order-requestt-dto';
109
106
  export * from './terminate-policy-request-dto';
110
107
  export * from './terminate-policy-response-class';
111
108
  export * from './timeslice-class';