@ariva-mds/mds 2.56.0 → 2.58.0

package/lib/types/models/BidAskTimeseriesAllOf.d.ts

@@ -0,0 +1,40 @@
+/**
+ * MDS API
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *
+ * The version of the OpenAPI document: 0.4.34
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import type { BidAskTimeseriesItem } from './BidAskTimeseriesItem';
+import type { Resolution } from './Resolution';
+/**
+ *
+ * @export
+ * @interface BidAskTimeseriesAllOf
+ */
+export interface BidAskTimeseriesAllOf {
+    /**
+     *
+     * @type {Resolution}
+     * @memberof BidAskTimeseriesAllOf
+     */
+    resolution?: Resolution;
+    /**
+     *
+     * @type {Array<BidAskTimeseriesItem>}
+     * @memberof BidAskTimeseriesAllOf
+     */
+    items?: Array<BidAskTimeseriesItem>;
+}
+/**
+ * Check if a given object implements the BidAskTimeseriesAllOf interface.
+ */
+export declare function instanceOfBidAskTimeseriesAllOf(value: object): boolean;
+export declare function BidAskTimeseriesAllOfFromJSON(json: any): BidAskTimeseriesAllOf;
+export declare function BidAskTimeseriesAllOfFromJSONTyped(json: any, ignoreDiscriminator: boolean): BidAskTimeseriesAllOf;
+export declare function BidAskTimeseriesAllOfToJSON(value?: BidAskTimeseriesAllOf | null): any;
+//# sourceMappingURL=BidAskTimeseriesAllOf.d.ts.map

package/lib/types/models/BidAskTimeseriesAllOf.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"BidAskTimeseriesAllOf.d.ts","sourceRoot":"","sources":["../../../src/models/BidAskTimeseriesAllOf.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,wBAAwB,CAAC;AAMnE,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,cAAc,CAAC;AAO/C;;;;GAIG;AACH,MAAM,WAAW,qBAAqB;IAClC;;;;OAIG;IACH,UAAU,CAAC,EAAE,UAAU,CAAC;IACxB;;;;OAIG;IACH,KAAK,CAAC,EAAE,KAAK,CAAC,oBAAoB,CAAC,CAAC;CACvC;AAED;;GAEG;AACH,wBAAgB,+BAA+B,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAItE;AAED,wBAAgB,6BAA6B,CAAC,IAAI,EAAE,GAAG,GAAG,qBAAqB,CAE9E;AAED,wBAAgB,kCAAkC,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,qBAAqB,CASjH;AAED,wBAAgB,2BAA2B,CAAC,KAAK,CAAC,EAAE,qBAAqB,GAAG,IAAI,GAAG,GAAG,CAYrF"}

package/lib/types/models/BidAskTimeseriesItem.d.ts

@@ -0,0 +1,51 @@
+/**
+ * MDS API
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *
+ * The version of the OpenAPI document: 0.4.34
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ * The time-series-specific bid/ask item data for an instrument
+ * @export
+ * @interface BidAskTimeseriesItem
+ */
+export interface BidAskTimeseriesItem {
+    /**
+     * Timestamp
+     * @type {string}
+     * @memberof BidAskTimeseriesItem
+     * @deprecated
+     */
+    time?: string;
+    /**
+     * Timestamp
+     * @type {Date}
+     * @memberof BidAskTimeseriesItem
+     */
+    datetime?: Date;
+    /**
+     * Bid value
+     * @type {number}
+     * @memberof BidAskTimeseriesItem
+     */
+    bid?: number;
+    /**
+     * Ask value
+     * @type {number}
+     * @memberof BidAskTimeseriesItem
+     */
+    ask?: number;
+}
+/**
+ * Check if a given object implements the BidAskTimeseriesItem interface.
+ */
+export declare function instanceOfBidAskTimeseriesItem(value: object): boolean;
+export declare function BidAskTimeseriesItemFromJSON(json: any): BidAskTimeseriesItem;
+export declare function BidAskTimeseriesItemFromJSONTyped(json: any, ignoreDiscriminator: boolean): BidAskTimeseriesItem;
+export declare function BidAskTimeseriesItemToJSON(value?: BidAskTimeseriesItem | null): any;
+//# sourceMappingURL=BidAskTimeseriesItem.d.ts.map

