@ariva-mds/mds 2.55.0 → 2.57.0

package/lib/types/models/TradingtimeByAssetDefinition.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/TradingtimeDefinition.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/TradingtimeDetails.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/TradingtimeException.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/TradingtimeInfoReply.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/TradingtimePartialException.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/WebSocketCommandAuthenticate.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/WebSocketCommandCancel.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/WebSocketCommandGetAfuCompanyProfile.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/WebSocketCommandGetFwwFundsProfile.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 WebSocketCommandGetFwwFundsProfile
+ */
+export interface WebSocketCommandGetFwwFundsProfile {
+    /**
+     * 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 WebSocketCommandGetFwwFundsProfile
+     */
+    instrumentId?: string;
+}
+/**
+ * Check if a given object implements the WebSocketCommandGetFwwFundsProfile interface.
+ */
+export declare function instanceOfWebSocketCommandGetFwwFundsProfile(value: object): boolean;
+export declare function WebSocketCommandGetFwwFundsProfileFromJSON(json: any): WebSocketCommandGetFwwFundsProfile;
+export declare function WebSocketCommandGetFwwFundsProfileFromJSONTyped(json: any, ignoreDiscriminator: boolean): WebSocketCommandGetFwwFundsProfile;
+export declare function WebSocketCommandGetFwwFundsProfileToJSON(value?: WebSocketCommandGetFwwFundsProfile | null): any;
+//# sourceMappingURL=WebSocketCommandGetFwwFundsProfile.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"WebSocketCommandGetFwwFundsProfile.d.ts","sourceRoot":"","sources":["../../../src/models/WebSocketCommandGetFwwFundsProfile.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH;;;;GAIG;AACH,MAAM,WAAW,kCAAkC;IAC/C;;;;OAIG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC;CACzB;AAED;;GAEG;AACH,wBAAgB,4CAA4C,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAInF;AAED,wBAAgB,0CAA0C,CAAC,IAAI,EAAE,GAAG,GAAG,kCAAkC,CAExG;AAED,wBAAgB,+CAA+C,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,kCAAkC,CAQ3I;AAED,wBAAgB,wCAAwC,CAAC,KAAK,CAAC,EAAE,kCAAkC,GAAG,IAAI,GAAG,GAAG,CAW/G"}

package/lib/types/models/WebSocketCommandGetInstrumentMasterdata.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/WebSocketCommandGetReference.d.ts

@@ -2,7 +2,7 @@
  * 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.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/WebSocketCommandGetSource.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/WebSocketCommandGetTradingtime.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/WebSocketCommandGetTradingtimeAnalysis.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/WebSocketCommandHeartbeat.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/WebSocketCommandListBidAskHistory.d.ts

@@ -2,7 +2,7 @@
  * 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.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/WebSocketCommandListInstrumentListings.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/WebSocketCommandListMarketstates.d.ts

@@ -0,0 +1,39 @@
+/**
+ * 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 { Quality } from './Quality';
+/**
+ *
+ * @export
+ * @interface WebSocketCommandListMarketstates
+ */
+export interface WebSocketCommandListMarketstates {
+    /**
+     *
+     * @type {Array<string>}
+     * @memberof WebSocketCommandListMarketstates
+     */
+    marketstateQueries?: Array<string>;
+    /**
+     *
+     * @type {Quality}
+     * @memberof WebSocketCommandListMarketstates
+     */
+    quality?: Quality;
+}
+/**
+ * Check if a given object implements the WebSocketCommandListMarketstates interface.
+ */
+export declare function instanceOfWebSocketCommandListMarketstates(value: object): boolean;
+export declare function WebSocketCommandListMarketstatesFromJSON(json: any): WebSocketCommandListMarketstates;
+export declare function WebSocketCommandListMarketstatesFromJSONTyped(json: any, ignoreDiscriminator: boolean): WebSocketCommandListMarketstates;
+export declare function WebSocketCommandListMarketstatesToJSON(value?: WebSocketCommandListMarketstates | null): any;
+//# sourceMappingURL=WebSocketCommandListMarketstates.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"WebSocketCommandListMarketstates.d.ts","sourceRoot":"","sources":["../../../src/models/WebSocketCommandListMarketstates.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAOzC;;;;GAIG;AACH,MAAM,WAAW,gCAAgC;IAC7C;;;;OAIG;IACH,kBAAkB,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IACnC;;;;OAIG;IACH,OAAO,CAAC,EAAE,OAAO,CAAC;CACrB;AAED;;GAEG;AACH,wBAAgB,0CAA0C,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAIjF;AAED,wBAAgB,wCAAwC,CAAC,IAAI,EAAE,GAAG,GAAG,gCAAgC,CAEpG;AAED,wBAAgB,6CAA6C,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,gCAAgC,CASvI;AAED,wBAAgB,sCAAsC,CAAC,KAAK,CAAC,EAAE,gCAAgC,GAAG,IAAI,GAAG,GAAG,CAY3G"}

package/lib/types/models/WebSocketCommandListPerformance.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/WebSocketCommandListTickHistory.d.ts

@@ -2,7 +2,7 @@
  * 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.9
+ * The version of the OpenAPI document: 0.4.34
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).