@cdx-forge/di-typescript-sdk 0.1.0-beta.1

package/dist/generated/src/apis/AlertDeliveryApi.d.ts

@@ -0,0 +1,218 @@
+/**
+ * Candescent DI API
+ * Welcome to the **Candescent Digital Insight API** documentation. This comprehensive API platform enables financial institutions, Marketplace Partners, and developers to build powerful digital banking experiences.  ## Getting Started  New to the Candescent API? Start here:  - **[Quick Start Guide](/guides/getting-started/quickstart/)** - Make your first API call in minutes - **[API Categories Overview](/guides/getting-started/api-overview/)** - Explore all available API categories - **[Error Codes Reference](/guides/getting-started/error-codes/)** - Handle errors effectively  ## API Categories  | Category | Description | |----------|-------------| | **[Accounts](/api/generated/accounts/)** | Account information, transactions, and banking images | | **[Alert Configuration](/api/generated/alert-configuration/)** | Alert types and templates | | **[Alert Delivery](/api/generated/alert-delivery/)** | Alert delivery history | | **[Alert Preferences](/api/generated/alert-preferences/)** | End-user notification preferences | | **[Authentication](/api/generated/authentication/)** | OAuth 2.0 token management and authorization | | **[Business Banking](/api/generated/business-banking/)** | Business banking services | | **[Customer Campaigns](/api/generated/customer-campaigns/)** | User segmentation and promotions | | **[Customer Management](/api/generated/customer-management/)** | Customer profiles, registration, and self-service | | **[Documents and Preferences](/api/generated/documents-and-preferences/)** | Disclosures and e-statement preferences | | **[Money Movement](/api/generated/money-movement/)** | Recipients and fund transfers | | **[MX](/api/generated/mx/)** | Account aggregation and financial insights | | **[Notification Channels](/api/generated/notification-channels/)** | Notification channels for alert delivery |  ## Base URLs  | Environment | Base URL | |-------------|----------| | Stage       | `https://api.candescent.com/digitalbanking/stage` | | Production  | `https://api.candescent.com/digitalbanking` |  > **Note:** This documentation primarily references the **Stage** environment for examples.  ## Authentication Overview  Candescent APIs use OAuth 2.0 with JWT Bearer tokens. Follow these steps:  ### Step 1: Obtain Client Credentials Get your `Client ID` and `Client Secret` from the Candescent Developer Console.  ### Step 2: Generate an Access Token  ```bash curl -X POST \'https://api.candescent.com/digitalbanking/stage/oauth2/v1/token\' \\   -H \'Authorization: Basic <BASE64_ENCODED(CLIENT_ID:CLIENT_SECRET)>\' \\   -H \'Content-Type: application/x-www-form-urlencoded\' \\   -H \'transactionid: <YOUR_UNIQUE_UUID>\' \\   -H \'institutionId: <YOUR_INSTITUTION_ID>\' \\   -d \'grant_type=client_credentials\' ```  ### Step 3: Make Authenticated Requests  Include the token in the `Authorization` header:  ```bash curl \'https://api.candescent.com/digitalbanking/stage/accounts/v1/accounts\' \\   -H \'Authorization: Bearer <YOUR_ACCESS_TOKEN>\' \\   -H \'institutionId: <YOUR_INSTITUTION_ID>\' \\   -H \'transactionid: <YOUR_UNIQUE_UUID>\' ```  > **Tip:** Access tokens expire in ~1 hour. Implement token refresh logic for uninterrupted access.  For detailed authentication flows, see the **[Authentication API Reference](/api/generated/authentication/)**.
+ *
+ * The version of the OpenAPI document: 1.4.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import * as runtime from '../runtime.js';
+import type { AlertHistoryContentResource, AlertHistorySummaryResources, Event } from '../models/index.js';
+export interface AlertDeliveryApiGetHistoryContentRequest {
+    alertHistoryId?: string;
+    eventId?: string;
+    id?: number;
+}
+export interface AlertDeliveryApiListHistoryRequest {
+    accountIds?: Array<string>;
+    alertTypeNames?: Array<string>;
+    emailStatus?: ListHistoryEmailStatusEnum;
+    endDate?: string;
+    eventIds?: Array<string>;
+    id?: number;
+    pushStatus?: ListHistoryPushStatusEnum;
+    readFlag?: boolean;
+    smsStatus?: ListHistorySmsStatusEnum;
+    startDate?: string;
+    hostUserId?: string;
+    loginId?: string;
+    institutionCustomerId?: string;
+}
+export interface AlertDeliveryApiPublishEventsRequest {
+    event: Event;
+    institutionCustomerId?: string;
+    hostUserId?: string;
+    loginId?: string;
+}
+/**
+ * AlertDeliveryApi - interface
+ *
+ * @export
+ * @interface AlertDeliveryApiInterface
+ */
+export interface AlertDeliveryApiInterface {
+    /**
+     * Creates request options for getHistoryContent without sending the request
+     * @param {string} [alertHistoryId] alertHistoryId
+     * @param {string} [eventId] eventId
+     * @param {number} [id] id
+     * @throws {RequiredError}
+     * @memberof AlertDeliveryApiInterface
+     */
+    getHistoryContentRequestOpts(requestParameters: AlertDeliveryApiGetHistoryContentRequest): Promise<runtime.RequestOpts>;
+    /**
+     * Retrieve specific alert history records using content ID, history summary ID, or event ID.
+     * @summary Get alert history content
+     * @param {string} [alertHistoryId] alertHistoryId
+     * @param {string} [eventId] eventId
+     * @param {number} [id] id
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof AlertDeliveryApiInterface
+     */
+    getHistoryContentRaw(requestParameters: AlertDeliveryApiGetHistoryContentRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<AlertHistoryContentResource>>;
+    /**
+     * Retrieve specific alert history records using content ID, history summary ID, or event ID.
+     * Get alert history content
+     */
+    getHistoryContent(requestParameters: AlertDeliveryApiGetHistoryContentRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AlertHistoryContentResource>;
+    /**
+     * Creates request options for listHistory without sending the request
+     * @param {Array<string>} [accountIds] accountIds
+     * @param {Array<string>} [alertTypeNames] alertTypeNames
+     * @param {Array<'SUCCESS' | 'FAILURE' | 'IN_PROCESS'>} [emailStatus] emailStatus
+     * @param {string} [endDate] endDate
+     * @param {Array<string>} [eventIds] eventIds
+     * @param {number} [id] id
+     * @param {Array<'SUCCESS' | 'FAILURE' | 'IN_PROCESS'>} [pushStatus] pushStatus
+     * @param {boolean} [readFlag] readFlag
+     * @param {Array<'SUCCESS' | 'FAILURE' | 'IN_PROCESS'>} [smsStatus] smsStatus
+     * @param {string} [startDate] startDate
+     * @param {string} [hostUserId] Identifier for the user associated with the financial institution. This parameter is **required** when the access token was issued using the &#x60;client_credentials&#x60; grant type; otherwise, it is optional. Cannot be used with &#x60;loginId&#x60; query parameter.
+     * @param {string} [loginId] Login identifier for the user associated with the financial institution. This parameter is **required** when the access token was issued using the &#x60;client_credentials&#x60; grant type; otherwise, it is optional. Cannot be used with &#x60;hostUserId&#x60; query parameter.
+     * @param {string} [institutionCustomerId] institutionCustomerId
+     * @throws {RequiredError}
+     * @memberof AlertDeliveryApiInterface
+     */
+    listHistoryRequestOpts(requestParameters: AlertDeliveryApiListHistoryRequest): Promise<runtime.RequestOpts>;
+    /**
+     * Retrieve alert history data using various filter parameters. You can filter by account IDs, date range, alert types, and other criteria.
+     * @summary List alert history
+     * @param {Array<string>} [accountIds] accountIds
+     * @param {Array<string>} [alertTypeNames] alertTypeNames
+     * @param {Array<'SUCCESS' | 'FAILURE' | 'IN_PROCESS'>} [emailStatus] emailStatus
+     * @param {string} [endDate] endDate
+     * @param {Array<string>} [eventIds] eventIds
+     * @param {number} [id] id
+     * @param {Array<'SUCCESS' | 'FAILURE' | 'IN_PROCESS'>} [pushStatus] pushStatus
+     * @param {boolean} [readFlag] readFlag
+     * @param {Array<'SUCCESS' | 'FAILURE' | 'IN_PROCESS'>} [smsStatus] smsStatus
+     * @param {string} [startDate] startDate
+     * @param {string} [hostUserId] Identifier for the user associated with the financial institution. This parameter is **required** when the access token was issued using the &#x60;client_credentials&#x60; grant type; otherwise, it is optional. Cannot be used with &#x60;loginId&#x60; query parameter.
+     * @param {string} [loginId] Login identifier for the user associated with the financial institution. This parameter is **required** when the access token was issued using the &#x60;client_credentials&#x60; grant type; otherwise, it is optional. Cannot be used with &#x60;hostUserId&#x60; query parameter.
+     * @param {string} [institutionCustomerId] institutionCustomerId
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof AlertDeliveryApiInterface
+     */
+    listHistoryRaw(requestParameters: AlertDeliveryApiListHistoryRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<AlertHistorySummaryResources>>;
+    /**
+     * Retrieve alert history data using various filter parameters. You can filter by account IDs, date range, alert types, and other criteria.
+     * List alert history
+     */
+    listHistory(requestParameters: AlertDeliveryApiListHistoryRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AlertHistorySummaryResources>;
+    /**
+     * Creates request options for publishEvents without sending the request
+     * @param {Event} event event
+     * @param {string} [institutionCustomerId] institutionCustomerId
+     * @param {string} [hostUserId] Identifier for the user associated with the financial institution. This parameter is **required** when the access token was issued using the &#x60;client_credentials&#x60; grant type; otherwise, it is optional. Cannot be used with &#x60;loginId&#x60; query parameter.
+     * @param {string} [loginId] Login identifier for the user associated with the financial institution. This parameter is **required** when the access token was issued using the &#x60;client_credentials&#x60; grant type; otherwise, it is optional. Cannot be used with &#x60;hostUserId&#x60; query parameter.
+     * @throws {RequiredError}
+     * @memberof AlertDeliveryApiInterface
+     */
+    publishEventsRequestOpts(requestParameters: AlertDeliveryApiPublishEventsRequest): Promise<runtime.RequestOpts>;
+    /**
+     * Trigger an alert notification when an event occurs. This API processes the event data and sends notifications based on the configured alert type, template, and customer preferences.  **Event Domain Types:** - **AccountEvent**: Account-related alerts (balance changes, low balance, etc.) - **TransactionEvent**: Transaction-related alerts (large transactions, payment exceeding limit, etc.) - **NotificationEvent**: Messages from external parties (such as Visa) that pass through to the customer without additional processing - **UserEvent**: User-related events (login, password change, etc.)  **Processing Flow:** 1. Event is received and validated 2. Alert type and user preferences are matched 3. Template is applied with event data 4. Notifications are sent via configured channels (EMAIL, SMS, PUSH)
+     * @summary Publish alert event
+     * @param {Event} event event
+     * @param {string} [institutionCustomerId] institutionCustomerId
+     * @param {string} [hostUserId] Identifier for the user associated with the financial institution. This parameter is **required** when the access token was issued using the &#x60;client_credentials&#x60; grant type; otherwise, it is optional. Cannot be used with &#x60;loginId&#x60; query parameter.
+     * @param {string} [loginId] Login identifier for the user associated with the financial institution. This parameter is **required** when the access token was issued using the &#x60;client_credentials&#x60; grant type; otherwise, it is optional. Cannot be used with &#x60;hostUserId&#x60; query parameter.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof AlertDeliveryApiInterface
+     */
+    publishEventsRaw(requestParameters: AlertDeliveryApiPublishEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
+    /**
+     * Trigger an alert notification when an event occurs. This API processes the event data and sends notifications based on the configured alert type, template, and customer preferences.  **Event Domain Types:** - **AccountEvent**: Account-related alerts (balance changes, low balance, etc.) - **TransactionEvent**: Transaction-related alerts (large transactions, payment exceeding limit, etc.) - **NotificationEvent**: Messages from external parties (such as Visa) that pass through to the customer without additional processing - **UserEvent**: User-related events (login, password change, etc.)  **Processing Flow:** 1. Event is received and validated 2. Alert type and user preferences are matched 3. Template is applied with event data 4. Notifications are sent via configured channels (EMAIL, SMS, PUSH)
+     * Publish alert event
+     */
+    publishEvents(requestParameters: AlertDeliveryApiPublishEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;
+}
+/**
+ *
+ */
+export declare class AlertDeliveryApi extends runtime.BaseAPI implements AlertDeliveryApiInterface {
+    /**
+     * Creates request options for getHistoryContent without sending the request
+     */
+    getHistoryContentRequestOpts(requestParameters: AlertDeliveryApiGetHistoryContentRequest): Promise<runtime.RequestOpts>;
+    /**
+     * Retrieve specific alert history records using content ID, history summary ID, or event ID.
+     * Get alert history content
+     */
+    getHistoryContentRaw(requestParameters: AlertDeliveryApiGetHistoryContentRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<AlertHistoryContentResource>>;
+    /**
+     * Retrieve specific alert history records using content ID, history summary ID, or event ID.
+     * Get alert history content
+     */
+    getHistoryContent(requestParameters?: AlertDeliveryApiGetHistoryContentRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AlertHistoryContentResource>;
+    /**
+     * Creates request options for listHistory without sending the request
+     */
+    listHistoryRequestOpts(requestParameters: AlertDeliveryApiListHistoryRequest): Promise<runtime.RequestOpts>;
+    /**
+     * Retrieve alert history data using various filter parameters. You can filter by account IDs, date range, alert types, and other criteria.
+     * List alert history
+     */
+    listHistoryRaw(requestParameters: AlertDeliveryApiListHistoryRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<AlertHistorySummaryResources>>;
+    /**
+     * Retrieve alert history data using various filter parameters. You can filter by account IDs, date range, alert types, and other criteria.
+     * List alert history
+     */
+    listHistory(requestParameters?: AlertDeliveryApiListHistoryRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AlertHistorySummaryResources>;
+    /**
+     * Creates request options for publishEvents without sending the request
+     */
+    publishEventsRequestOpts(requestParameters: AlertDeliveryApiPublishEventsRequest): Promise<runtime.RequestOpts>;
+    /**
+     * Trigger an alert notification when an event occurs. This API processes the event data and sends notifications based on the configured alert type, template, and customer preferences.  **Event Domain Types:** - **AccountEvent**: Account-related alerts (balance changes, low balance, etc.) - **TransactionEvent**: Transaction-related alerts (large transactions, payment exceeding limit, etc.) - **NotificationEvent**: Messages from external parties (such as Visa) that pass through to the customer without additional processing - **UserEvent**: User-related events (login, password change, etc.)  **Processing Flow:** 1. Event is received and validated 2. Alert type and user preferences are matched 3. Template is applied with event data 4. Notifications are sent via configured channels (EMAIL, SMS, PUSH)
+     * Publish alert event
+     */
+    publishEventsRaw(requestParameters: AlertDeliveryApiPublishEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
+    /**
+     * Trigger an alert notification when an event occurs. This API processes the event data and sends notifications based on the configured alert type, template, and customer preferences.  **Event Domain Types:** - **AccountEvent**: Account-related alerts (balance changes, low balance, etc.) - **TransactionEvent**: Transaction-related alerts (large transactions, payment exceeding limit, etc.) - **NotificationEvent**: Messages from external parties (such as Visa) that pass through to the customer without additional processing - **UserEvent**: User-related events (login, password change, etc.)  **Processing Flow:** 1. Event is received and validated 2. Alert type and user preferences are matched 3. Template is applied with event data 4. Notifications are sent via configured channels (EMAIL, SMS, PUSH)
+     * Publish alert event
+     */
+    publishEvents(requestParameters: AlertDeliveryApiPublishEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;
+}
+/**
+ * @export
+ */
+export declare const ListHistoryEmailStatusEnum: {
+    readonly SUCCESS: "SUCCESS";
+    readonly FAILURE: "FAILURE";
+    readonly IN_PROCESS: "IN_PROCESS";
+};
+export type ListHistoryEmailStatusEnum = typeof ListHistoryEmailStatusEnum[keyof typeof ListHistoryEmailStatusEnum];
+/**
+ * @export
+ */
+export declare const ListHistoryPushStatusEnum: {
+    readonly SUCCESS: "SUCCESS";
+    readonly FAILURE: "FAILURE";
+    readonly IN_PROCESS: "IN_PROCESS";
+};
+export type ListHistoryPushStatusEnum = typeof ListHistoryPushStatusEnum[keyof typeof ListHistoryPushStatusEnum];
+/**
+ * @export
+ */
+export declare const ListHistorySmsStatusEnum: {
+    readonly SUCCESS: "SUCCESS";
+    readonly FAILURE: "FAILURE";
+    readonly IN_PROCESS: "IN_PROCESS";
+};
+export type ListHistorySmsStatusEnum = typeof ListHistorySmsStatusEnum[keyof typeof ListHistorySmsStatusEnum];

package/dist/generated/src/apis/AlertDeliveryApi.js

@@ -0,0 +1,219 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * Candescent DI API
+ * Welcome to the **Candescent Digital Insight API** documentation. This comprehensive API platform enables financial institutions, Marketplace Partners, and developers to build powerful digital banking experiences.  ## Getting Started  New to the Candescent API? Start here:  - **[Quick Start Guide](/guides/getting-started/quickstart/)** - Make your first API call in minutes - **[API Categories Overview](/guides/getting-started/api-overview/)** - Explore all available API categories - **[Error Codes Reference](/guides/getting-started/error-codes/)** - Handle errors effectively  ## API Categories  | Category | Description | |----------|-------------| | **[Accounts](/api/generated/accounts/)** | Account information, transactions, and banking images | | **[Alert Configuration](/api/generated/alert-configuration/)** | Alert types and templates | | **[Alert Delivery](/api/generated/alert-delivery/)** | Alert delivery history | | **[Alert Preferences](/api/generated/alert-preferences/)** | End-user notification preferences | | **[Authentication](/api/generated/authentication/)** | OAuth 2.0 token management and authorization | | **[Business Banking](/api/generated/business-banking/)** | Business banking services | | **[Customer Campaigns](/api/generated/customer-campaigns/)** | User segmentation and promotions | | **[Customer Management](/api/generated/customer-management/)** | Customer profiles, registration, and self-service | | **[Documents and Preferences](/api/generated/documents-and-preferences/)** | Disclosures and e-statement preferences | | **[Money Movement](/api/generated/money-movement/)** | Recipients and fund transfers | | **[MX](/api/generated/mx/)** | Account aggregation and financial insights | | **[Notification Channels](/api/generated/notification-channels/)** | Notification channels for alert delivery |  ## Base URLs  | Environment | Base URL | |-------------|----------| | Stage       | `https://api.candescent.com/digitalbanking/stage` | | Production  | `https://api.candescent.com/digitalbanking` |  > **Note:** This documentation primarily references the **Stage** environment for examples.  ## Authentication Overview  Candescent APIs use OAuth 2.0 with JWT Bearer tokens. Follow these steps:  ### Step 1: Obtain Client Credentials Get your `Client ID` and `Client Secret` from the Candescent Developer Console.  ### Step 2: Generate an Access Token  ```bash curl -X POST \'https://api.candescent.com/digitalbanking/stage/oauth2/v1/token\' \\   -H \'Authorization: Basic <BASE64_ENCODED(CLIENT_ID:CLIENT_SECRET)>\' \\   -H \'Content-Type: application/x-www-form-urlencoded\' \\   -H \'transactionid: <YOUR_UNIQUE_UUID>\' \\   -H \'institutionId: <YOUR_INSTITUTION_ID>\' \\   -d \'grant_type=client_credentials\' ```  ### Step 3: Make Authenticated Requests  Include the token in the `Authorization` header:  ```bash curl \'https://api.candescent.com/digitalbanking/stage/accounts/v1/accounts\' \\   -H \'Authorization: Bearer <YOUR_ACCESS_TOKEN>\' \\   -H \'institutionId: <YOUR_INSTITUTION_ID>\' \\   -H \'transactionid: <YOUR_UNIQUE_UUID>\' ```  > **Tip:** Access tokens expire in ~1 hour. Implement token refresh logic for uninterrupted access.  For detailed authentication flows, see the **[Authentication API Reference](/api/generated/authentication/)**.
+ *
+ * The version of the OpenAPI document: 1.4.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import * as runtime from '../runtime.js';
+import { AlertHistoryContentResourceFromJSON, AlertHistorySummaryResourcesFromJSON, EventToJSON, } from '../models/index.js';
+/**
+ *
+ */
+export class AlertDeliveryApi extends runtime.BaseAPI {
+    /**
+     * Creates request options for getHistoryContent without sending the request
+     */
+    async getHistoryContentRequestOpts(requestParameters) {
+        const queryParameters = {};
+        if (requestParameters['alertHistoryId'] != null) {
+            queryParameters['alertHistoryId'] = requestParameters['alertHistoryId'];
+        }
+        if (requestParameters['eventId'] != null) {
+            queryParameters['eventId'] = requestParameters['eventId'];
+        }
+        if (requestParameters['id'] != null) {
+            queryParameters['id'] = requestParameters['id'];
+        }
+        const headerParameters = {};
+        if (this.configuration && this.configuration.accessToken) {
+            const token = this.configuration.accessToken;
+            const tokenString = await token("BearerAuth", []);
+            if (tokenString) {
+                headerParameters["Authorization"] = `Bearer ${tokenString}`;
+            }
+        }
+        let urlPath = `/db-alerts-delivery/v1/alert-history-content`;
+        return {
+            path: urlPath,
+            method: 'GET',
+            headers: headerParameters,
+            query: queryParameters,
+        };
+    }
+    /**
+     * Retrieve specific alert history records using content ID, history summary ID, or event ID.
+     * Get alert history content
+     */
+    async getHistoryContentRaw(requestParameters, initOverrides) {
+        const requestOptions = await this.getHistoryContentRequestOpts(requestParameters);
+        const response = await this.request(requestOptions, initOverrides);
+        return new runtime.JSONApiResponse(response, (jsonValue) => AlertHistoryContentResourceFromJSON(jsonValue));
+    }
+    /**
+     * Retrieve specific alert history records using content ID, history summary ID, or event ID.
+     * Get alert history content
+     */
+    async getHistoryContent(requestParameters = {}, initOverrides) {
+        const response = await this.getHistoryContentRaw(requestParameters, initOverrides);
+        return await response.value();
+    }
+    /**
+     * Creates request options for listHistory without sending the request
+     */
+    async listHistoryRequestOpts(requestParameters) {
+        const queryParameters = {};
+        if (requestParameters['accountIds'] != null) {
+            queryParameters['accountIds'] = requestParameters['accountIds'];
+        }
+        if (requestParameters['alertTypeNames'] != null) {
+            queryParameters['alertTypeNames'] = requestParameters['alertTypeNames'];
+        }
+        if (requestParameters['emailStatus'] != null) {
+            queryParameters['emailStatus'] = requestParameters['emailStatus'];
+        }
+        if (requestParameters['endDate'] != null) {
+            queryParameters['endDate'] = requestParameters['endDate'];
+        }
+        if (requestParameters['eventIds'] != null) {
+            queryParameters['eventIds'] = requestParameters['eventIds'];
+        }
+        if (requestParameters['id'] != null) {
+            queryParameters['id'] = requestParameters['id'];
+        }
+        if (requestParameters['pushStatus'] != null) {
+            queryParameters['pushStatus'] = requestParameters['pushStatus'];
+        }
+        if (requestParameters['readFlag'] != null) {
+            queryParameters['readFlag'] = requestParameters['readFlag'];
+        }
+        if (requestParameters['smsStatus'] != null) {
+            queryParameters['smsStatus'] = requestParameters['smsStatus'];
+        }
+        if (requestParameters['startDate'] != null) {
+            queryParameters['startDate'] = requestParameters['startDate'];
+        }
+        if (requestParameters['hostUserId'] != null) {
+            queryParameters['hostUserId'] = requestParameters['hostUserId'];
+        }
+        if (requestParameters['loginId'] != null) {
+            queryParameters['loginId'] = requestParameters['loginId'];
+        }
+        const headerParameters = {};
+        if (requestParameters['institutionCustomerId'] != null) {
+            headerParameters['institutionCustomerId'] = String(requestParameters['institutionCustomerId']);
+        }
+        if (this.configuration && this.configuration.accessToken) {
+            const token = this.configuration.accessToken;
+            const tokenString = await token("BearerAuth", []);
+            if (tokenString) {
+                headerParameters["Authorization"] = `Bearer ${tokenString}`;
+            }
+        }
+        let urlPath = `/db-alerts-delivery/v1/alert-history`;
+        return {
+            path: urlPath,
+            method: 'GET',
+            headers: headerParameters,
+            query: queryParameters,
+        };
+    }
+    /**
+     * Retrieve alert history data using various filter parameters. You can filter by account IDs, date range, alert types, and other criteria.
+     * List alert history
+     */
+    async listHistoryRaw(requestParameters, initOverrides) {
+        const requestOptions = await this.listHistoryRequestOpts(requestParameters);
+        const response = await this.request(requestOptions, initOverrides);
+        return new runtime.JSONApiResponse(response, (jsonValue) => AlertHistorySummaryResourcesFromJSON(jsonValue));
+    }
+    /**
+     * Retrieve alert history data using various filter parameters. You can filter by account IDs, date range, alert types, and other criteria.
+     * List alert history
+     */
+    async listHistory(requestParameters = {}, initOverrides) {
+        const response = await this.listHistoryRaw(requestParameters, initOverrides);
+        return await response.value();
+    }
+    /**
+     * Creates request options for publishEvents without sending the request
+     */
+    async publishEventsRequestOpts(requestParameters) {
+        if (requestParameters['event'] == null) {
+            throw new runtime.RequiredError('event', 'Required parameter "event" was null or undefined when calling publishEvents().');
+        }
+        const queryParameters = {};
+        if (requestParameters['hostUserId'] != null) {
+            queryParameters['hostUserId'] = requestParameters['hostUserId'];
+        }
+        if (requestParameters['loginId'] != null) {
+            queryParameters['loginId'] = requestParameters['loginId'];
+        }
+        const headerParameters = {};
+        headerParameters['Content-Type'] = 'application/json';
+        if (requestParameters['institutionCustomerId'] != null) {
+            headerParameters['institutionCustomerId'] = String(requestParameters['institutionCustomerId']);
+        }
+        if (this.configuration && this.configuration.accessToken) {
+            const token = this.configuration.accessToken;
+            const tokenString = await token("BearerAuth", []);
+            if (tokenString) {
+                headerParameters["Authorization"] = `Bearer ${tokenString}`;
+            }
+        }
+        let urlPath = `/db-events/v1/realtime-events`;
+        return {
+            path: urlPath,
+            method: 'POST',
+            headers: headerParameters,
+            query: queryParameters,
+            body: EventToJSON(requestParameters['event']),
+        };
+    }
+    /**
+     * Trigger an alert notification when an event occurs. This API processes the event data and sends notifications based on the configured alert type, template, and customer preferences.  **Event Domain Types:** - **AccountEvent**: Account-related alerts (balance changes, low balance, etc.) - **TransactionEvent**: Transaction-related alerts (large transactions, payment exceeding limit, etc.) - **NotificationEvent**: Messages from external parties (such as Visa) that pass through to the customer without additional processing - **UserEvent**: User-related events (login, password change, etc.)  **Processing Flow:** 1. Event is received and validated 2. Alert type and user preferences are matched 3. Template is applied with event data 4. Notifications are sent via configured channels (EMAIL, SMS, PUSH)
+     * Publish alert event
+     */
+    async publishEventsRaw(requestParameters, initOverrides) {
+        const requestOptions = await this.publishEventsRequestOpts(requestParameters);
+        const response = await this.request(requestOptions, initOverrides);
+        return new runtime.VoidApiResponse(response);
+    }
+    /**
+     * Trigger an alert notification when an event occurs. This API processes the event data and sends notifications based on the configured alert type, template, and customer preferences.  **Event Domain Types:** - **AccountEvent**: Account-related alerts (balance changes, low balance, etc.) - **TransactionEvent**: Transaction-related alerts (large transactions, payment exceeding limit, etc.) - **NotificationEvent**: Messages from external parties (such as Visa) that pass through to the customer without additional processing - **UserEvent**: User-related events (login, password change, etc.)  **Processing Flow:** 1. Event is received and validated 2. Alert type and user preferences are matched 3. Template is applied with event data 4. Notifications are sent via configured channels (EMAIL, SMS, PUSH)
+     * Publish alert event
+     */
+    async publishEvents(requestParameters, initOverrides) {
+        await this.publishEventsRaw(requestParameters, initOverrides);
+    }
+}
+/**
+ * @export
+ */
+export const ListHistoryEmailStatusEnum = {
+    SUCCESS: 'SUCCESS',
+    FAILURE: 'FAILURE',
+    IN_PROCESS: 'IN_PROCESS'
+};
+/**
+ * @export
+ */
+export const ListHistoryPushStatusEnum = {
+    SUCCESS: 'SUCCESS',
+    FAILURE: 'FAILURE',
+    IN_PROCESS: 'IN_PROCESS'
+};
+/**
+ * @export
+ */
+export const ListHistorySmsStatusEnum = {
+    SUCCESS: 'SUCCESS',
+    FAILURE: 'FAILURE',
+    IN_PROCESS: 'IN_PROCESS'
+};