package/lib/types/models/BidAskTimeseriesItem.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"BidAskTimeseriesItem.d.ts","sourceRoot":"","sources":["../../../src/models/BidAskTimeseriesItem.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH;;;;GAIG;AACH,MAAM,WAAW,oBAAoB;IACjC;;;;;OAKG;IACH,IAAI,CAAC,EAAE,MAAM,CAAC;IACd;;;;OAIG;IACH,QAAQ,CAAC,EAAE,IAAI,CAAC;IAChB;;;;OAIG;IACH,GAAG,CAAC,EAAE,MAAM,CAAC;IACb;;;;OAIG;IACH,GAAG,CAAC,EAAE,MAAM,CAAC;CAChB;AAED;;GAEG;AACH,wBAAgB,8BAA8B,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAIrE;AAED,wBAAgB,4BAA4B,CAAC,IAAI,EAAE,GAAG,GAAG,oBAAoB,CAE5E;AAED,wBAAgB,iCAAiC,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,oBAAoB,CAW/G;AAED,wBAAgB,0BAA0B,CAAC,KAAK,CAAC,EAAE,oBAAoB,GAAG,IAAI,GAAG,GAAG,CAcnF"}

package/lib/types/models/ChartData.d.ts

@@ -0,0 +1,85 @@
+/**
+ * MDS API
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *
+ * The version of the OpenAPI document: 0.4.34
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import type { DayMarkData } from './DayMarkData';
+import type { Resolution } from './Resolution';
+import type { TimeseriesData } from './TimeseriesData';
+import type { Tradingtime } from './Tradingtime';
+/**
+ * Represents chart-specific data for an instrument.
+ * @export
+ * @interface ChartData
+ */
+export interface ChartData {
+    /**
+     * Id for the Marketstate of an Instrument that is listed on a Source. <p> Format: InstrumentId "," ListingVariant "," Source <p>InstrumentId: The InstrumentID in one of the defined formats, see  <a href="#model-InstrumentId">InstrumentId</a></p> <p>ListingVariant: Normally the listing variant is only determined by the trading currency, in that case the ListingVariant is named after the Currency (e.g. EUR). But other variant types might be possible!</p> <p>Source: The Source or Exchange. </p>
+     * <p> Any MarketstateId is also a valid MarketstateQuery.</bold></p>
+     * @type {string}
+     * @memberof ChartData
+     */
+    marketstateId?: string;
+    /**
+     * ID for one instrument, ie. a stock or an index. This will be the highest ranked available identifier for this instrument from the following list: <p>- ISIN: DE0007100000 <br>- Currency: CURRENCY(EUR/USD) <br>- EUREX-Option: EUREXO(DE000710000000,C,3000,1222) </p>
+     * @type {string}
+     * @memberof ChartData
+     */
+    instrumentId?: string;
+    /**
+     * Source
+     * @type {string}
+     * @memberof ChartData
+     */
+    sourceId?: string;
+    /**
+     * if an instrument is listed eg. in multiple currencies on one exchange then the information in this field is used to discriminate between them.
+     * @type {string}
+     * @memberof ChartData
+     */
+    currency?: string;
+    /**
+     * if an instrument is listed eg. in multiple currencies on one exchange then the information in this field is used to discriminate between them.
+     * @type {string}
+     * @memberof ChartData
+     */
+    listingVariant?: string;
+    /**
+     *
+     * @type {Resolution}
+     * @memberof ChartData
+     */
+    resolution?: Resolution;
+    /**
+     *
+     * @type {DayMarkData}
+     * @memberof ChartData
+     */
+    close?: DayMarkData;
+    /**
+     *
+     * @type {Tradingtime}
+     * @memberof ChartData
+     */
+    tradingTimes?: Tradingtime;
+    /**
+     *
+     * @type {Array<TimeseriesData>}
+     * @memberof ChartData
+     */
+    items?: Array<TimeseriesData>;
+}
+/**
+ * Check if a given object implements the ChartData interface.
+ */
+export declare function instanceOfChartData(value: object): boolean;
+export declare function ChartDataFromJSON(json: any): ChartData;
+export declare function ChartDataFromJSONTyped(json: any, ignoreDiscriminator: boolean): ChartData;
+export declare function ChartDataToJSON(value?: ChartData | null): any;
+//# sourceMappingURL=ChartData.d.ts.map

