@emilgroup/insurance-sdk-node 1.66.1-beta.1 → 1.66.1-beta.2

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 (35) hide show
  1. package/.openapi-generator/FILES +1 -0
  2. package/README.md +2 -2
  3. package/dist/models/calculate-custom-premium-request-dto.d.ts +2 -2
  4. package/dist/models/create-booking-funnel-request-dto.d.ts +14 -14
  5. package/dist/models/create-lead-request-dto.d.ts +34 -34
  6. package/dist/models/create-product-field-request-dto.d.ts +41 -41
  7. package/dist/models/get-draft-policy-request-dto.d.ts +2 -2
  8. package/dist/models/grpc-clone-lead-account-request-dto.d.ts +25 -25
  9. package/dist/models/grpc-update-lead-request-dto.d.ts +35 -35
  10. package/dist/models/index.d.ts +1 -0
  11. package/dist/models/index.js +1 -0
  12. package/dist/models/patch-booking-funnel-request-dto.d.ts +17 -17
  13. package/dist/models/patch-lead-request-dto.d.ts +3 -3
  14. package/dist/models/policy-object-dto.d.ts +5 -5
  15. package/dist/models/shared-create-lead-policy-request-dto.d.ts +56 -0
  16. package/dist/models/shared-create-lead-policy-request-dto.js +15 -0
  17. package/dist/models/shared-lead-policy-object-dto.d.ts +5 -5
  18. package/dist/models/update-booking-funnel-request-dto.d.ts +17 -17
  19. package/dist/models/update-policy-request-dto.d.ts +7 -7
  20. package/models/calculate-custom-premium-request-dto.ts +2 -2
  21. package/models/create-booking-funnel-request-dto.ts +14 -14
  22. package/models/create-lead-request-dto.ts +34 -34
  23. package/models/create-product-field-request-dto.ts +41 -41
  24. package/models/get-draft-policy-request-dto.ts +2 -2
  25. package/models/grpc-clone-lead-account-request-dto.ts +25 -25
  26. package/models/grpc-update-lead-request-dto.ts +35 -35
  27. package/models/index.ts +1 -0
  28. package/models/patch-booking-funnel-request-dto.ts +17 -17
  29. package/models/patch-lead-request-dto.ts +3 -3
  30. package/models/policy-object-dto.ts +5 -5
  31. package/models/shared-create-lead-policy-request-dto.ts +62 -0
  32. package/models/shared-lead-policy-object-dto.ts +5 -5
  33. package/models/update-booking-funnel-request-dto.ts +17 -17
  34. package/models/update-policy-request-dto.ts +7 -7
  35. package/package.json +1 -1
@@ -213,6 +213,7 @@ models/product-field-type-class.ts
213
213
  models/product-version-class.ts
214
214
  models/rest-clone-lead-account-request-dto.ts
215
215
  models/sepa-dto.ts
216
+ models/shared-create-lead-policy-request-dto.ts
216
217
  models/shared-invoice-class.ts
217
218
  models/shared-lead-policy-object-dto.ts
218
219
  models/shared-product-field-class.ts
package/README.md CHANGED
@@ -17,11 +17,11 @@ Although this package can be used in both TypeScript and JavaScript, it is inten
17
17
  Navigate to the folder of your consuming project and run one of the following commands:
18
18
 
19
19
  ```
20
- npm install @emilgroup/insurance-sdk-node@1.66.1-beta.1 --save
20
+ npm install @emilgroup/insurance-sdk-node@1.66.1-beta.2 --save
21
21
  ```
22
22
  or
23
23
  ```
24
- yarn add @emilgroup/insurance-sdk-node@1.66.1-beta.1
24
+ yarn add @emilgroup/insurance-sdk-node@1.66.1-beta.2
25
25
  ```
26
26
 
27
27
  And then you can import `PoliciesApi`.
@@ -16,13 +16,13 @@
16
16
  */
