@brokerize/client 1.4.0 → 1.6.0

package/dist/cjs/swagger/apis/WebsocketApi.d.ts

@@ -0,0 +1,24 @@
+/**
+ * brokerize
+ * The brokerize API allows clients to implement multi-brokerage with a unified interface. For more information, visit brokerize.com
+ *
+ *
+ *
+ * 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";
+/**
+ *
+ */
+export declare class WebsocketApi extends runtime.BaseAPI {
+    /**
+     * Most operations at brokerize have asynchronous effects.  For example, consider the flow of an order: when the user creates an order, it will not immediately appear in order list endpoints, because usually brokers take a few seconds until they are retrievable in those lists. Also, after a while, the order may be executed or cancelled asynchronously by the stock exchange.  A common solution for frontends would be to reload the order list regularly. However data is then either delayed or there will be many more requests than needed.  The brokerize websocket endpoint allows getting updates via web sockets. Generally speaking, clients can subscribe by assigning a subscription id and will then receive updates on that subscription.  In this documentation, ⬆️ denotes messages from the client to the server, whereas messages from server to client are marked with ⬇️.  ## authentication  When using cookies for authorization, the WebSocket connection is authenticated with the HTTP upgrade request.  If token headers are used, the _first_ message from client to server must be:  ``` ⬆️ {     \"cmd\": \"authorize\",     \"idToken\": <string> } ```  In all cases, clients must wait for the welcome message before sending other messages:  ``` ⬇️ { \"cmd\": \"authenticated\" } ```  ## ping  After 1 minute of inactivity of a client, the WebSocket connection will be considered stale and will automatically terminated. To prevent this, a ping message can be sent:  ```  ⬆️ {\"cmd\": \"ping\"} ```  The server also sends this message regularly. If no message has been received on a WebSocket connection for more than 1 minute, it should be terminated by the client.  ```  ⬇️ {\"cmd\": \"ping\"} ```  ## subscriptions  Subscriptions can be used to get invalidate events or updates for selected resources.  ### invalidate subscriptions  Invalidation events can be used for the frontend to know when reload requests via the HTTP endpoints are appropriate. Currently only invalidate events can be subscribed, the actual data must then be reloaded using the HTTP endpoints.  To set up a subscription for an invalidate event, use:  ``` ⬆️ {     \"cmd\": \"subscribe\",     \"type\": \"invalidate\",     \"subscriptionId\": 1,     \"entity: \"brokersessions\" /_* \"positions\" | \"orders\" *_/,     \"portfolioId\": 42 /_* required for \"positions\" or \"orders\" *_/ } ```  If the subscription failed to be set up on the server, an error will be sent for the subscription. This also automatically ends the subscription on the server side:  ``` ⬇️ {     \"subscriptionId\": 1,     \"error\": {         \"message\": \"Could not set up invalidation event due to...\"     } } ```  If an invalid `subscriptionId` is provided (or the subscription id is already in use by the connection), an error like this will be sent:  ``` ⬇️ {     \"error\": {         \"message\": \"Could not add subscription due to invalid subscriptionId\"     } } ```  ⚠️ _the connection will then be terminated immediately_.  If the subscription is sucessfuly set up, whenever an invalidation happens, the server will send a message like this:  ``` ⬇️ {     \"cmd\": \"invalidate\",     \"subscriptionId\": 1 } ```  When that invalidation event is received, the client should reload the data using the corresponding endpoints.  Clients can end their subscription with the `unsubscribe` command:  ``` ⬆️ {     \"cmd\": \"unsubscribe\",     \"subscriptionId\": 1 } ```  ### subscribe to the state of a decoupled operation  For decoupled operations (e.g. authorizing a session TAN using a second factor device), the state of the operation can be subscribed:  ``` ⬆️ {     \"cmd\": \"subscribe\",     \"type\": \"decoupledOperationStatus\",     \"subscriptionId\": 1,     \"sessionId\": string,     \"decoupledOperationId\": string } ```  Error handling as well as unsubscribing works as described for invalidate subscriptions. Example message from the server for updating the state:  ``` ⬇️ {     \"cmd\": \"updateDecoupledOperationStatus\",     \"subscriptionId\": number,     \"state\": <DecoupledOperationStatus> } ```
+     */
+    websocketRaw(initOverrides?: RequestInit | runtime.InitOverideFunction): Promise<runtime.ApiResponse<void>>;
+    /**
+     * Most operations at brokerize have asynchronous effects.  For example, consider the flow of an order: when the user creates an order, it will not immediately appear in order list endpoints, because usually brokers take a few seconds until they are retrievable in those lists. Also, after a while, the order may be executed or cancelled asynchronously by the stock exchange.  A common solution for frontends would be to reload the order list regularly. However data is then either delayed or there will be many more requests than needed.  The brokerize websocket endpoint allows getting updates via web sockets. Generally speaking, clients can subscribe by assigning a subscription id and will then receive updates on that subscription.  In this documentation, ⬆️ denotes messages from the client to the server, whereas messages from server to client are marked with ⬇️.  ## authentication  When using cookies for authorization, the WebSocket connection is authenticated with the HTTP upgrade request.  If token headers are used, the _first_ message from client to server must be:  ``` ⬆️ {     \"cmd\": \"authorize\",     \"idToken\": <string> } ```  In all cases, clients must wait for the welcome message before sending other messages:  ``` ⬇️ { \"cmd\": \"authenticated\" } ```  ## ping  After 1 minute of inactivity of a client, the WebSocket connection will be considered stale and will automatically terminated. To prevent this, a ping message can be sent:  ```  ⬆️ {\"cmd\": \"ping\"} ```  The server also sends this message regularly. If no message has been received on a WebSocket connection for more than 1 minute, it should be terminated by the client.  ```  ⬇️ {\"cmd\": \"ping\"} ```  ## subscriptions  Subscriptions can be used to get invalidate events or updates for selected resources.  ### invalidate subscriptions  Invalidation events can be used for the frontend to know when reload requests via the HTTP endpoints are appropriate. Currently only invalidate events can be subscribed, the actual data must then be reloaded using the HTTP endpoints.  To set up a subscription for an invalidate event, use:  ``` ⬆️ {     \"cmd\": \"subscribe\",     \"type\": \"invalidate\",     \"subscriptionId\": 1,     \"entity: \"brokersessions\" /_* \"positions\" | \"orders\" *_/,     \"portfolioId\": 42 /_* required for \"positions\" or \"orders\" *_/ } ```  If the subscription failed to be set up on the server, an error will be sent for the subscription. This also automatically ends the subscription on the server side:  ``` ⬇️ {     \"subscriptionId\": 1,     \"error\": {         \"message\": \"Could not set up invalidation event due to...\"     } } ```  If an invalid `subscriptionId` is provided (or the subscription id is already in use by the connection), an error like this will be sent:  ``` ⬇️ {     \"error\": {         \"message\": \"Could not add subscription due to invalid subscriptionId\"     } } ```  ⚠️ _the connection will then be terminated immediately_.  If the subscription is sucessfuly set up, whenever an invalidation happens, the server will send a message like this:  ``` ⬇️ {     \"cmd\": \"invalidate\",     \"subscriptionId\": 1 } ```  When that invalidation event is received, the client should reload the data using the corresponding endpoints.  Clients can end their subscription with the `unsubscribe` command:  ``` ⬆️ {     \"cmd\": \"unsubscribe\",     \"subscriptionId\": 1 } ```  ### subscribe to the state of a decoupled operation  For decoupled operations (e.g. authorizing a session TAN using a second factor device), the state of the operation can be subscribed:  ``` ⬆️ {     \"cmd\": \"subscribe\",     \"type\": \"decoupledOperationStatus\",     \"subscriptionId\": 1,     \"sessionId\": string,     \"decoupledOperationId\": string } ```  Error handling as well as unsubscribing works as described for invalidate subscriptions. Example message from the server for updating the state:  ``` ⬇️ {     \"cmd\": \"updateDecoupledOperationStatus\",     \"subscriptionId\": number,     \"state\": <DecoupledOperationStatus> } ```
+     */
+    websocket(initOverrides?: RequestInit | runtime.InitOverideFunction): Promise<void>;
+}