package/lib/types/models/ChartData.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ChartData.d.ts","sourceRoot":"","sources":["../../../src/models/ChartData.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,eAAe,CAAC;AAMjD,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,cAAc,CAAC;AAM/C,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,kBAAkB,CAAC;AAMvD,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,eAAe,CAAC;AAOjD;;;;GAIG;AACH,MAAM,WAAW,SAAS;IACtB;;;;;OAKG;IACH,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB;;;;OAIG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB;;;;OAIG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB;;;;OAIG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB;;;;OAIG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB;;;;OAIG;IACH,UAAU,CAAC,EAAE,UAAU,CAAC;IACxB;;;;OAIG;IACH,KAAK,CAAC,EAAE,WAAW,CAAC;IACpB;;;;OAIG;IACH,YAAY,CAAC,EAAE,WAAW,CAAC;IAC3B;;;;OAIG;IACH,KAAK,CAAC,EAAE,KAAK,CAAC,cAAc,CAAC,CAAC;CACjC;AAED;;GAEG;AACH,wBAAgB,mBAAmB,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAI1D;AAED,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,GAAG,GAAG,SAAS,CAEtD;AAED,wBAAgB,sBAAsB,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,SAAS,CAgBzF;AAED,wBAAgB,eAAe,CAAC,KAAK,CAAC,EAAE,SAAS,GAAG,IAAI,GAAG,GAAG,CAmB7D"}

package/lib/types/models/ChartDataAllOf.d.ts

@@ -0,0 +1,54 @@
+/**
+ * MDS API
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *
+ * The version of the OpenAPI document: 0.4.34
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import type { DayMarkData } from './DayMarkData';
+import type { Resolution } from './Resolution';
+import type { TimeseriesData } from './TimeseriesData';
+import type { Tradingtime } from './Tradingtime';
+/**
+ *
+ * @export
+ * @interface ChartDataAllOf
+ */
+export interface ChartDataAllOf {
+    /**
+     *
+     * @type {Resolution}
+     * @memberof ChartDataAllOf
+     */
+    resolution?: Resolution;
+    /**
+     *
+     * @type {DayMarkData}
+     * @memberof ChartDataAllOf
+     */
+    close?: DayMarkData;
+    /**
+     *
+     * @type {Tradingtime}
+     * @memberof ChartDataAllOf
+     */
+    tradingTimes?: Tradingtime;
+    /**
+     *
+     * @type {Array<TimeseriesData>}
+     * @memberof ChartDataAllOf
+     */
+    items?: Array<TimeseriesData>;
+}
+/**
+ * Check if a given object implements the ChartDataAllOf interface.
+ */
+export declare function instanceOfChartDataAllOf(value: object): boolean;
+export declare function ChartDataAllOfFromJSON(json: any): ChartDataAllOf;
+export declare function ChartDataAllOfFromJSONTyped(json: any, ignoreDiscriminator: boolean): ChartDataAllOf;
+export declare function ChartDataAllOfToJSON(value?: ChartDataAllOf | null): any;
+//# sourceMappingURL=ChartDataAllOf.d.ts.map

package/lib/types/models/ChartDataAllOf.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ChartDataAllOf.d.ts","sourceRoot":"","sources":["../../../src/models/ChartDataAllOf.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,eAAe,CAAC;AAMjD,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,cAAc,CAAC;AAM/C,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,kBAAkB,CAAC;AAMvD,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,eAAe,CAAC;AAOjD;;;;GAIG;AACH,MAAM,WAAW,cAAc;IAC3B;;;;OAIG;IACH,UAAU,CAAC,EAAE,UAAU,CAAC;IACxB;;;;OAIG;IACH,KAAK,CAAC,EAAE,WAAW,CAAC;IACpB;;;;OAIG;IACH,YAAY,CAAC,EAAE,WAAW,CAAC;IAC3B;;;;OAIG;IACH,KAAK,CAAC,EAAE,KAAK,CAAC,cAAc,CAAC,CAAC;CACjC;AAED;;GAEG;AACH,wBAAgB,wBAAwB,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAI/D;AAED,wBAAgB,sBAAsB,CAAC,IAAI,EAAE,GAAG,GAAG,cAAc,CAEhE;AAED,wBAAgB,2BAA2B,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,cAAc,CAWnG;AAED,wBAAgB,oBAAoB,CAAC,KAAK,CAAC,EAAE,cAAc,GAAG,IAAI,GAAG,GAAG,CAcvE"}

package/lib/types/models/ContinuationToken.d.ts