17
17
  export interface CalculateCustomPremiumRequestDto {
18
18
  /**
19
- *
19
+ * Custom premium data.
20
20
  * @type {object}
21
21
  * @memberof CalculateCustomPremiumRequestDto
22
22
  */
23
23
  'data': object;
24
24
  /**
25
- *
25
+ * Custom provider name.
26
26
  * @type {string}
27
27
  * @memberof CalculateCustomPremiumRequestDto
28
28
  */
@@ -16,55 +16,55 @@
16
16
  */
17
17
  export interface CreateBookingFunnelRequestDto {
18
18
  /**
19
- *
20
- * @type {object}
21
- * @memberof CreateBookingFunnelRequestDto
22
- */
23
- 'stepsConfig'?: object;
24
- /**
25
- *
19
+ * Unique identifier for the object.
26
20
  * @type {string}
27
21
  * @memberof CreateBookingFunnelRequestDto
28
22
  */
29
23
  'code'?: string;
30
24
  /**
31
- *
25
+ * Parent Booking funnel ID
32
26
  * @type {number}
33
27
  * @memberof CreateBookingFunnelRequestDto
34
28
  */
35
29
  'parentId'?: number;
36
30
  /**
37
- *
31
+ * Booking funnel name
38
32
  * @type {string}
39
33
  * @memberof CreateBookingFunnelRequestDto
40
34
  */
41
35
  'name': string;
42
36
  /**
43
- *
37
+ * Code snippet to load the booking funnel.
44
38
  * @type {string}
45
39
  * @memberof CreateBookingFunnelRequestDto
46
40
  */
47
41
  'jsCode': string;
48
42
  /**
49
- *
43
+ * Steps configuration for the booking funnel.
44
+ * @type {object}
45
+ * @memberof CreateBookingFunnelRequestDto
46
+ */
47
+ 'stepsConfig'?: object;
48
+ /**
49
+ * Custom css for the booking funnel.
50
50
  * @type {string}
51
51
  * @memberof CreateBookingFunnelRequestDto
52
52
  */
53
53
  'css'?: string;
54
54
  /**
55
- *
55
+ * URL to fetch the logo for the booking funnel.
56
56
  * @type {string}
57
57
  * @memberof CreateBookingFunnelRequestDto
58
58
  */
59
59
  'logoPath'?: string;
60
60
  /**
61
- *
61
+ * A slug is a human-readable, unique identifier, used to identify a resource instead of a less human-readable identifier like an id.
62
62
  * @type {string}
63
63
  * @memberof CreateBookingFunnelRequestDto
64
64
  */
65
65
  'productSlug': string;
66
66
  /**
67
- *
67
+ * Product version id. Will default to the latest version if not specified.
68
68
  * @type {number}
69
69
  * @memberof CreateBookingFunnelRequestDto
70
70
  */
@@ -11,10 +11,10 @@
11
11
  */
12
12
  import { CreateAccountRequestDto } from './create-account-request-dto';
13
13
  import { CreateBankAccountRequestDto } from './create-bank-account-request-dto';
14
- import { CreateLeadPolicyRequestDto } from './create-lead-policy-request-dto';
15
14
  import { CreatePaymentMethodRequestDto } from './create-payment-method-request-dto';
16
15
  import { LinkLeadPartnerRequestDto } from './link-lead-partner-request-dto';
17
16
  import { PremiumOverrideRequestDto } from './premium-override-request-dto';
17
+ import { SharedCreateLeadPolicyRequestDto } from './shared-create-lead-policy-request-dto';
18
18
  import { UploadedDocumentDto } from './uploaded-document-dto';
19
19
  /**
20
20
  *
@@ -23,81 +23,81 @@ import { UploadedDocumentDto } from './uploaded-document-dto';
23
23
  */
24
24
  export interface CreateLeadRequestDto {
25
25
  /**
26
- *
26
+ * The lead code is used in cases where the lead has been initiated before the lead creation.
27
27
  * @type {string}
28
28
  * @memberof CreateLeadRequestDto
29
29
  */
30
- 'accountCode': string;
31
- /**
32
- *
33
- * @type {CreateAccountRequestDto}
34
- * @memberof CreateLeadRequestDto
35
- */
36
- 'account': CreateAccountRequestDto;
30
+ 'code'?: string;
37
31
  /**
38
- *
39
- * @type {CreateLeadPolicyRequestDto}
32
+ * The product version id of the product version to be used for the lead. The product version id will be validated if the \'validate\' flag is set to true.
33
+ * @type {number}
40
34
  * @memberof CreateLeadRequestDto
41
35
  */
42
- 'policy': CreateLeadPolicyRequestDto;
36
+ 'productVersionId'?: number;
43
37
  /**
44
- *
45
- * @type {object}
38
+ * 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.
39
+ * @type {string}
46
40
  * @memberof CreateLeadRequestDto
47
41
  */
48
- 'customData'?: object;
42
+ 'accountCode'?: string;
49
43
  /**
50
- *
51
- * @type {LinkLeadPartnerRequestDto}
44
+ * Account object. The create lead request should either contain accountCode or account. The account content will be validated if the \'validate\' flag is set to true. an empty object is required if \'validate flag is set to false.
45
+ * @type {CreateAccountRequestDto}
52
46
  * @memberof CreateLeadRequestDto
53
47
  */
54
- 'partner'?: LinkLeadPartnerRequestDto;
48
+ 'account': CreateAccountRequestDto;
55
49
  /**
56
- *
57
- * @type {string}
50
+ * The policy object contains necessary information to create a policy. The Policy content will be validated if the \'validate\' flag is set to true
51
+ * @type {SharedCreateLeadPolicyRequestDto}
58
52
  * @memberof CreateLeadRequestDto
59
53
  */
60
- 'code'?: string;
54
+ 'policy': SharedCreateLeadPolicyRequestDto;
61
55
  /**
62
- *
63
- * @type {number}
56
+ * 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.
57
+ * @type {CreateBankAccountRequestDto}
64
58
  * @memberof CreateLeadRequestDto
65
59
  */
66
- 'productVersionId'?: number;
60
+ 'bankAccount'?: CreateBankAccountRequestDto;
67
61
  /**
68
- *
69
- * @type {CreateBankAccountRequestDto}
62
+ * 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
63
+ * @type {object}
70
64
  * @memberof CreateLeadRequestDto
71
65
  */
72
- 'bankAccount'?: CreateBankAccountRequestDto;
66
+ 'customData'?: object;
73
67
  /**
74
- *
68
+ * 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.
75
69
  * @type {UploadedDocumentDto}
76
70
  * @memberof CreateLeadRequestDto
77
71
  */
78
72
  'uploadedDocument'?: UploadedDocumentDto;
79
73
  /**
80
- *
74
+ * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
81
75
  * @type {string}
82
76
  * @memberof CreateLeadRequestDto
83
77
  */
84
78
  'status'?: string;
85
79
  /**
86
- *
87
- * @type {PremiumOverrideRequestDto}
80
+ * 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.
81
+ * @type {Array<PremiumOverrideRequestDto>}
88
82
  * @memberof CreateLeadRequestDto
89
83
  */
90
- 'premiumOverride'?: PremiumOverrideRequestDto;
84
+ 'premiumOverride'?: Array<PremiumOverrideRequestDto>;
91
85
  /**
92
- *
86
+ * Payment method, used to for payment method support, such as SEPA, invoice, etc. The payment method content will be validated if the \'validate\' flag is set to true.
93
87
  * @type {CreatePaymentMethodRequestDto}
94
88
  * @memberof CreateLeadRequestDto
95
89
  */
96
90
  'paymentMethod'?: CreatePaymentMethodRequestDto;
97
91
  /**
98
- *
92
+ * 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.
99
93
  * @type {boolean}
100
94
  * @memberof CreateLeadRequestDto
101
95
  */
102
96
  'validate'?: boolean;
97
+ /**
98
+ * Optional partner object contains necessary information to link a partner to the policy. The partner content will be validated if the \'validate\' flag is set to true.
99
+ * @type {LinkLeadPartnerRequestDto}
100
+ * @memberof CreateLeadRequestDto
101
+ */
102
+ 'partner'?: LinkLeadPartnerRequestDto;
103
103
  }
@@ -16,131 +16,131 @@
16
16
  */
17
17
  export interface CreateProductFieldRequestDto {
18
18
  /**
19
- *
20
- * @type {object}
21
- * @memberof CreateProductFieldRequestDto
22
- */
23
- 'defaultValue': object;
24
- /**
25
- *
26
- * @type {object}
27
- * @memberof CreateProductFieldRequestDto
28
- */
29
- 'minValue'?: object;
30
- /**
31
- *
32
- * @type {object}
33
- * @memberof CreateProductFieldRequestDto
34
- */
35
- 'maxValue'?: object;
36
- /**
37
- *
38
- * @type {object}
39
- * @memberof CreateProductFieldRequestDto
40
- */
41
- 'metadata'?: object;
42
- /**
43
- *
19
+ * Product field name
44
20
  * @type {string}
45
21
  * @memberof CreateProductFieldRequestDto
46
22
  */
47
23
  'name': string;
48
24
  /**
49
- *
25
+ * Product field label
50
26
  * @type {string}
51
27
  * @memberof CreateProductFieldRequestDto
52
28
  */
53
29
  'label': string;
54
30
  /**
55
- *
31
+ * Product field type entity
56
32
  * @type {string}
57
33
  * @memberof CreateProductFieldRequestDto
58
34
  */
59
35
  'typeEntity': CreateProductFieldRequestDtoTypeEntityEnum;
60
36
  /**
61
- *
37
+ * Product field type id
62
38
  * @type {number}
63
39
  * @memberof CreateProductFieldRequestDto
64
40
  */
65
41
  'typeId': number;
66
42
  /**
67
- *
43
+ * Insured object id
68
44
  * @type {number}
69
45
  * @memberof CreateProductFieldRequestDto
70
46
  */
71
47
  'insuredObjectId': number;
72
48
  /**
73
- *
49
+ * Product field group
74
50
  * @type {string}
75
51
  * @memberof CreateProductFieldRequestDto
76
52
  */
77
53
  'group': string;
78
54
  /**
79
- *
55
+ * Is field required?
80
56
  * @type {boolean}
81
57
  * @memberof CreateProductFieldRequestDto
82
58
  */
83
59
  'isRequired': boolean;
84
60
  /**
85
- *
61
+ * Is field hidden on the booking funnel?
86
62
  * @type {boolean}
87
63
  * @memberof CreateProductFieldRequestDto
88
64
  */
89
65
  'isHidden': boolean;
90
66
  /**
91
- *
67
+ * Should the field value be unique across policies?
92
68
  * @type {boolean}
93
69
  * @memberof CreateProductFieldRequestDto
94
70
  */
95
71
  'isUnique': boolean;
96
72
  /**
97
- *
73
+ * Should the field be hidden on customer portal?
98
74
  * @type {boolean}
99
75
  * @memberof CreateProductFieldRequestDto
100
76
  */
101
77
  'isHiddenCustomerPortal': boolean;
102
78
  /**
103
- *
79
+ * Should the field be editable on customer portal?
104
80
  * @type {boolean}
105
81
  * @memberof CreateProductFieldRequestDto
106
82
  */
107
83
  'isEditableCustomerPortal': boolean;
108
84
  /**
109
- *
85
+ * Default value of the field. For the field type date-time, it should be { \"templated\" : \"{{today}}\" }
86
+ * @type {object}
87
+ * @memberof CreateProductFieldRequestDto
88
+ */
89
+ 'defaultValue': object;
90
+ /**
91
+ * Default value of the field. For the field type date-time, it should be { \"templated\" : \"{{today}}\" }
92
+ * @type {object}
93
+ * @memberof CreateProductFieldRequestDto
94
+ */
95
+ 'minValue'?: object;
96
+ /**
97
+ * Booking funnel description
110
98
  * @type {string}
111
99
  * @memberof CreateProductFieldRequestDto
112
100
  */
113
101
  'bfDescription'?: string;
114
102
  /**
115
- *
103
+ * Booking funnel tooltip
116
104
  * @type {string}
117
105
  * @memberof CreateProductFieldRequestDto
118
106
  */
119
107
  'bfTooltip'?: string;
120
108
  /**
121
- *
109
+ * Booking funnel label
122
110
  * @type {string}
123
111
  * @memberof CreateProductFieldRequestDto
124
112
  */
125
113
  'bfLabel'?: string;
126
114
  /**
127
- *
115
+ * Expression to calculate the field.
128
116
  * @type {string}
129
117
  * @memberof CreateProductFieldRequestDto
130
118
  */
131
119
  'expression'?: string;
132
120
  /**
133
- *
121
+ * Default value of the field. For the field type date-time, it should be { \"templated\" : \"{{today}}\" }
122
+ * @type {object}
123
+ * @memberof CreateProductFieldRequestDto
124
+ */
125
+ 'maxValue'?: object;
126
+ /**
127
+ * Order index for the product field item, used to define the order of the items in the insured object. The order will also impact the order of the items in the policy itself.
134
128
  * @type {number}
135
129
  * @memberof CreateProductFieldRequestDto
136
130
  */
137
131
  'order'?: number;
138
132
  /**
139
- *
133
+ * order index for the product field for display on the booking funnel, not defined for hidden fields.
140
134
  * @type {number}
141
135
  * @memberof CreateProductFieldRequestDto
142
136
  */
143
137
  'legacyBfOrder'?: number;
138
+ /**
139
+ * Product field metadata object. The field may contain special data specific to the product.
140
+ * @type {object}
141
+ * @memberof CreateProductFieldRequestDto
142
+ */
143
+ 'metadata'?: object;
144
144
  }
145
145
  export declare const CreateProductFieldRequestDtoTypeEntityEnum: {
146
146
  readonly SystemProductFieldType: "system_product_field_type";
@@ -16,13 +16,13 @@
16
16
  */
17
17
  export interface GetDraftPolicyRequestDto {
18
18
  /**
19
- *
19
+ * Unique identifier of the Draft Policy that this object belongs to.
20
20
  * @type {string}
21
21
  * @memberof GetDraftPolicyRequestDto
22
22
  */
23
23
  'policyCode': string;
24
24
  /**
25
- *
25
+ * Fields to expand response by.
26
26
  * @type {string}
27
27
  * @memberof GetDraftPolicyRequestDto
28
28
  */
@@ -16,95 +16,95 @@
16
16
  */
17
17
  export interface GrpcCloneLeadAccountRequestDto {
18
18
  /**
19
- *
20
- * @type {string}
21
- * @memberof GrpcCloneLeadAccountRequestDto
22
- */
23
- 'birthDate'?: string;
24
- /**
25
- *
26
- * @type {object}
27
- * @memberof GrpcCloneLeadAccountRequestDto
28
- */
29
- 'customFields'?: object;
30
- /**
31
- *
19
+ * Optional field to enter the honorific title you want to be called.
32
20
  * @type {string}
33
21
  * @memberof GrpcCloneLeadAccountRequestDto
34
22
  */
35
23
  'title'?: GrpcCloneLeadAccountRequestDtoTitleEnum;
36
24
  /**
37
- *
25
+ * The account\'s holder first name. The account\'s first name will be validated if the \'validate\' flag is set to true.
38
26
  * @type {string}
39
27
  * @memberof GrpcCloneLeadAccountRequestDto
40
28
  */
41
29
  'firstName'?: string;
42
30
  /**
43
- *
31
+ * The account\'s holder first name. The account\'s first name will be validated if the \'validate\' flag is set to true.
44
32
  * @type {string}
45
33
  * @memberof GrpcCloneLeadAccountRequestDto
46
34
  */
47
35
  'lastName'?: string;
48
36
  /**
49
- *
37
+ * The account\'s holder email address. It is displayed alongside the account in your dashboard and can be useful for searching and tracking. The account\'s email address will be validated if the \'validate\' flag is set to true.
50
38
  * @type {string}
51
39
  * @memberof GrpcCloneLeadAccountRequestDto
52
40
  */
53
41
  'email'?: string;
54
42
  /**
55
- *
43
+ * The account\'s holder gender. The account\'s gender will be validated if the \'validate\' flag is set to true.
56
44
  * @type {string}
57
45
  * @memberof GrpcCloneLeadAccountRequestDto
58
46
  */
59
47
  'gender'?: string;
60
48
  /**
61
- *
49
+ * The account\'s holder street name. The account\'s street name will be validated if the \'validate\' flag is set to true.
62
50
  * @type {string}
63
51
  * @memberof GrpcCloneLeadAccountRequestDto
64
52
  */
65
53
  'street'?: string;
66
54
  /**
67
- *
55
+ * The account\'s holder ZIP or postal code. The account\'s ZIP or postal code will be validated if the \'validate\' flag is set to true.
68
56
  * @type {string}
69
57
  * @memberof GrpcCloneLeadAccountRequestDto
70
58
  */
71
59
  'zipCode'?: string;
72
60
  /**
73
- *
61
+ * The account\'s holder city, district, suburb, town, or village. The account\'s city will be validated if the \'validate\' flag is set to true.
74
62
  * @type {string}
75
63
  * @memberof GrpcCloneLeadAccountRequestDto
76
64
  */
77
65
  'city'?: string;
78
66
  /**
79
- *
67
+ * The account\'s holder house number. The account\'s house number will be validated if the \'validate\' flag is set to true.
80
68
  * @type {string}
81
69
  * @memberof GrpcCloneLeadAccountRequestDto
82
70
  */
83
71
  'houseNumber'?: string;
84
72
  /**
85
- *
73
+ * The account\'s holder date of birth (Required for account of type person). The account\'s date of birth will be validated if the \'validate\' flag is set to true.
74
+ * @type {string}
75
+ * @memberof GrpcCloneLeadAccountRequestDto
76
+ */
77
+ 'birthDate'?: string;
78
+ /**
79
+ * The account\'s holder phone number. The account\'s phone number will be validated if the \'validate\' flag is set to true.
86
80
  * @type {string}
87
81
  * @memberof GrpcCloneLeadAccountRequestDto
88
82
  */
89
83
  'phone'?: string;
90
84
  /**
91
- *
85
+ * The account\'s type. Default value is person
92
86
  * @type {string}
93
87
  * @memberof GrpcCloneLeadAccountRequestDto
94
88
  */
95
89
  'type'?: GrpcCloneLeadAccountRequestDtoTypeEnum;
96
90
  /**
97
- *
91
+ * The account\'s company name (Required for account of type org). The account\'s company name will be validated if the \'validate\' flag is set to true.
98
92
  * @type {string}
99
93
  * @memberof GrpcCloneLeadAccountRequestDto
100
94
  */
101
95
  'companyName'?: string;
102
96
  /**
103
- *
97
+ * Account number.
104
98
  * @type {string}
105
99
  * @memberof GrpcCloneLeadAccountRequestDto
106
100
  */
107
101
  'accountNumber'?: string;
102
+ /**
103
+ * Optional custom fields for account. It could be included additional required/optional fields that the account would need for specific cases.
104
+ * @type {object}
105
+ * @memberof GrpcCloneLeadAccountRequestDto
106
+ */
107
+ 'customFields'?: object;
108
108
  }
109
109
  export declare const GrpcCloneLeadAccountRequestDtoTitleEnum: {
110
110
  readonly Empty: "";
@@ -23,87 +23,87 @@ import { UploadedDocumentDto } from './uploaded-document-dto';
23
23
  */
24
24
  export interface GrpcUpdateLeadRequestDto {
25
25
  /**
26
- *
27
- * @type {string}
26
+ * The product version id of the product version to be used for the lead. The product version id will be validated if the \'validate\' flag is set to true.
27
+ * @type {number}
28
28
  * @memberof GrpcUpdateLeadRequestDto
29
29
  */
30
- 'code': string;
30
+ 'productVersionId'?: number;
31
31
  /**
32
- *
32
+ * Account object. The create lead request should either contain accountCode or account. The account content will be validated if the \'validate\' flag is set to true. an empty object is required if \'validate flag is set to false.
33
33
  * @type {CreateAccountRequestDto}
34
34
  * @memberof GrpcUpdateLeadRequestDto
35
35
  */
36
36
  'account': CreateAccountRequestDto;
37
37
  /**
38
- *
38
+ * The policy object contains necessary information to create a policy. The Policy content will be validated if the \'validate\' flag is set to true
39
39
  * @type {CreateLeadPolicyRequestDto}
40
40
  * @memberof GrpcUpdateLeadRequestDto
41
41
  */
42
42
  'policy': CreateLeadPolicyRequestDto;
43
43
  /**
44
- *
45
- * @type {object}
44
+ * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
45
+ * @type {string}
46
46
  * @memberof GrpcUpdateLeadRequestDto
47
47
  */
48
- 'customData'?: object;
48
+ 'status': string;
49
49
  /**
50
- *
51
- * @type {boolean}
50
+ * 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.
51
+ * @type {CreateBankAccountRequestDto}
52
52
  * @memberof GrpcUpdateLeadRequestDto
53
53
  */
54
- 'shouldTriggerWorkflow'?: boolean;
54
+ 'bankAccount'?: CreateBankAccountRequestDto;
55
55
  /**
56
- *
57
- * @type {LinkLeadPartnerRequestDto}
56
+ * 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
57
+ * @type {object}
58
58
  * @memberof GrpcUpdateLeadRequestDto
59
59
  */
60
- 'partner'?: LinkLeadPartnerRequestDto;
60
+ 'customData'?: object;
61
61
  /**
62
- *
63
- * @type {number}
62
+ * 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.
63
+ * @type {UploadedDocumentDto}
64
64
  * @memberof GrpcUpdateLeadRequestDto
65
65
  */
66
- 'productVersionId'?: number;
66
+ 'uploadedDocument'?: UploadedDocumentDto;
67
67
  /**
68
- *
69
- * @type {string}
68
+ * 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.
69
+ * @type {Array<PremiumOverrideRequestDto>}
70
70
  * @memberof GrpcUpdateLeadRequestDto
71
71
  */
72
- 'status': string;
72
+ 'premiumOverride'?: Array<PremiumOverrideRequestDto>;
73
73
  /**
74
- *
75
- * @type {CreateBankAccountRequestDto}
74
+ * 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.
75
+ * @type {string}
76
76
  * @memberof GrpcUpdateLeadRequestDto
77
77
  */
78
- 'bankAccount'?: CreateBankAccountRequestDto;
78
+ 'accountCode'?: string;
79
79
  /**
80
- *
81
- * @type {UploadedDocumentDto}
80
+ * Payment method, used to for payment method support, such as SEPA, invoice, etc. The payment method content will be validated if the \'validate\' flag is set to true.
81
+ * @type {CreatePaymentMethodRequestDto}
82
82
  * @memberof GrpcUpdateLeadRequestDto
83
83
  */
84
- 'uploadedDocument'?: UploadedDocumentDto;
84
+ 'paymentMethod'?: CreatePaymentMethodRequestDto;
85
85
  /**
86
- *
87
- * @type {PremiumOverrideRequestDto}
86
+ * 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.
87
+ * @type {boolean}
88
88
  * @memberof GrpcUpdateLeadRequestDto
89
89
  */
90
- 'premiumOverride'?: PremiumOverrideRequestDto;
90
+ 'validate'?: boolean;
91
91
  /**
92
- *
93
- * @type {string}
92
+ * Optional partner object contains necessary information to link a partner to the policy. The partner content will be validated if the \'validate\' flag is set to true.
93
+ * @type {LinkLeadPartnerRequestDto}
94
94
  * @memberof GrpcUpdateLeadRequestDto
95
95
  */
96
- 'accountCode'?: string;
96
+ 'partner'?: LinkLeadPartnerRequestDto;
97
97
  /**
98
98
  *
99
- * @type {CreatePaymentMethodRequestDto}
99
+ * @type {string}
100
100
  * @memberof GrpcUpdateLeadRequestDto
101
101
  */
102
- 'paymentMethod'?: CreatePaymentMethodRequestDto;
102
+ 'code': string;
103
103
  /**
104
104
  *
105
105
  * @type {boolean}
106
106
  * @memberof GrpcUpdateLeadRequestDto
107
107
  */
108
- 'validate'?: boolean;
108
+ 'shouldTriggerWorkflow'?: boolean;
109
109
  }