@emilgroup/public-api-sdk-node 1.41.1-beta.3 → 1.41.1-beta.5

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.
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/public-api-sdk-node@1.41.1-beta.3 --save
20
+ npm install @emilgroup/public-api-sdk-node@1.41.1-beta.5 --save
21
21
  ```
22
22
  or
23
23
  ```
24
- yarn add @emilgroup/public-api-sdk-node@1.41.1-beta.3
24
+ yarn add @emilgroup/public-api-sdk-node@1.41.1-beta.5
25
25
  ```
26
26
 
27
27
  And then you can import `PublicApi`.
package/base.ts CHANGED
@@ -60,6 +60,7 @@ export enum Environment {
60
60
  Staging = 'https://apiv2-staging.emil.de',
61
61
  Development = 'https://apiv2-dev.emil.de',
62
62
  ProductionZurich = 'https://eu-central-2.apiv2.emil.de',
63
+ StagingZurich = 'https://eu-central-2.apiv2-staging.emil.de',
63
64
  }
64
65
 
65
66
  let _retry_count = 0
package/dist/base.d.ts CHANGED
@@ -39,7 +39,8 @@ export declare enum Environment {
39
39
  Test = "https://apiv2-test.emil.de",
40
40
  Staging = "https://apiv2-staging.emil.de",
41
41
  Development = "https://apiv2-dev.emil.de",
42
- ProductionZurich = "https://eu-central-2.apiv2.emil.de"
42
+ ProductionZurich = "https://eu-central-2.apiv2.emil.de",
43
+ StagingZurich = "https://eu-central-2.apiv2-staging.emil.de"
43
44
  }
44
45
  export declare function resetRetry(): void;
45
46
  /**
package/dist/base.js CHANGED
@@ -132,6 +132,7 @@ var Environment;
132
132
  Environment["Staging"] = "https://apiv2-staging.emil.de";
133
133
  Environment["Development"] = "https://apiv2-dev.emil.de";
134
134
  Environment["ProductionZurich"] = "https://eu-central-2.apiv2.emil.de";
135
+ Environment["StagingZurich"] = "https://eu-central-2.apiv2-staging.emil.de";
135
136
  })(Environment = exports.Environment || (exports.Environment = {}));
136
137
  var _retry_count = 0;
137
138
  var _retry = null;
@@ -101,16 +101,20 @@ export interface CreateAccountRequestDto {
101
101
  'accountNumber'?: string;
102
102
  /**
103
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}
104
+ * @type {{ [key: string]: object; }}
105
105
  * @memberof CreateAccountRequestDto
106
106
  */
107
- 'customFields'?: object;
107
+ 'customFields'?: {
108
+ [key: string]: object;
109
+ };
108
110
  /**
109
111
  * Metadata contains extra information that the account would need for specific cases.
110
- * @type {object}
112
+ * @type {{ [key: string]: object; }}
111
113
  * @memberof CreateAccountRequestDto
112
114
  */
113
- 'metadata'?: object;
115
+ 'metadata'?: {
116
+ [key: string]: object;
117
+ };
114
118
  }
115
119
  export declare const CreateAccountRequestDtoTitleEnum: {
116
120
  readonly Empty: "";
@@ -17,10 +17,12 @@
17
17
  export interface CreateCustomApplicationRequestDto {
18
18
  /**
19
19
  * Required data to create a custom application.
20
- * @type {object}
20
+ * @type {{ [key: string]: object; }}
21
21
  * @memberof CreateCustomApplicationRequestDto
22
22
  */
23
- 'data': object;
23
+ 'data': {
24
+ [key: string]: object;
25
+ };
24
26
  /**
25
27
  * Custom provider name.
26
28
  * @type {string}
@@ -29,10 +29,12 @@ export interface CreateDocumentRequestDto {
29
29
  'productSlug'?: string;
30
30
  /**
31
31
  * Document payload.
32
- * @type {object}
32
+ * @type {{ [key: string]: object; }}
33
33
  * @memberof CreateDocumentRequestDto
34
34
  */
35
- 'payload': object;
35
+ 'payload': {
36
+ [key: string]: object;
37
+ };
36
38
  /**
37
39
  * Document entity type.
38
40
  * @type {string}
@@ -71,10 +73,12 @@ export interface CreateDocumentRequestDto {
71
73
  'requester': CreateDocumentRequestDtoRequesterEnum;
72
74
  /**
73
75
  * Metadata contains extra information that the document would need for specific cases.
74
- * @type {object}
76
+ * @type {{ [key: string]: object; }}
75
77
  * @memberof CreateDocumentRequestDto
76
78
  */
77
- 'metadata'?: object;
79
+ 'metadata'?: {
80
+ [key: string]: object;
81
+ };
78
82
  /**
79
83
  * Document type.
80
84
  * @type {string}
@@ -31,10 +31,12 @@ export interface CreateEstimatedInvoiceRequestDto {
31
31
  'policyObjects'?: Array<PolicyObjectRequestDto>;
32
32
  /**
33
33
  * Customer custom data for premium calculation. Necessary when no policyObjects are provided.
34
- * @type {object}
34
+ * @type {{ [key: string]: object; }}
35
35
  * @memberof CreateEstimatedInvoiceRequestDto
36
36
  */
37
- 'data'?: object;
37
+ 'data'?: {
38
+ [key: string]: object;
39
+ };
38
40
  /**
39
41
  * Custom provider name. Necessary if data is provided.
40
42
  * @type {string}
@@ -72,10 +72,12 @@ export interface CreateLeadRequestDto {
72
72
  'bankAccount'?: CreateBankAccountRequestDto;
73
73
  /**
74
74
  * 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
75
- * @type {object}
75
+ * @type {{ [key: string]: object; }}
76
76
  * @memberof CreateLeadRequestDto
77
77
  */
78
- 'customData'?: object;
78
+ 'customData'?: {
79
+ [key: string]: object;
80
+ };
79
81
  /**
80
82
  * 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.
81
83
  * @type {UploadedDocumentDto}
@@ -29,10 +29,12 @@ export interface PolicyObjectRequestDto {
29
29
  'insuredObjectName'?: string;
30
30
  /**
31
31
  * Insured object data. The date will be validated if the \'validate\' flag is set to true.
32
- * @type {object}
32
+ * @type {{ [key: string]: object; }}
33
33
  * @memberof PolicyObjectRequestDto
34
34
  */
35
- 'data'?: object;
35
+ 'data'?: {
36
+ [key: string]: object;
37
+ };
36
38
  /**
37
39
  *
38
40
  * @type {string}
@@ -29,8 +29,10 @@ export interface SendNotificationRequestDto {
29
29
  'emailSubject'?: string;
30
30
  /**
31
31
  * Payload is used by the template engine to replace all template variables with proper data. For more information, please go to https://github.com/flosch/pongo2.
32
- * @type {object}
32
+ * @type {{ [key: string]: object; }}
33
33
  * @memberof SendNotificationRequestDto
34
34
  */
35
- 'payload'?: object;
35
+ 'payload'?: {
36
+ [key: string]: object;
37
+ };
36
38
  }
@@ -65,10 +65,12 @@ export interface UpdateLeadRequestDto {
65
65
  'bankAccount'?: CreateBankAccountRequestDto;
66
66
  /**
67
67
  * 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
68
- * @type {object}
68
+ * @type {{ [key: string]: object; }}
69
69
  * @memberof UpdateLeadRequestDto
70
70
  */
71
- 'customData'?: object;
71
+ 'customData'?: {
72
+ [key: string]: object;
73
+ };
72
74
  /**
73
75
  * 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.
74
76
  * @type {UploadedDocumentDto}
@@ -106,16 +106,16 @@ export interface CreateAccountRequestDto {
106
106
  'accountNumber'?: string;
107
107
  /**
108
108
  * Optional custom fields for account. It could be included additional required/optional fields that the account would need for specific cases.
109
- * @type {object}
109
+ * @type {{ [key: string]: object; }}
110
110
  * @memberof CreateAccountRequestDto
111
111
  */
112
- 'customFields'?: object;
112
+ 'customFields'?: { [key: string]: object; };
113
113
  /**
114
114
  * Metadata contains extra information that the account would need for specific cases.
115
- * @type {object}
115
+ * @type {{ [key: string]: object; }}
116
116
  * @memberof CreateAccountRequestDto
117
117
  */
118
- 'metadata'?: object;
118
+ 'metadata'?: { [key: string]: object; };
119
119
  }
120
120
 
121
121
  export const CreateAccountRequestDtoTitleEnum = {
@@ -22,10 +22,10 @@
22
22
  export interface CreateCustomApplicationRequestDto {
23
23
  /**
24
24
  * Required data to create a custom application.
25
- * @type {object}
25
+ * @type {{ [key: string]: object; }}
26
26
  * @memberof CreateCustomApplicationRequestDto
27
27
  */
28
- 'data': object;
28
+ 'data': { [key: string]: object; };
29
29
  /**
30
30
  * Custom provider name.
31
31
  * @type {string}
@@ -34,10 +34,10 @@ export interface CreateDocumentRequestDto {
34
34
  'productSlug'?: string;
35
35
  /**
36
36
  * Document payload.
37
- * @type {object}
37
+ * @type {{ [key: string]: object; }}
38
38
  * @memberof CreateDocumentRequestDto
39
39
  */
40
- 'payload': object;
40
+ 'payload': { [key: string]: object; };
41
41
  /**
42
42
  * Document entity type.
43
43
  * @type {string}
@@ -76,10 +76,10 @@ export interface CreateDocumentRequestDto {
76
76
  'requester': CreateDocumentRequestDtoRequesterEnum;
77
77
  /**
78
78
  * Metadata contains extra information that the document would need for specific cases.
79
- * @type {object}
79
+ * @type {{ [key: string]: object; }}
80
80
  * @memberof CreateDocumentRequestDto
81
81
  */
82
- 'metadata'?: object;
82
+ 'metadata'?: { [key: string]: object; };
83
83
  /**
84
84
  * Document type.
85
85
  * @type {string}
@@ -36,10 +36,10 @@ export interface CreateEstimatedInvoiceRequestDto {
36
36
  'policyObjects'?: Array<PolicyObjectRequestDto>;
37
37
  /**
38
38
  * Customer custom data for premium calculation. Necessary when no policyObjects are provided.
39
- * @type {object}
39
+ * @type {{ [key: string]: object; }}
40
40
  * @memberof CreateEstimatedInvoiceRequestDto
41
41
  */
42
- 'data'?: object;
42
+ 'data'?: { [key: string]: object; };
43
43
  /**
44
44
  * Custom provider name. Necessary if data is provided.
45
45
  * @type {string}
@@ -77,10 +77,10 @@ export interface CreateLeadRequestDto {
77
77
  'bankAccount'?: CreateBankAccountRequestDto;
78
78
  /**
79
79
  * 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
80
- * @type {object}
80
+ * @type {{ [key: string]: object; }}
81
81
  * @memberof CreateLeadRequestDto
82
82
  */
83
- 'customData'?: object;
83
+ 'customData'?: { [key: string]: object; };
84
84
  /**
85
85
  * 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.
86
86
  * @type {UploadedDocumentDto}
@@ -34,10 +34,10 @@ export interface PolicyObjectRequestDto {
34
34
  'insuredObjectName'?: string;
35
35
  /**
36
36
  * Insured object data. The date will be validated if the \'validate\' flag is set to true.
37
- * @type {object}
37
+ * @type {{ [key: string]: object; }}
38
38
  * @memberof PolicyObjectRequestDto
39
39
  */
40
- 'data'?: object;
40
+ 'data'?: { [key: string]: object; };
41
41
  /**
42
42
  *
43
43
  * @type {string}
@@ -34,9 +34,9 @@ export interface SendNotificationRequestDto {
34
34
  'emailSubject'?: string;
35
35
  /**
36
36
  * Payload is used by the template engine to replace all template variables with proper data. For more information, please go to https://github.com/flosch/pongo2.
37
- * @type {object}
37
+ * @type {{ [key: string]: object; }}
38
38
  * @memberof SendNotificationRequestDto
39
39
  */
40
- 'payload'?: object;
40
+ 'payload'?: { [key: string]: object; };
41
41
  }
42
42
 
@@ -70,10 +70,10 @@ export interface UpdateLeadRequestDto {
70
70
  'bankAccount'?: CreateBankAccountRequestDto;
71
71
  /**
72
72
  * 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
73
- * @type {object}
73
+ * @type {{ [key: string]: object; }}
74
74
  * @memberof UpdateLeadRequestDto
75
75
  */
76
- 'customData'?: object;
76
+ 'customData'?: { [key: string]: object; };
77
77
  /**
78
78
  * 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.
79
79
  * @type {UploadedDocumentDto}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@emilgroup/public-api-sdk-node",
3
- "version": "1.41.1-beta.3",
3
+ "version": "1.41.1-beta.5",
4
4
  "description": "OpenAPI client for @emilgroup/public-api-sdk-node",
5
5
  "author": "OpenAPI-Generator Contributors",
6
6
  "keywords": [
@@ -18,7 +18,7 @@
18
18
  "prepare": "npm run build"
19
19
  },
20
20
  "dependencies": {
21
- "axios": "1.12.0",
21
+ "axios": "1.18.0",
22
22
  "form-data": "^4.0.0",
23
23
  "url": "^0.11.0"
24
24
  },