package/dist/cjs/swagger/apis/WebsocketApi.js

@@ -0,0 +1,65 @@
+"use strict";
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * brokerize
+ * The brokerize API allows clients to implement multi-brokerage with a unified interface. For more information, visit brokerize.com
+ *
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
+}) : (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    o[k2] = m[k];
+}));
+var __setModuleDefault = (this && this.__setModuleDefault) || (Object.create ? (function(o, v) {
+    Object.defineProperty(o, "default", { enumerable: true, value: v });
+}) : function(o, v) {
+    o["default"] = v;
+});
+var __importStar = (this && this.__importStar) || function (mod) {
+    if (mod && mod.__esModule) return mod;
+    var result = {};
+    if (mod != null) for (var k in mod) if (k !== "default" && Object.prototype.hasOwnProperty.call(mod, k)) __createBinding(result, mod, k);
+    __setModuleDefault(result, mod);
+    return result;
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.WebsocketApi = void 0;
+const runtime = __importStar(require("../runtime"));
+/**
+ *
+ */
+class WebsocketApi extends runtime.BaseAPI {
+    /**
+     * Most operations at brokerize have asynchronous effects.  For example, consider the flow of an order: when the user creates an order, it will not immediately appear in order list endpoints, because usually brokers take a few seconds until they are retrievable in those lists. Also, after a while, the order may be executed or cancelled asynchronously by the stock exchange.  A common solution for frontends would be to reload the order list regularly. However data is then either delayed or there will be many more requests than needed.  The brokerize websocket endpoint allows getting updates via web sockets. Generally speaking, clients can subscribe by assigning a subscription id and will then receive updates on that subscription.  In this documentation, ⬆️ denotes messages from the client to the server, whereas messages from server to client are marked with ⬇️.  ## authentication  When using cookies for authorization, the WebSocket connection is authenticated with the HTTP upgrade request.  If token headers are used, the _first_ message from client to server must be:  ``` ⬆️ {     \"cmd\": \"authorize\",     \"idToken\": <string> } ```  In all cases, clients must wait for the welcome message before sending other messages:  ``` ⬇️ { \"cmd\": \"authenticated\" } ```  ## ping  After 1 minute of inactivity of a client, the WebSocket connection will be considered stale and will automatically terminated. To prevent this, a ping message can be sent:  ```  ⬆️ {\"cmd\": \"ping\"} ```  The server also sends this message regularly. If no message has been received on a WebSocket connection for more than 1 minute, it should be terminated by the client.  ```  ⬇️ {\"cmd\": \"ping\"} ```  ## subscriptions  Subscriptions can be used to get invalidate events or updates for selected resources.  ### invalidate subscriptions  Invalidation events can be used for the frontend to know when reload requests via the HTTP endpoints are appropriate. Currently only invalidate events can be subscribed, the actual data must then be reloaded using the HTTP endpoints.  To set up a subscription for an invalidate event, use:  ``` ⬆️ {     \"cmd\": \"subscribe\",     \"type\": \"invalidate\",     \"subscriptionId\": 1,     \"entity: \"brokersessions\" /_* \"positions\" | \"orders\" *_/,     \"portfolioId\": 42 /_* required for \"positions\" or \"orders\" *_/ } ```  If the subscription failed to be set up on the server, an error will be sent for the subscription. This also automatically ends the subscription on the server side:  ``` ⬇️ {     \"subscriptionId\": 1,     \"error\": {         \"message\": \"Could not set up invalidation event due to...\"     } } ```  If an invalid `subscriptionId` is provided (or the subscription id is already in use by the connection), an error like this will be sent:  ``` ⬇️ {     \"error\": {         \"message\": \"Could not add subscription due to invalid subscriptionId\"     } } ```  ⚠️ _the connection will then be terminated immediately_.  If the subscription is sucessfuly set up, whenever an invalidation happens, the server will send a message like this:  ``` ⬇️ {     \"cmd\": \"invalidate\",     \"subscriptionId\": 1 } ```  When that invalidation event is received, the client should reload the data using the corresponding endpoints.  Clients can end their subscription with the `unsubscribe` command:  ``` ⬆️ {     \"cmd\": \"unsubscribe\",     \"subscriptionId\": 1 } ```  ### subscribe to the state of a decoupled operation  For decoupled operations (e.g. authorizing a session TAN using a second factor device), the state of the operation can be subscribed:  ``` ⬆️ {     \"cmd\": \"subscribe\",     \"type\": \"decoupledOperationStatus\",     \"subscriptionId\": 1,     \"sessionId\": string,     \"decoupledOperationId\": string } ```  Error handling as well as unsubscribing works as described for invalidate subscriptions. Example message from the server for updating the state:  ``` ⬇️ {     \"cmd\": \"updateDecoupledOperationStatus\",     \"subscriptionId\": number,     \"state\": <DecoupledOperationStatus> } ```
+     */
+    async websocketRaw(initOverrides) {
+        const queryParameters = {};
+        const headerParameters = {};
+        const response = await this.request({
+            path: `/websocket`,
+            method: "GET",
+            headers: headerParameters,
+            query: queryParameters,
+        }, initOverrides);
+        return new runtime.VoidApiResponse(response);
+    }
+    /**
+     * Most operations at brokerize have asynchronous effects.  For example, consider the flow of an order: when the user creates an order, it will not immediately appear in order list endpoints, because usually brokers take a few seconds until they are retrievable in those lists. Also, after a while, the order may be executed or cancelled asynchronously by the stock exchange.  A common solution for frontends would be to reload the order list regularly. However data is then either delayed or there will be many more requests than needed.  The brokerize websocket endpoint allows getting updates via web sockets. Generally speaking, clients can subscribe by assigning a subscription id and will then receive updates on that subscription.  In this documentation, ⬆️ denotes messages from the client to the server, whereas messages from server to client are marked with ⬇️.  ## authentication  When using cookies for authorization, the WebSocket connection is authenticated with the HTTP upgrade request.  If token headers are used, the _first_ message from client to server must be:  ``` ⬆️ {     \"cmd\": \"authorize\",     \"idToken\": <string> } ```  In all cases, clients must wait for the welcome message before sending other messages:  ``` ⬇️ { \"cmd\": \"authenticated\" } ```  ## ping  After 1 minute of inactivity of a client, the WebSocket connection will be considered stale and will automatically terminated. To prevent this, a ping message can be sent:  ```  ⬆️ {\"cmd\": \"ping\"} ```  The server also sends this message regularly. If no message has been received on a WebSocket connection for more than 1 minute, it should be terminated by the client.  ```  ⬇️ {\"cmd\": \"ping\"} ```  ## subscriptions  Subscriptions can be used to get invalidate events or updates for selected resources.  ### invalidate subscriptions  Invalidation events can be used for the frontend to know when reload requests via the HTTP endpoints are appropriate. Currently only invalidate events can be subscribed, the actual data must then be reloaded using the HTTP endpoints.  To set up a subscription for an invalidate event, use:  ``` ⬆️ {     \"cmd\": \"subscribe\",     \"type\": \"invalidate\",     \"subscriptionId\": 1,     \"entity: \"brokersessions\" /_* \"positions\" | \"orders\" *_/,     \"portfolioId\": 42 /_* required for \"positions\" or \"orders\" *_/ } ```  If the subscription failed to be set up on the server, an error will be sent for the subscription. This also automatically ends the subscription on the server side:  ``` ⬇️ {     \"subscriptionId\": 1,     \"error\": {         \"message\": \"Could not set up invalidation event due to...\"     } } ```  If an invalid `subscriptionId` is provided (or the subscription id is already in use by the connection), an error like this will be sent:  ``` ⬇️ {     \"error\": {         \"message\": \"Could not add subscription due to invalid subscriptionId\"     } } ```  ⚠️ _the connection will then be terminated immediately_.  If the subscription is sucessfuly set up, whenever an invalidation happens, the server will send a message like this:  ``` ⬇️ {     \"cmd\": \"invalidate\",     \"subscriptionId\": 1 } ```  When that invalidation event is received, the client should reload the data using the corresponding endpoints.  Clients can end their subscription with the `unsubscribe` command:  ``` ⬆️ {     \"cmd\": \"unsubscribe\",     \"subscriptionId\": 1 } ```  ### subscribe to the state of a decoupled operation  For decoupled operations (e.g. authorizing a session TAN using a second factor device), the state of the operation can be subscribed:  ``` ⬆️ {     \"cmd\": \"subscribe\",     \"type\": \"decoupledOperationStatus\",     \"subscriptionId\": 1,     \"sessionId\": string,     \"decoupledOperationId\": string } ```  Error handling as well as unsubscribing works as described for invalidate subscriptions. Example message from the server for updating the state:  ``` ⬇️ {     \"cmd\": \"updateDecoupledOperationStatus\",     \"subscriptionId\": number,     \"state\": <DecoupledOperationStatus> } ```
+     */
+    async websocket(initOverrides) {
+        await this.websocketRaw(initOverrides);
+    }
+}
+exports.WebsocketApi = WebsocketApi;

package/dist/cjs/swagger/apis/index.d.ts

@@ -0,0 +1,13 @@
+export * from "./AdminApi";
+export * from "./DecoupledOperationsApi";
+export * from "./DemobrokerApi";
+export * from "./ExportApi";
+export * from "./MetaApi";
+export * from "./OrderApi";
+export * from "./PortfolioApi";
+export * from "./SecuritiesApi";
+export * from "./SessionApi";
+export * from "./TradeApi";
+export * from "./TradeDraftApi";
+export * from "./UserApi";
+export * from "./WebsocketApi";

package/dist/cjs/swagger/apis/index.js

@@ -0,0 +1,31 @@
+"use strict";
+var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
+}) : (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    o[k2] = m[k];
+}));
+var __exportStar = (this && this.__exportStar) || function(m, exports) {
+    for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+/* tslint:disable */
+/* eslint-disable */
+__exportStar(require("./AdminApi"), exports);
+__exportStar(require("./DecoupledOperationsApi"), exports);
+__exportStar(require("./DemobrokerApi"), exports);
+__exportStar(require("./ExportApi"), exports);
+__exportStar(require("./MetaApi"), exports);
+__exportStar(require("./OrderApi"), exports);
+__exportStar(require("./PortfolioApi"), exports);
+__exportStar(require("./SecuritiesApi"), exports);
+__exportStar(require("./SessionApi"), exports);
+__exportStar(require("./TradeApi"), exports);
+__exportStar(require("./TradeDraftApi"), exports);
+__exportStar(require("./UserApi"), exports);
+__exportStar(require("./WebsocketApi"), exports);

package/dist/cjs/swagger/index.d.ts

@@ -0,0 +1,3 @@
+export * from "./runtime";
+export * from "./apis";
+export * from "./models";

package/dist/cjs/swagger/index.js

@@ -0,0 +1,21 @@
+"use strict";
+var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
+}) : (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    o[k2] = m[k];
+}));
+var __exportStar = (this && this.__exportStar) || function(m, exports) {
+    for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+/* tslint:disable */
+/* eslint-disable */
+__exportStar(require("./runtime"), exports);
+__exportStar(require("./apis"), exports);
+__exportStar(require("./models"), exports);

package/dist/cjs/swagger/models/AccessTokenItem.d.ts

@@ -0,0 +1,45 @@
+/**
+ * brokerize
+ * The brokerize API allows clients to implement multi-brokerage with a unified interface. For more information, visit brokerize.com
+ *
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ *
+ * @export
+ * @interface AccessTokenItem
+ */
+export interface AccessTokenItem {
+    /**
+     *
+     * @type {Date}
+     * @memberof AccessTokenItem
+     */
+    expiresAt: Date;
+    /**
+     *
+     * @type {string}
+     * @memberof AccessTokenItem
+     */
+    id: string;
+    /**
+     *
+     * @type {string}
+     * @memberof AccessTokenItem
+     */
+    name: string;
+    /**
+     *
+     * @type {Array<string>}
+     * @memberof AccessTokenItem
+     */
+    permissions: Array<string>;
+}
+export declare function AccessTokenItemFromJSON(json: any): AccessTokenItem;
+export declare function AccessTokenItemFromJSONTyped(json: any, ignoreDiscriminator: boolean): AccessTokenItem;
+export declare function AccessTokenItemToJSONRecursive(value?: AccessTokenItem | null, ignoreParent?: boolean): any;
+export declare function AccessTokenItemToJSON(value?: AccessTokenItem | null): any;

package/dist/cjs/swagger/models/AccessTokenItem.js

@@ -0,0 +1,50 @@
+"use strict";
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * brokerize
+ * The brokerize API allows clients to implement multi-brokerage with a unified interface. For more information, visit brokerize.com
+ *
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.AccessTokenItemToJSON = exports.AccessTokenItemToJSONRecursive = exports.AccessTokenItemFromJSONTyped = exports.AccessTokenItemFromJSON = void 0;
+function AccessTokenItemFromJSON(json) {
+    return AccessTokenItemFromJSONTyped(json, false);
+}
+exports.AccessTokenItemFromJSON = AccessTokenItemFromJSON;
+function AccessTokenItemFromJSONTyped(json, ignoreDiscriminator) {
+    if (json === undefined || json === null) {
+        return json;
+    }
+    return {
+        expiresAt: new Date(json["expiresAt"]),
+        id: json["id"],
+        name: json["name"],
+        permissions: json["permissions"],
+    };
+}
+exports.AccessTokenItemFromJSONTyped = AccessTokenItemFromJSONTyped;
+function AccessTokenItemToJSONRecursive(value, ignoreParent = false) {
+    if (value === undefined) {
+        return undefined;
+    }
+    if (value === null) {
+        return null;
+    }
+    return {
+        expiresAt: value.expiresAt.toISOString(),
+        id: value.id,
+        name: value.name,
+        permissions: value.permissions,
+    };
+}
+exports.AccessTokenItemToJSONRecursive = AccessTokenItemToJSONRecursive;
+function AccessTokenItemToJSON(value) {
+    return AccessTokenItemToJSONRecursive(value, false);
+}
+exports.AccessTokenItemToJSON = AccessTokenItemToJSON;

package/dist/cjs/swagger/models/AccessTokenResult.d.ts

@@ -0,0 +1,33 @@
+/**
+ * brokerize
+ * The brokerize API allows clients to implement multi-brokerage with a unified interface. For more information, visit brokerize.com
+ *
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ *
+ * @export
+ * @interface AccessTokenResult
+ */
+export interface AccessTokenResult {
+    /**
+     *
+     * @type {string}
+     * @memberof AccessTokenResult
+     */
+    id: string;
+    /**
+     *
+     * @type {string}
+     * @memberof AccessTokenResult
+     */
+    token: string;
+}
+export declare function AccessTokenResultFromJSON(json: any): AccessTokenResult;
+export declare function AccessTokenResultFromJSONTyped(json: any, ignoreDiscriminator: boolean): AccessTokenResult;
+export declare function AccessTokenResultToJSONRecursive(value?: AccessTokenResult | null, ignoreParent?: boolean): any;
+export declare function AccessTokenResultToJSON(value?: AccessTokenResult | null): any;

package/dist/cjs/swagger/models/AccessTokenResult.js

@@ -0,0 +1,46 @@
+"use strict";
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * brokerize
+ * The brokerize API allows clients to implement multi-brokerage with a unified interface. For more information, visit brokerize.com
+ *
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.AccessTokenResultToJSON = exports.AccessTokenResultToJSONRecursive = exports.AccessTokenResultFromJSONTyped = exports.AccessTokenResultFromJSON = void 0;
+function AccessTokenResultFromJSON(json) {
+    return AccessTokenResultFromJSONTyped(json, false);
+}
+exports.AccessTokenResultFromJSON = AccessTokenResultFromJSON;
+function AccessTokenResultFromJSONTyped(json, ignoreDiscriminator) {
+    if (json === undefined || json === null) {
+        return json;
+    }
+    return {
+        id: json["id"],
+        token: json["token"],
+    };
+}
+exports.AccessTokenResultFromJSONTyped = AccessTokenResultFromJSONTyped;
+function AccessTokenResultToJSONRecursive(value, ignoreParent = false) {
+    if (value === undefined) {
+        return undefined;
+    }
+    if (value === null) {
+        return null;
+    }
+    return {
+        id: value.id,
+        token: value.token,
+    };
+}
+exports.AccessTokenResultToJSONRecursive = AccessTokenResultToJSONRecursive;
+function AccessTokenResultToJSON(value) {
+    return AccessTokenResultToJSONRecursive(value, false);
+}
+exports.AccessTokenResultToJSON = AccessTokenResultToJSON;

package/dist/cjs/swagger/models/AddOAuthReturnToUrlRequest.d.ts

@@ -0,0 +1,27 @@
+/**
+ * brokerize
+ * The brokerize API allows clients to implement multi-brokerage with a unified interface. For more information, visit brokerize.com
+ *
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ *
+ * @export
+ * @interface AddOAuthReturnToUrlRequest
+ */
+export interface AddOAuthReturnToUrlRequest {
+    /**
+     *
+     * @type {string}
+     * @memberof AddOAuthReturnToUrlRequest
+     */
+    url: string;
+}
+export declare function AddOAuthReturnToUrlRequestFromJSON(json: any): AddOAuthReturnToUrlRequest;
+export declare function AddOAuthReturnToUrlRequestFromJSONTyped(json: any, ignoreDiscriminator: boolean): AddOAuthReturnToUrlRequest;
+export declare function AddOAuthReturnToUrlRequestToJSONRecursive(value?: AddOAuthReturnToUrlRequest | null, ignoreParent?: boolean): any;
+export declare function AddOAuthReturnToUrlRequestToJSON(value?: AddOAuthReturnToUrlRequest | null): any;

package/dist/cjs/swagger/models/AddOAuthReturnToUrlRequest.js

@@ -0,0 +1,44 @@
+"use strict";
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * brokerize
+ * The brokerize API allows clients to implement multi-brokerage with a unified interface. For more information, visit brokerize.com
+ *
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.AddOAuthReturnToUrlRequestToJSON = exports.AddOAuthReturnToUrlRequestToJSONRecursive = exports.AddOAuthReturnToUrlRequestFromJSONTyped = exports.AddOAuthReturnToUrlRequestFromJSON = void 0;
+function AddOAuthReturnToUrlRequestFromJSON(json) {
+    return AddOAuthReturnToUrlRequestFromJSONTyped(json, false);
+}
+exports.AddOAuthReturnToUrlRequestFromJSON = AddOAuthReturnToUrlRequestFromJSON;
+function AddOAuthReturnToUrlRequestFromJSONTyped(json, ignoreDiscriminator) {
+    if (json === undefined || json === null) {
+        return json;
+    }
+    return {
+        url: json["url"],
+    };
+}
+exports.AddOAuthReturnToUrlRequestFromJSONTyped = AddOAuthReturnToUrlRequestFromJSONTyped;
+function AddOAuthReturnToUrlRequestToJSONRecursive(value, ignoreParent = false) {
+    if (value === undefined) {
+        return undefined;
+    }
+    if (value === null) {
+        return null;
+    }
+    return {
+        url: value.url,
+    };
+}
+exports.AddOAuthReturnToUrlRequestToJSONRecursive = AddOAuthReturnToUrlRequestToJSONRecursive;
+function AddOAuthReturnToUrlRequestToJSON(value) {
+    return AddOAuthReturnToUrlRequestToJSONRecursive(value, false);
+}
+exports.AddOAuthReturnToUrlRequestToJSON = AddOAuthReturnToUrlRequestToJSON;

package/dist/cjs/swagger/models/AddOriginRequest.d.ts

@@ -0,0 +1,27 @@
+/**
+ * brokerize
+ * The brokerize API allows clients to implement multi-brokerage with a unified interface. For more information, visit brokerize.com
+ *
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ *
+ * @export
+ * @interface AddOriginRequest
+ */
+export interface AddOriginRequest {
+    /**
+     *
+     * @type {string}
+     * @memberof AddOriginRequest
+     */
+    origin: string;
+}
+export declare function AddOriginRequestFromJSON(json: any): AddOriginRequest;
+export declare function AddOriginRequestFromJSONTyped(json: any, ignoreDiscriminator: boolean): AddOriginRequest;
+export declare function AddOriginRequestToJSONRecursive(value?: AddOriginRequest | null, ignoreParent?: boolean): any;
+export declare function AddOriginRequestToJSON(value?: AddOriginRequest | null): any;

package/dist/cjs/swagger/models/AddOriginRequest.js

@@ -0,0 +1,44 @@
+"use strict";
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * brokerize
+ * The brokerize API allows clients to implement multi-brokerage with a unified interface. For more information, visit brokerize.com
+ *
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.AddOriginRequestToJSON = exports.AddOriginRequestToJSONRecursive = exports.AddOriginRequestFromJSONTyped = exports.AddOriginRequestFromJSON = void 0;
+function AddOriginRequestFromJSON(json) {
+    return AddOriginRequestFromJSONTyped(json, false);
+}
+exports.AddOriginRequestFromJSON = AddOriginRequestFromJSON;
+function AddOriginRequestFromJSONTyped(json, ignoreDiscriminator) {
+    if (json === undefined || json === null) {
+        return json;
+    }
+    return {
+        origin: json["origin"],
+    };
+}
+exports.AddOriginRequestFromJSONTyped = AddOriginRequestFromJSONTyped;
+function AddOriginRequestToJSONRecursive(value, ignoreParent = false) {
+    if (value === undefined) {
+        return undefined;
+    }
+    if (value === null) {
+        return null;
+    }
+    return {
+        origin: value.origin,
+    };
+}
+exports.AddOriginRequestToJSONRecursive = AddOriginRequestToJSONRecursive;
+function AddOriginRequestToJSON(value) {
+    return AddOriginRequestToJSONRecursive(value, false);
+}
+exports.AddOriginRequestToJSON = AddOriginRequestToJSON;

package/dist/cjs/swagger/models/AddSessionCompleteChallengeParams.d.ts

@@ -0,0 +1,33 @@
+/**
+ * brokerize
+ * The brokerize API allows clients to implement multi-brokerage with a unified interface. For more information, visit brokerize.com
+ *
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ *
+ * @export
+ * @interface AddSessionCompleteChallengeParams
+ */
+export interface AddSessionCompleteChallengeParams {
+    /**
+     *
+     * @type {string}
+     * @memberof AddSessionCompleteChallengeParams
+     */
+    challengeId: string;
+    /**
+     *
+     * @type {string}
+     * @memberof AddSessionCompleteChallengeParams
+     */
+    challengeResponse: string;
+}
+export declare function AddSessionCompleteChallengeParamsFromJSON(json: any): AddSessionCompleteChallengeParams;
+export declare function AddSessionCompleteChallengeParamsFromJSONTyped(json: any, ignoreDiscriminator: boolean): AddSessionCompleteChallengeParams;
+export declare function AddSessionCompleteChallengeParamsToJSONRecursive(value?: AddSessionCompleteChallengeParams | null, ignoreParent?: boolean): any;
+export declare function AddSessionCompleteChallengeParamsToJSON(value?: AddSessionCompleteChallengeParams | null): any;

package/dist/cjs/swagger/models/AddSessionCompleteChallengeParams.js

@@ -0,0 +1,46 @@
+"use strict";
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * brokerize
+ * The brokerize API allows clients to implement multi-brokerage with a unified interface. For more information, visit brokerize.com
+ *
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.AddSessionCompleteChallengeParamsToJSON = exports.AddSessionCompleteChallengeParamsToJSONRecursive = exports.AddSessionCompleteChallengeParamsFromJSONTyped = exports.AddSessionCompleteChallengeParamsFromJSON = void 0;
+function AddSessionCompleteChallengeParamsFromJSON(json) {
+    return AddSessionCompleteChallengeParamsFromJSONTyped(json, false);
+}
+exports.AddSessionCompleteChallengeParamsFromJSON = AddSessionCompleteChallengeParamsFromJSON;
+function AddSessionCompleteChallengeParamsFromJSONTyped(json, ignoreDiscriminator) {
+    if (json === undefined || json === null) {
+        return json;
+    }
+    return {
+        challengeId: json["challengeId"],
+        challengeResponse: json["challengeResponse"],
+    };
+}
+exports.AddSessionCompleteChallengeParamsFromJSONTyped = AddSessionCompleteChallengeParamsFromJSONTyped;
+function AddSessionCompleteChallengeParamsToJSONRecursive(value, ignoreParent = false) {
+    if (value === undefined) {
+        return undefined;
+    }
+    if (value === null) {
+        return null;
+    }
+    return {
+        challengeId: value.challengeId,
+        challengeResponse: value.challengeResponse,
+    };
+}
+exports.AddSessionCompleteChallengeParamsToJSONRecursive = AddSessionCompleteChallengeParamsToJSONRecursive;
+function AddSessionCompleteChallengeParamsToJSON(value) {
+    return AddSessionCompleteChallengeParamsToJSONRecursive(value, false);
+}
+exports.AddSessionCompleteChallengeParamsToJSON = AddSessionCompleteChallengeParamsToJSON;

package/dist/cjs/swagger/models/AddSessionParams.d.ts

@@ -0,0 +1,45 @@
+/**
+ * brokerize
+ * The brokerize API allows clients to implement multi-brokerage with a unified interface. For more information, visit brokerize.com
+ *
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ *
+ * @export
+ * @interface AddSessionParams
+ */
+export interface AddSessionParams {
+    /**
+     *
+     * @type {string}
+     * @memberof AddSessionParams
+     */
+    brokerName: string;
+    /**
+     *
+     * @type {string}
+     * @memberof AddSessionParams
+     */
+    env: string;
+    /**
+     *
+     * @type {string}
+     * @memberof AddSessionParams
+     */
+    password: string;
+    /**
+     *
+     * @type {string}
+     * @memberof AddSessionParams
+     */
+    username: string;
+}
+export declare function AddSessionParamsFromJSON(json: any): AddSessionParams;
+export declare function AddSessionParamsFromJSONTyped(json: any, ignoreDiscriminator: boolean): AddSessionParams;
+export declare function AddSessionParamsToJSONRecursive(value?: AddSessionParams | null, ignoreParent?: boolean): any;
+export declare function AddSessionParamsToJSON(value?: AddSessionParams | null): any;