@0xmonaco/types 1.0.62 → 1.0.65

package/dist/margin-accounts/index.d.ts

@@ -230,6 +230,12 @@ export interface MarginAccountMovement {
 }
 export interface GetMarginAccountMovementsResponse {
     movements: MarginAccountMovement[];
+    /**
+     * Matching movements. Exact up to 10,000 pages of the requested page size
+     * (`pageSize` x 10,000 rows) and saturates there, so a caller with more
+     * movements than the listing can page through reads the cap, not its
+     * lifetime total. `page` is capped at 10,000.
+     */
     total: number;
     page: number;
     pageSize: number;

package/dist/positions/index.d.ts

@@ -149,6 +149,12 @@ export interface ListPositionsParams {
 }
 export interface ListPositionsResponse {
     positions: Position[];
+    /**
+     * Matching positions. Exact up to 10,000 pages of the requested page size
+     * (`pageSize` x 10,000 rows) and saturates there, so a caller with more
+     * matching positions than the listing can page through reads the cap, not
+     * its lifetime total. `page` is capped at 10,000.
+     */
     total: number;
     page: number;
     pageSize: number;
@@ -304,6 +310,12 @@ export interface PositionHistoryEvent {
 }
 export interface ListPositionHistoryResponse {
     events: PositionHistoryEvent[];
+    /**
+     * Matching position-history events. Exact up to 10,000 pages of the
+     * requested page size (`pageSize` x 10,000 rows) and saturates there, so a
+     * caller with more history than the listing can page through reads the cap,
+     * not its lifetime total. `page` is capped at 10,000.
+     */
     total: number;
     page: number;
     pageSize: number;

package/dist/profile/index.d.ts

@@ -292,14 +292,17 @@ export interface GetUserTradesResponse {
     /** Items per page */
     pageSize: number;
     /**
-     * Total number of trades.
+     * Total matching trades. In page-number mode it is exact up to
+     * `pageSize` × 10,000 rows and saturates there, so a wallet with more history
+     * than legacy mode can page through reads the cap, not its lifetime total.
      *
      * @deprecated Only populated by legacy page-number (offset) responses; 0 in
      * cursor mode, which has no exact total. Walk `nextPageToken` instead.
      */
     total: number;
     /**
-     * Total number of pages.
+     * Total pages at this `pageSize`. Exact up to 10,000 in page-number mode and
+     * saturates there, the last page legacy mode can reach.
      *
      * @deprecated Only populated by legacy page-number (offset) responses; 0 in
      * cursor mode, which has no exact total. Walk `nextPageToken` instead.

package/dist/trading/responses.d.ts

@@ -170,12 +170,13 @@ export interface GetPaginatedOrdersParams {
      * - Non-empty: an opaque cursor from a previous response's
      *   `nextPageToken`; results resume immediately after that position.
      *
-     * In either cursor-walk state (empty or non-empty), `page` is ignored, the
-     * response omits exact totals (`total`/`totalPages`/`page` are 0), and
-     * results cover full order history — hot and archived rows merged —
-     * unlike page-number mode, which only ever sees recent history. Clients
-     * that need complete order history must use the cursor form (pass `""` to
-     * start, then follow `nextPageToken`) rather than `page`.
+     * In either cursor-walk state (empty or non-empty), `page` is ignored (it
+     * comes back as 0), but `total` and `totalPages` ARE populated — bounded by
+     * the server count ceiling, see `totalCapped`. Results cover full order
+     * history — hot and archived rows merged — unlike page-number mode, which
+     * only ever sees recent history. Clients that need complete order history
+     * must use the cursor form (pass `""` to start, then follow `nextPageToken`)
+     * rather than `page`.
      */
     pageToken?: string;
 }
@@ -186,10 +187,9 @@ export interface GetPaginatedOrdersResponse {
     /** Array of historical orders from PostgreSQL (paginated) */
     orders: Order[];
     /**
-     * Total number of orders matching the query.
-     *
-     * @deprecated Only populated by legacy page-number (offset) responses; 0 in
-     * cursor mode, which has no exact total. Walk `nextPageToken` instead.
+     * Total number of orders matching the query, populated in BOTH pagination
+     * modes and bounded by the server count ceiling — see `totalCapped`. When
+     * `totalCapped` is `true` this is a lower bound (at least this many exist).
      */
     total: number;
     /**
@@ -202,10 +202,9 @@ export interface GetPaginatedOrdersResponse {
     /** Number of orders per page */
     pageSize: number;
     /**
-     * Total number of pages.
-     *
-     * @deprecated Only populated by legacy page-number (offset) responses; 0 in
-     * cursor mode, which has no exact total. Walk `nextPageToken` instead.
+     * Total number of pages at this `pageSize`, populated in BOTH pagination
+     * modes and bounded by the server count ceiling — see `totalCapped`. A lower
+     * bound when `totalCapped` is `true`.
      */
     totalPages: number;
     /**
@@ -223,6 +222,13 @@ export interface GetPaginatedOrdersResponse {
      * history.
      */
     nextPageToken: string;
+    /**
+     * `true` when MORE than the server ceiling of orders matched, so the count
+     * stopped at the ceiling and `total` / `totalPages` are a lower bound (more
+     * than `total` orders exist). `false` when `total` is the exact count —
+     * including exactly the ceiling, which is still reported exactly.
+     */
+    totalCapped: boolean;
 }
 /**
  * Response from getting a single order by ID
@@ -550,6 +556,12 @@ export interface ConditionalOrder {
 }
 export interface ListConditionalOrdersResponse {
     orders: ConditionalOrder[];
+    /**
+     * Matching conditional orders. Exact up to 10,000 pages of the requested
+     * page size (`pageSize` x 10,000 rows) and saturates there, so a caller with
+     * more matching conditional orders than the listing can page through reads
+     * the cap, not its lifetime total. `page` is capped at 10,000.
+     */
     total: number;
     page: number;
     pageSize: number;
@@ -818,7 +830,12 @@ export interface ListTwapOrdersParams {
  */
 export interface ListTwapOrdersResponse {
     orders: TwapOrder[];
-    /** Total number of TWAP orders matching the filter */
+    /**
+     * Matching TWAP orders. Exact up to 10,000 pages of the requested page size
+     * (`pageSize` x 10,000 rows) and saturates there, so a caller with more
+     * matching TWAP orders than the listing can page through reads the cap, not
+     * its lifetime total. `page` is capped at 10,000.
+     */
     total: number;
     /** Current page number */
     page: number;

package/dist/websocket/events/instrument-events.d.ts

@@ -18,6 +18,10 @@
  * Perp-only fields (`maxLeverage`, `initialMarginRate`, `maintenanceMarginRate`)
  * are optional and omitted on the wire for spot markets, which have no leverage
  * or margin parameters. All numeric quantities are decimal strings.
+ *
+ * Every frame (snapshot and live) carries `baseIconUrl` and `quoteIconUrl` for
+ * the market's two assets, each `null` when that asset has no icon configured,
+ * so a client can render a position's asset icons from the instrument row alone.
  */
 /**
  * The kind of instrument change a frame reports.
@@ -65,6 +69,20 @@ export interface InstrumentEventData {
     marketType: string;
     /** Asset-class category, e.g. "crypto", "equities", "commodities" */
     category: string;
+    /**
+     * Base asset icon URL, or `null` when the asset has no icon configured.
+     * The server sends this on every market (spot and perp) as an explicit `null`
+     * when absent, unlike the perp-only fields that are omitted — but the property
+     * is declared **optional** so that adding it stays a non-breaking change for
+     * code that constructs or mocks this shape. Never a synthesized URL. Join a
+     * position's `tradingPairId` to this row to render the icon without a REST call.
+     */
+    baseIconUrl?: string | null;
+    /**
+     * Quote asset icon URL, or `null` when the asset has no icon configured. See
+     * {@link InstrumentEventData.baseIconUrl}.
+     */
+    quoteIconUrl?: string | null;
     /** Maximum leverage (decimal string). Perp-only; omitted for spot. */
     maxLeverage?: string;
     /** Initial margin rate (decimal string). Perp-only; omitted for spot. */

package/dist/websocket/events/instrument-events.js

@@ -18,4 +18,8 @@
  * Perp-only fields (`maxLeverage`, `initialMarginRate`, `maintenanceMarginRate`)
  * are optional and omitted on the wire for spot markets, which have no leverage
  * or margin parameters. All numeric quantities are decimal strings.
+ *
+ * Every frame (snapshot and live) carries `baseIconUrl` and `quoteIconUrl` for
+ * the market's two assets, each `null` when that asset has no icon configured,
+ * so a client can render a position's asset icons from the instrument row alone.
  */

package/dist/wire/schema.d.ts

@@ -4624,7 +4624,11 @@ export interface components {
         };
         GetMarginAccountMovementsResponse: {
             movements?: components["schemas"]["MarginAccountMovement"][] | null;
-            /** Format: uint32 */
+            /**
+             * Format: uint32
+             * @description Matching movements. Exact up to 10,000 pages of the requested page size (page_size x 10,000 rows) and saturates there, so a caller with more movements than the listing can page through reads the cap, not its lifetime total.
+             * @example 150
+             */
             total?: number | null;
             /** Format: uint32 */
             page?: number | null;
@@ -5882,13 +5886,13 @@ export interface components {
             pageSize?: string | null;
             /**
              * @deprecated
-             * @description Deprecated: total number of trades (legacy offset mode only; 0 in cursor mode)
+             * @description Deprecated: total matching trades (legacy page-number mode only; 0 in cursor mode). Exact up to pageSize x 10,000 rows and saturates there. Use pageToken cursor pagination instead.
              * @example 150
              */
             total?: string | null;
             /**
              * @deprecated
-             * @description Deprecated: total number of pages (legacy offset mode only; 0 in cursor mode)
+             * @description Deprecated: total pages at this pageSize (legacy page-number mode only; 0 in cursor mode). Exact up to 10,000 and saturates there. Use pageToken cursor pagination instead.
              * @example 8
              */
             totalPages?: string | null;
@@ -6213,7 +6217,11 @@ export interface components {
         };
         ListConditionalOrdersResponse: {
             orders?: components["schemas"]["ConditionalOrder"][] | null;
-            /** Format: uint32 */
+            /**
+             * Format: uint32
+             * @description Matching conditional orders. Exact up to 10,000 pages of the requested page size (page_size x 10,000 rows) and saturates there, so a caller with more matching conditional orders than the listing can page through reads the cap, not its lifetime total.
+             * @example 3
+             */
             total?: number | null;
             /** Format: uint32 */
             page?: number | null;
@@ -6288,8 +6296,7 @@ export interface components {
             orders?: components["schemas"]["GetOrderResponse"][] | null;
             /**
              * Format: uint32
-             * @deprecated
-             * @description Deprecated: total number of orders matching the filter (legacy offset mode only; 0 in cursor mode)
+             * @description Total number of orders matching the filter, populated in both pagination modes; bounded by the server ceiling — a lower bound when totalCapped is true.
              * @example 150
              */
             total?: number | null;
@@ -6308,8 +6315,7 @@ export interface components {
             pageSize?: number | null;
             /**
              * Format: uint32
-             * @deprecated
-             * @description Deprecated: total number of pages (legacy offset mode only; 0 in cursor mode)
+             * @description Total number of pages at this pageSize, populated in both pagination modes; bounded by the server ceiling — a lower bound when totalCapped is true.
              * @example 8
              */
             totalPages?: number | null;
@@ -6329,6 +6335,11 @@ export interface components {
              *      means page-number mode does not participate in cursor continuation.
              */
             nextPageToken?: string | null;
+            /**
+             * @description True when more than the server ceiling of orders matched, so the count stopped at the ceiling and total/totalPages are a lower bound (more than total exist). False when total is the exact count, including exactly the ceiling.
+             * @example false
+             */
+            totalCapped?: boolean | null;
         };
         ListPendingWithdrawalsResponse: {
             withdrawals?: components["schemas"]["PendingWithdrawal"][] | null;
@@ -6359,7 +6370,11 @@ export interface components {
         };
         ListPositionHistoryResponse: {
             events?: components["schemas"]["PositionHistoryEvent"][] | null;
-            /** Format: uint32 */
+            /**
+             * Format: uint32
+             * @description Matching position-history events. Exact up to 10,000 pages of the requested page size (page_size x 10,000 rows) and saturates there, so a caller with more history than the listing can page through reads the cap, not its lifetime total.
+             * @example 150
+             */
             total?: number | null;
             /** Format: uint32 */
             page?: number | null;
@@ -6368,7 +6383,11 @@ export interface components {
         };
         ListPositionsResponse: {
             positions?: components["schemas"]["Position"][] | null;
-            /** Format: uint32 */
+            /**
+             * Format: uint32
+             * @description Matching positions. Exact up to 10,000 pages of the requested page size (page_size x 10,000 rows) and saturates there, so a caller with more matching positions than the listing can page through reads the cap, not its lifetime total.
+             * @example 150
+             */
             total?: number | null;
             /** Format: uint32 */
             page?: number | null;
@@ -6416,7 +6435,7 @@ export interface components {
             orders?: components["schemas"]["TwapOrder"][] | null;
             /**
              * Format: uint32
-             * @description Total number of TWAP orders matching the filter
+             * @description Matching TWAP orders. Exact up to 10,000 pages of the requested page size (page_size x 10,000 rows) and saturates there, so a caller with more matching TWAP orders than the listing can page through reads the cap, not its lifetime total.
              * @example 3
              */
             total?: number | null;
@@ -12650,13 +12669,14 @@ export interface operations {
                  *       - Non-empty: an opaque cursor from a previous response's
                  *         `next_page_token`; results resume immediately after that position.
                  *
-                 *      In either cursor-walk state (empty or non-empty), `page` is ignored, the
-                 *      response omits exact totals (total/total_pages/page are 0), and results
-                 *      cover full order history — hot and archived rows merged — unlike
-                 *      page-number mode, which only ever sees recent history. Clients that need
-                 *      complete order history must use the cursor form (start with an empty
-                 *      string, then follow next_page_token) rather than `page`. Filters and
-                 *      orderBy must match the request that produced the token.
+                 *      In either cursor-walk state (empty or non-empty), `page` is ignored (it
+                 *      comes back as 0), but `total` and `total_pages` ARE populated — bounded by
+                 *      the server count ceiling, see `total_capped`. Results cover full order
+                 *      history — hot and archived rows merged — unlike page-number mode, which
+                 *      only ever sees recent history. Clients that need complete order history
+                 *      must use the cursor form (start with an empty string, then follow
+                 *      next_page_token) rather than `page`. Filters and orderBy must match the
+                 *      request that produced the token.
                  */
                 pageToken?: string;
             };

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@0xmonaco/types",
-	"version": "1.0.62",
+	"version": "1.0.65",
 	"type": "module",
 	"homepage": "https://docs.0xmonaco.com/sdk/typescript",
 	"main": "./dist/index.js",
@@ -16,7 +16,7 @@
 		"lint": "biome lint ."
 	},
 	"dependencies": {
-		"@0xmonaco/contracts": "1.0.62",
+		"@0xmonaco/contracts": "1.0.65",
 		"zod": "^4.1.12"
 	},
 	"peerDependencies": {