@emilgroup/public-api-sdk-node 1.15.0 → 1.16.0

package/models/update-lead-request-dto.ts

@@ -26,13 +26,13 @@ import { UploadedDocumentDto } from './uploaded-document-dto';
  */
 export interface UpdateLeadRequestDto {
     /**
-     * Unique identifier for the object.
+     * The lead code is used in cases where the lead has been initiated before the lead creation.
      * @type {string}
      * @memberof UpdateLeadRequestDto
      */
     'code': string;
     /**
-     * Unique identifier referencing the product version.
+     * 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.
      * @type {number}
      * @memberof UpdateLeadRequestDto
      */
@@ -44,46 +44,52 @@ export interface UpdateLeadRequestDto {
      */
     'productCode': string;
     /**
-     * 
+     * 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.
+     * @type {CreateAccountRequestDto}
+     * @memberof UpdateLeadRequestDto
+     */
+    'account': CreateAccountRequestDto;
+    /**
+     * The policy objects contains necessary information to create a policy.     The Policy objects array will be validated if the \'validate\' flag is set to true
      * @type {Array<PolicyObjectRequestDto>}
      * @memberof UpdateLeadRequestDto
      */
-    'policyObjects': Array<PolicyObjectRequestDto>;
+    'policyObjects'?: Array<PolicyObjectRequestDto>;
     /**
-     * Bank account details
-     * @type {CreateBankAccountRequestDto}
+     * 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.
+     * @type {Array<CreateBankAccountRequestDto>}
      * @memberof UpdateLeadRequestDto
      */
-    'bankAccount'?: CreateBankAccountRequestDto;
+    'bankAccount'?: Array<CreateBankAccountRequestDto>;
     /**
-     * Custom data.
+     * 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
      * @type {object}
      * @memberof UpdateLeadRequestDto
      */
     'customData'?: object;
     /**
-     * Codes for documents to be uploaded.
+     * 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.
      * @type {UploadedDocumentDto}
      * @memberof UpdateLeadRequestDto
      */
     'uploadedDocument'?: UploadedDocumentDto;
     /**
-     * Lead status. Default values are \"created\", \"approved\" and \"declined\". However, those can be extended using /lead-statuses endpoint from insuranceservice.
+     * Lead status. Default values are \"created\", \"approved\" and \"declined\".      However, those can be extended using /lead-statuses endpoint from insuranceservice.
      * @type {string}
      * @memberof UpdateLeadRequestDto
      */
     'status': string;
     /**
-     * Payment Method.
+     * 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.
      * @type {CreatePaymentMethodRequestDto}
      * @memberof UpdateLeadRequestDto
      */
     'paymentMethod'?: CreatePaymentMethodRequestDto;
     /**
-     * 
-     * @type {CreateAccountRequestDto}
+     * 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.
+     * @type {boolean}
      * @memberof UpdateLeadRequestDto
      */
-    'account': CreateAccountRequestDto;
+    'validate'?: boolean;
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@emilgroup/public-api-sdk-node",
-  "version": "1.15.0",
+  "version": "1.16.0",
   "description": "OpenAPI client for @emilgroup/public-api-sdk-node",
   "author": "OpenAPI-Generator Contributors",
   "keywords": [