@@ -1,8 +1,8 @@
 /**
  * MDS API
- *  Please note the following definitions used throughout this API.<p> **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments. <p> **Instrument**: An instrument  is e.g. a stock, a bond,  an index, a currency-pair or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types, ...), Fundamental stock data, News, ... <p> **Listing**: An instrument can be traded/calculated on multiple Sources. Some sources even support multiple listings of the same instrument (for example in different currencies). A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data, ... <p> **Instrument** **vs** **Listing**: The Microsoft stock is an Instrument identified by  the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these Listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX) or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade und quote informations ...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the Listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**:  Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed.  However depending on Source and context some events can refer to a whole trading day without specifying a time of day. E.g. ECB currency rates are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges.  If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. I you see  \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately the swagger-ui does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" http request-header as described above.<p> **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
  *
- * The version of the OpenAPI document: 0.9
+ * The version of the OpenAPI document: 0.4.34
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/lib/types/models/DayMarkData.d.ts

@@ -1,8 +1,8 @@
 /**
  * MDS API
- *  Please note the following definitions used throughout this API.<p> **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments. <p> **Instrument**: An instrument  is e.g. a stock, a bond,  an index, a currency-pair or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types, ...), Fundamental stock data, News, ... <p> **Listing**: An instrument can be traded/calculated on multiple Sources. Some sources even support multiple listings of the same instrument (for example in different currencies). A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data, ... <p> **Instrument** **vs** **Listing**: The Microsoft stock is an Instrument identified by  the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these Listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX) or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade und quote informations ...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the Listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**:  Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed.  However depending on Source and context some events can refer to a whole trading day without specifying a time of day. E.g. ECB currency rates are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges.  If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. I you see  \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately the swagger-ui does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" http request-header as described above.<p> **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
  *
- * The version of the OpenAPI document: 0.9
+ * The version of the OpenAPI document: 0.4.34
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/lib/types/models/DayMarkDataEod.d.ts

@@ -1,8 +1,8 @@
 /**
  * MDS API
- *  Please note the following definitions used throughout this API.<p> **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments. <p> **Instrument**: An instrument  is e.g. a stock, a bond,  an index, a currency-pair or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types, ...), Fundamental stock data, News, ... <p> **Listing**: An instrument can be traded/calculated on multiple Sources. Some sources even support multiple listings of the same instrument (for example in different currencies). A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data, ... <p> **Instrument** **vs** **Listing**: The Microsoft stock is an Instrument identified by  the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these Listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX) or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade und quote informations ...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the Listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**:  Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed.  However depending on Source and context some events can refer to a whole trading day without specifying a time of day. E.g. ECB currency rates are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges.  If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. I you see  \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately the swagger-ui does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" http request-header as described above.<p> **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
  *
- * The version of the OpenAPI document: 0.9
+ * The version of the OpenAPI document: 0.4.34
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/lib/types/models/EodExtract.d.ts

@@ -1,8 +1,8 @@
 /**
  * MDS API
- *  Please note the following definitions used throughout this API.<p> **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments. <p> **Instrument**: An instrument  is e.g. a stock, a bond,  an index, a currency-pair or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types, ...), Fundamental stock data, News, ... <p> **Listing**: An instrument can be traded/calculated on multiple Sources. Some sources even support multiple listings of the same instrument (for example in different currencies). A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data, ... <p> **Instrument** **vs** **Listing**: The Microsoft stock is an Instrument identified by  the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these Listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX) or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade und quote informations ...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the Listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**:  Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed.  However depending on Source and context some events can refer to a whole trading day without specifying a time of day. E.g. ECB currency rates are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges.  If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. I you see  \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately the swagger-ui does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" http request-header as described above.<p> **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
  *
- * The version of the OpenAPI document: 0.9
+ * The version of the OpenAPI document: 0.4.34
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/lib/types/models/EodExtractWithId.d.ts

@@ -1,8 +1,8 @@
 /**
  * MDS API
- *  Please note the following definitions used throughout this API.<p> **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments. <p> **Instrument**: An instrument  is e.g. a stock, a bond,  an index, a currency-pair or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types, ...), Fundamental stock data, News, ... <p> **Listing**: An instrument can be traded/calculated on multiple Sources. Some sources even support multiple listings of the same instrument (for example in different currencies). A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data, ... <p> **Instrument** **vs** **Listing**: The Microsoft stock is an Instrument identified by  the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these Listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX) or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade und quote informations ...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the Listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**:  Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed.  However depending on Source and context some events can refer to a whole trading day without specifying a time of day. E.g. ECB currency rates are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges.  If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. I you see  \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately the swagger-ui does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" http request-header as described above.<p> **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
  *
- * The version of the OpenAPI document: 0.9
+ * The version of the OpenAPI document: 0.4.34
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/lib/types/models/FeedsAfuCompanyInitialLoadGet200Response.d.ts

@@ -1,8 +1,8 @@
 /**
  * MDS API
- *  Please note the following definitions used throughout this API.<p> **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments. <p> **Instrument**: An instrument  is e.g. a stock, a bond,  an index, a currency-pair or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types, ...), Fundamental stock data, News, ... <p> **Listing**: An instrument can be traded/calculated on multiple Sources. Some sources even support multiple listings of the same instrument (for example in different currencies). A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data, ... <p> **Instrument** **vs** **Listing**: The Microsoft stock is an Instrument identified by  the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these Listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX) or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade und quote informations ...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the Listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**:  Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed.  However depending on Source and context some events can refer to a whole trading day without specifying a time of day. E.g. ECB currency rates are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges.  If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. I you see  \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately the swagger-ui does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" http request-header as described above.<p> **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
  *
- * The version of the OpenAPI document: 0.9
+ * The version of the OpenAPI document: 0.4.34
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/lib/types/models/FeedsFwwFundsInitialLoadGet200Response.d.ts

@@ -0,0 +1,32 @@
+/**
+ * MDS API
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *
+ * The version of the OpenAPI document: 0.4.34
+ *
+ *
+ * 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 FeedsFwwFundsInitialLoadGet200Response
+ */
+export interface FeedsFwwFundsInitialLoadGet200Response {
+    /**
+     * Token to fetch the next part of data
+     * @type {string}
+     * @memberof FeedsFwwFundsInitialLoadGet200Response
+     */
+    continuationToken: string;
+}
+/**
+ * Check if a given object implements the FeedsFwwFundsInitialLoadGet200Response interface.
+ */
+export declare function instanceOfFeedsFwwFundsInitialLoadGet200Response(value: object): boolean;
+export declare function FeedsFwwFundsInitialLoadGet200ResponseFromJSON(json: any): FeedsFwwFundsInitialLoadGet200Response;
+export declare function FeedsFwwFundsInitialLoadGet200ResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): FeedsFwwFundsInitialLoadGet200Response;
+export declare function FeedsFwwFundsInitialLoadGet200ResponseToJSON(value?: FeedsFwwFundsInitialLoadGet200Response | null): any;
+//# sourceMappingURL=FeedsFwwFundsInitialLoadGet200Response.d.ts.map

package/lib/types/models/FeedsFwwFundsInitialLoadGet200Response.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"FeedsFwwFundsInitialLoadGet200Response.d.ts","sourceRoot":"","sources":["../../../src/models/FeedsFwwFundsInitialLoadGet200Response.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAUH;;;;GAIG;AACH,MAAM,WAAW,sCAAsC;IACnD;;;;OAIG;IACH,iBAAiB,EAAE,MAAM,CAAC;CAC7B;AAED;;GAEG;AACH,wBAAgB,gDAAgD,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAKvF;AAED,wBAAgB,8CAA8C,CAAC,IAAI,EAAE,GAAG,GAAG,sCAAsC,CAEhH;AAED,wBAAgB,mDAAmD,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,sCAAsC,CAQnJ;AAED,wBAAgB,4CAA4C,CAAC,KAAK,CAAC,EAAE,sCAAsC,GAAG,IAAI,GAAG,GAAG,CAWvH"}

package/lib/types/models/FeedsListingsSourceIdInitialLoadGet200Response.d.ts

@@ -1,8 +1,8 @@
 /**
  * MDS API
- *  Please note the following definitions used throughout this API.<p> **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments. <p> **Instrument**: An instrument  is e.g. a stock, a bond,  an index, a currency-pair or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types, ...), Fundamental stock data, News, ... <p> **Listing**: An instrument can be traded/calculated on multiple Sources. Some sources even support multiple listings of the same instrument (for example in different currencies). A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data, ... <p> **Instrument** **vs** **Listing**: The Microsoft stock is an Instrument identified by  the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these Listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX) or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade und quote informations ...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the Listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**:  Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed.  However depending on Source and context some events can refer to a whole trading day without specifying a time of day. E.g. ECB currency rates are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges.  If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. I you see  \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately the swagger-ui does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" http request-header as described above.<p> **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
  *
- * The version of the OpenAPI document: 0.9
+ * The version of the OpenAPI document: 0.4.34
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/lib/types/models/FeedsMarketstatesSourceIdInitialLoadGet200Response.d.ts

@@ -1,8 +1,8 @@
 /**
  * MDS API
- *  Please note the following definitions used throughout this API.<p> **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments. <p> **Instrument**: An instrument  is e.g. a stock, a bond,  an index, a currency-pair or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types, ...), Fundamental stock data, News, ... <p> **Listing**: An instrument can be traded/calculated on multiple Sources. Some sources even support multiple listings of the same instrument (for example in different currencies). A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data, ... <p> **Instrument** **vs** **Listing**: The Microsoft stock is an Instrument identified by  the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these Listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX) or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade und quote informations ...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the Listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**:  Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed.  However depending on Source and context some events can refer to a whole trading day without specifying a time of day. E.g. ECB currency rates are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges.  If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. I you see  \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately the swagger-ui does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" http request-header as described above.<p> **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
  *
- * The version of the OpenAPI document: 0.9
+ * The version of the OpenAPI document: 0.4.34
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/lib/types/models/FeedsMarketstatesSourceIdInitialLoadGet200Response.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"FeedsMarketstatesSourceIdInitialLoadGet200Response.d.ts","sourceRoot":"","sources":["../../../src/models/FeedsMarketstatesSourceIdInitialLoadGet200Response.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AASH,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,eAAe,CAAC;AAMjD,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,oBAAoB,CAAC;AAM3D,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,mBAAmB,CAAC;AAYzD,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,eAAe,CAAC;AAMjD,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAMzC,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,iBAAiB,CAAC;AAMrD,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,UAAU,CAAC;AAMvC,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,SAAS,CAAC;AAOrC;;;;GAIG;AACH,MAAM,WAAW,kDAAkD;IAC/D;;;;;OAKG;IACH,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB;;;;OAIG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB;;;;OAIG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB;;;;OAIG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB;;;;OAIG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB;;;;OAIG;IACH,aAAa,CAAC,EAAE,aAAa,CAAC;IAC9B;;;;OAIG;IACH,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB;;;;OAIG;IACH,IAAI,CAAC,EAAE,eAAe,CAAC;IACvB;;;;OAIG;IACH,GAAG,CAAC,EAAE,gBAAgB,CAAC;IACvB;;;;OAIG;IACH,GAAG,CAAC,EAAE,gBAAgB,CAAC;IACvB;;;;OAIG;IACH,SAAS,CAAC,EAAE,gBAAgB,CAAC;IAC7B;;;;OAIG;IACH,SAAS,CAAC,EAAE,gBAAgB,CAAC;IAC7B;;;;OAIG;IACH,IAAI,CAAC,EAAE,WAAW,CAAC;IACnB;;;;OAIG;IACH,IAAI,CAAC,EAAE,WAAW,CAAC;IACnB;;;;OAIG;IACH,GAAG,CAAC,EAAE,WAAW,CAAC;IAClB;;;;OAIG;IACH,KAAK,CAAC,EAAE,WAAW,CAAC;IACpB;;;;OAIG;IACH,UAAU,CAAC,EAAE,WAAW,CAAC;IACzB;;;;OAIG;IACH,aAAa,CAAC,EAAE,WAAW,CAAC;IAC5B;;;;OAIG;IACH,aAAa,CAAC,EAAE,WAAW,CAAC;IAC5B;;;;OAIG;IACH,qBAAqB,CAAC,EAAE,WAAW,CAAC;IACpC;;;;OAIG;IACH,QAAQ,CAAC,EAAE,WAAW,CAAC;IACvB;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,WAAW,CAAC;IAC/B;;;;OAIG;IACH,QAAQ,CAAC,EAAE,WAAW,CAAC;IACvB;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,WAAW,CAAC;IAC/B;;;;OAIG;IACH,WAAW,CAAC,EAAE,WAAW,CAAC;IAC1B;;;;OAIG;IACH,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB;;;;OAIG;IACH,KAAK,CAAC,EAAE,KAAK,CAAC;IACd;;;;OAIG;IACH,iBAAiB,EAAE,MAAM,CAAC;CAC7B;AAED;;GAEG;AACH,wBAAgB,4DAA4D,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAKnG;AAED,wBAAgB,0DAA0D,CAAC,IAAI,EAAE,GAAG,GAAG,kDAAkD,CAExI;AAED,wBAAgB,+DAA+D,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,kDAAkD,CAmC3K;AAED,wBAAgB,wDAAwD,CAAC,KAAK,CAAC,EAAE,kDAAkD,GAAG,IAAI,GAAG,GAAG,CAmC/I"}
+{"version":3,"file":"FeedsMarketstatesSourceIdInitialLoadGet200Response.d.ts","sourceRoot":"","sources":["../../../src/models/FeedsMarketstatesSourceIdInitialLoadGet200Response.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AASH,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,eAAe,CAAC;AAMjD,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,oBAAoB,CAAC;AAM3D,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,mBAAmB,CAAC;AAYzD,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,eAAe,CAAC;AAMjD,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAMzC,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,iBAAiB,CAAC;AAMrD,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,UAAU,CAAC;AAMvC,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,SAAS,CAAC;AAOrC;;;;GAIG;AACH,MAAM,WAAW,kDAAkD;IAC/D;;;;;OAKG;IACH,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB;;;;OAIG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB;;;;OAIG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB;;;;OAIG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB;;;;OAIG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB;;;;OAIG;IACH,aAAa,CAAC,EAAE,aAAa,CAAC;IAC9B;;;;OAIG;IACH,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB;;;;OAIG;IACH,IAAI,CAAC,EAAE,eAAe,CAAC;IACvB;;;;OAIG;IACH,GAAG,CAAC,EAAE,gBAAgB,CAAC;IACvB;;;;OAIG;IACH,GAAG,CAAC,EAAE,gBAAgB,CAAC;IACvB;;;;OAIG;IACH,SAAS,CAAC,EAAE,gBAAgB,CAAC;IAC7B;;;;OAIG;IACH,SAAS,CAAC,EAAE,gBAAgB,CAAC;IAC7B;;;;OAIG;IACH,IAAI,CAAC,EAAE,WAAW,CAAC;IACnB;;;;OAIG;IACH,IAAI,CAAC,EAAE,WAAW,CAAC;IACnB;;;;OAIG;IACH,GAAG,CAAC,EAAE,WAAW,CAAC;IAClB;;;;OAIG;IACH,KAAK,CAAC,EAAE,WAAW,CAAC;IACpB;;;;OAIG;IACH,UAAU,CAAC,EAAE,WAAW,CAAC;IACzB;;;;OAIG;IACH,aAAa,CAAC,EAAE,WAAW,CAAC;IAC5B;;;;OAIG;IACH,aAAa,CAAC,EAAE,WAAW,CAAC;IAC5B;;;;OAIG;IACH,qBAAqB,CAAC,EAAE,WAAW,CAAC;IACpC;;;;OAIG;IACH,QAAQ,CAAC,EAAE,WAAW,CAAC;IACvB;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,WAAW,CAAC;IAC/B;;;;OAIG;IACH,QAAQ,CAAC,EAAE,WAAW,CAAC;IACvB;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,WAAW,CAAC;IAC/B;;;;OAIG;IACH,WAAW,CAAC,EAAE,WAAW,CAAC;IAC1B;;;;OAIG;IACH,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB;;;;OAIG;IACH,KAAK,CAAC,EAAE,KAAK,CAAC;IACd;;;;OAIG;IACH,iBAAiB,EAAE,MAAM,CAAC;CAC7B;AAED;;GAEG;AACH,wBAAgB,4DAA4D,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAKnG;AAED,wBAAgB,0DAA0D,CAAC,IAAI,EAAE,GAAG,GAAG,kDAAkD,CAExI;AAED,wBAAgB,+DAA+D,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,kDAAkD,CAmC3K;AAED,wBAAgB,wDAAwD,CAAC,KAAK,CAAC,EAAE,kDAAkD,GAAG,IAAI,GAAG,GAAG,CAsC/I"}

package/lib/types/models/FeedsMasterdataInitialLoadGet200Response.d.ts

@@ -1,8 +1,8 @@
 /**
  * MDS API
- *  Please note the following definitions used throughout this API.<p> **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments. <p> **Instrument**: An instrument  is e.g. a stock, a bond,  an index, a currency-pair or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types, ...), Fundamental stock data, News, ... <p> **Listing**: An instrument can be traded/calculated on multiple Sources. Some sources even support multiple listings of the same instrument (for example in different currencies). A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data, ... <p> **Instrument** **vs** **Listing**: The Microsoft stock is an Instrument identified by  the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these Listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX) or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade und quote informations ...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the Listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**:  Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed.  However depending on Source and context some events can refer to a whole trading day without specifying a time of day. E.g. ECB currency rates are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges.  If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. I you see  \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately the swagger-ui does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" http request-header as described above.<p> **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
  *
- * The version of the OpenAPI document: 0.9
+ * The version of the OpenAPI document: 0.4.34
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/lib/types/models/IdFieldsInstrument.d.ts

@@ -1,8 +1,8 @@
 /**
  * MDS API
- *  Please note the following definitions used throughout this API.<p> **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments. <p> **Instrument**: An instrument  is e.g. a stock, a bond,  an index, a currency-pair or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types, ...), Fundamental stock data, News, ... <p> **Listing**: An instrument can be traded/calculated on multiple Sources. Some sources even support multiple listings of the same instrument (for example in different currencies). A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data, ... <p> **Instrument** **vs** **Listing**: The Microsoft stock is an Instrument identified by  the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these Listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX) or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade und quote informations ...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the Listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**:  Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed.  However depending on Source and context some events can refer to a whole trading day without specifying a time of day. E.g. ECB currency rates are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges.  If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. I you see  \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately the swagger-ui does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" http request-header as described above.<p> **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
+ *  Please note the following definitions used throughout this API:  **Source**: A source can be any kind of marketplace (exchange) or an entity that calculates prices/values for instruments.  **Instrument**: An instrument is e.g. a stock, a bond, an index, a currency-pair, or a specific future/option contract. An instrument is identified by an InstrumentId. Some information in MDS is linked to instruments: Masterdata (names, instrument types,...), Fundamental stock data, News,...  **Listing**: An instrument can be traded/calculated on multiple sources. Some sources even support multiple listings of the same instrument, e.g. lisings in different currencies. A listing is identified by a MarketstateId. Most information in MDS is linked to listings: Marketstate (prices/quotes), Tickdata (price/quote history), Performance data,...  **Instrument** **vs** **Listing**: The Microsoft stock is an instrument identified by the InstrumentId \"US5949181045\". It is listed and traded on many exchanges. Each of these listings is identified by a unique MarketstateId, i.e. \"US5949181045@GAT\" (listing on Tradegate) or \"US5949181045,USD@SIX\" (USD-listing on SIX), or \"US5949181045,CHF@SIX\" (CHF-listing on SIX).  **Marketstate** defines the current state of an instrument listed on a source. In our case besides open, close, post and pre market also latest trade and quote information...  **MarketstateQuery**: When you request a price/quote in MDS, you have to select the listing(s) you wish to receive them for. Most API calls use a MarketstateQuery as a parameter to express a filter for one or more Marketstates. The query often takes the form of \"DE0007100000@ETR\" and can also utilize wildcards like \"*\" or \"?\". <br> See here for a full specification <a href=\"#model-MarketstateQuery\">MarketstateQuery</a>  **Timestamps**: Most events covered in MDS have a known instant they refer to. A trade on an exchange usually has an exact time when it was executed. However depending on source and context some events can refer to a whole trading day without specifying a time of day. ECB currency rates for instance are determined for the whole day. In other cases an exact time is not part of the licensed data, e.g. when looking at the end-of-day quality of some exchanges. If an exact time is known, this is transmitted in a field \"datetime\". If only a date is given the field \"date\" is used. If you see \"00:00:00.000\" in a datetime field, this actually means something happened exactly at midnight, it is not a special value indicating \\\"no date available\\\".  **SSE-NOTE**: Many endpoints support Server Sent Events (SSE) to get pushed updates. To receive SSE the client needs to request the content-type \"text/event-stream\" via the \"accept\" http request-header. <br>Unfortunately Swagger UI does not support SSE! To test SSE on an endpoint use the curl command shown in the snapshot response and modify the \"accept\" HTTP request-header as described above.  **CURL-NOTE**: When use curl use the option -i to see the response headers. If the return status is 401 then you have to reauthorize. Otherwise you do not see whether the token is expired and wondering that there is no response.
  *
- * The version of the OpenAPI document: 0.9
+ * The version of the OpenAPI document: 0.4.34
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).