@mywebapi.com/sdk 0.1.0

package/dist/generated/model/mT4SymbolInfoApiResponse.d.ts

@@ -0,0 +1,42 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+import type { MT4SymbolInfo } from './mT4SymbolInfo';
+/**
+ * Unified v2 response envelope: data is the payload (null on error); error is the
+ * error object (null on success, always serialised); meta contains response metadata
+ * (activityId and optional paging). HTTP status is always 200.
+ */
+export interface MT4SymbolInfoApiResponse {
+    /**
+       * v2 DTO describing a single symbol's market data and metadata as held in
+       * the wrapper's pumping cache. Curated subset of the wrapper's SymbolInfo:
+       * covers what clients monitoring tick feeds / building a quote panel
+       * actually need — current Bid/Ask, session High/Low, tick precision
+       * (Digits, Point), current Spread (in points), last-tick direction, and
+       * the last-tick timestamp. Internal bookkeeping (Count, UpdateFlag,
+       * Visible, SpreadBalance, Commission, CommType) is intentionally omitted:
+       * those are pump-side cache mechanics or broker-side commission config
+       * that don't belong on a real-time market-data wire.
+       */
+    data?: MT4SymbolInfo | null;
+    /**
+       * v2 error body. Code is the stable transport error code; ManagerCode is the raw MT4
+       * ResultCode (serialized as a string for a known enum member, or as a number for an
+       * unrecognised value returned by MT4); Message is a human-readable description.
+       */
+    error?: ApiError | null;
+    /**
+       * Response metadata. ActivityId is the W3C trace-id for correlation in Seq/SigNoz.
+       * Paging is present only on paginated list responses; otherwise it is omitted —
+       * the global JSON context policy serialises null fields, so we override that here
+       * with System.Text.Json.Serialization.JsonIgnoreCondition.WhenWritingNull.
+       */
+    meta?: ApiMeta | null;
+}

package/dist/generated/model/mT4SymbolInfoListApiResponse.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+import type { MT4SymbolInfo } from './mT4SymbolInfo';
+/**
+ * Unified v2 response envelope: data is the payload (null on error); error is the
+ * error object (null on success, always serialised); meta contains response metadata
+ * (activityId and optional paging). HTTP status is always 200.
+ */
+export interface MT4SymbolInfoListApiResponse {
+    /** @nullable */
+    data?: MT4SymbolInfo[] | null;
+    /**
+       * v2 error body. Code is the stable transport error code; ManagerCode is the raw MT4
+       * ResultCode (serialized as a string for a known enum member, or as a number for an
+       * unrecognised value returned by MT4); Message is a human-readable description.
+       */
+    error?: ApiError | null;
+    /**
+       * Response metadata. ActivityId is the W3C trace-id for correlation in Seq/SigNoz.
+       * Paging is present only on paginated list responses; otherwise it is omitted —
+       * the global JSON context policy serialises null fields, so we override that here
+       * with System.Text.Json.Serialization.JsonIgnoreCondition.WhenWritingNull.
+       */
+    meta?: ApiMeta | null;
+}

package/dist/generated/model/mT4SymbolSession.d.ts

@@ -0,0 +1,23 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+/**
+ * v2 DTO for one open/close session window. The wrapper stores three of these
+ * per direction (Quote/Trade) per weekday — see CPlugin.SaaSWebApps.WebAPI.DTOs.MT4.v2.MT4SymbolDaySessions.
+ * All four time components are server-local (the wrapper itself has no
+ * timezone — the trading server's clock is the reference frame).
+ */
+export interface MT4SymbolSession {
+    /** Session opens at this hour (0–23) */
+    openHour?: number;
+    /** Session opens at this minute (0–59) */
+    openMinute?: number;
+    /** Session closes at this hour (0–23) */
+    closeHour?: number;
+    /** Session closes at this minute (0–59) */
+    closeMinute?: number;
+}

package/dist/generated/model/mT4Sync.d.ts

@@ -0,0 +1,41 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { SynchronizationMode } from './synchronizationMode';
+/**
+ * v2 DTO for a single MT4 chart-history synchronization rule. Curated
+ * subset of the wrapper's ConSync — drops the Reserved padding, the
+ * Next pointer chain, the unused port slot, AND the `Password`
+ * field (replication credentials to the upstream sync source).
+ */
+export interface MT4Sync {
+    /**
+       * Upstream sync server address (used as cursor key)
+       * @nullable
+       */
+    server?: string | null;
+    /**
+       * Replication login (upstream credential identifier)
+       * @nullable
+       */
+    login?: string | null;
+    /** Enable flag (0 = disabled, 1 = enabled — raw wrapper int) */
+    enable?: number;
+    /** Synchronization mode (Add / Update / Insert — wrapper enum) */
+    mode?: SynchronizationMode;
+    /** Sync range start (negative = whole chart) */
+    from?: number;
+    /** Sync range end (negative = whole chart) */
+    to?: number;
+    /**
+       * Comma-separated list of symbols to synchronize
+       * @nullable
+       */
+    securities?: string | null;
+    /** Time correction in minutes applied to incoming bars */
+    timeCorrection?: number;
+}

package/dist/generated/model/mT4SyncApiResponse.d.ts

@@ -0,0 +1,37 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+import type { MT4Sync } from './mT4Sync';
+/**
+ * Unified v2 response envelope: data is the payload (null on error); error is the
+ * error object (null on success, always serialised); meta contains response metadata
+ * (activityId and optional paging). HTTP status is always 200.
+ */
+export interface MT4SyncApiResponse {
+    /**
+       * v2 DTO for a single MT4 chart-history synchronization rule. Curated
+       * subset of the wrapper's ConSync — drops the Reserved padding, the
+       * Next pointer chain, the unused port slot, AND the `Password`
+       * field (replication credentials to the upstream sync source).
+       */
+    data?: MT4Sync | null;
+    /**
+       * v2 error body. Code is the stable transport error code; ManagerCode is the raw MT4
+       * ResultCode (serialized as a string for a known enum member, or as a number for an
+       * unrecognised value returned by MT4); Message is a human-readable description.
+       */
+    error?: ApiError | null;
+    /**
+       * Response metadata. ActivityId is the W3C trace-id for correlation in Seq/SigNoz.
+       * Paging is present only on paginated list responses; otherwise it is omitted —
+       * the global JSON context policy serialises null fields, so we override that here
+       * with System.Text.Json.Serialization.JsonIgnoreCondition.WhenWritingNull.
+       */
+    meta?: ApiMeta | null;
+}

package/dist/generated/model/mT4SyncListApiResponse.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+import type { MT4Sync } from './mT4Sync';
+/**
+ * Unified v2 response envelope: data is the payload (null on error); error is the
+ * error object (null on success, always serialised); meta contains response metadata
+ * (activityId and optional paging). HTTP status is always 200.
+ */
+export interface MT4SyncListApiResponse {
+    /** @nullable */
+    data?: MT4Sync[] | null;
+    /**
+       * v2 error body. Code is the stable transport error code; ManagerCode is the raw MT4
+       * ResultCode (serialized as a string for a known enum member, or as a number for an
+       * unrecognised value returned by MT4); Message is a human-readable description.
+       */
+    error?: ApiError | null;
+    /**
+       * Response metadata. ActivityId is the W3C trace-id for correlation in Seq/SigNoz.
+       * Paging is present only on paginated list responses; otherwise it is omitted —
+       * the global JSON context policy serialises null fields, so we override that here
+       * with System.Text.Json.Serialization.JsonIgnoreCondition.WhenWritingNull.
+       */
+    meta?: ApiMeta | null;
+}

package/dist/generated/model/mT4TickInfo.d.ts

@@ -0,0 +1,28 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+/**
+ * v2 DTO describing the last known tick for a trading symbol. Pump-cached
+ * snapshot of bid/ask quote — for sub-second updates, prefer the SignalR
+ * tick stream over polling this endpoint. The wrapper's `TickInfo`
+ * has no additional fields; the curated DTO is 1:1 on field semantics
+ * with the wrapper, only the timestamp source field is renamed for
+ * readability (`Ctm` → `Time`).
+ */
+export interface MT4TickInfo {
+    /**
+       * Symbol the tick applies to (e.g. "EURUSD")
+       * @nullable
+       */
+    symbol?: string | null;
+    /** Server-side tick timestamp (UTC) */
+    time?: string;
+    /** Bid price (best price at which the broker is buying) */
+    bid?: number;
+    /** Ask price (best price at which the broker is selling) */
+    ask?: number;
+}

package/dist/generated/model/mT4TickInfoApiResponse.d.ts

@@ -0,0 +1,39 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+import type { MT4TickInfo } from './mT4TickInfo';
+/**
+ * Unified v2 response envelope: data is the payload (null on error); error is the
+ * error object (null on success, always serialised); meta contains response metadata
+ * (activityId and optional paging). HTTP status is always 200.
+ */
+export interface MT4TickInfoApiResponse {
+    /**
+       * v2 DTO describing the last known tick for a trading symbol. Pump-cached
+       * snapshot of bid/ask quote — for sub-second updates, prefer the SignalR
+       * tick stream over polling this endpoint. The wrapper's `TickInfo`
+       * has no additional fields; the curated DTO is 1:1 on field semantics
+       * with the wrapper, only the timestamp source field is renamed for
+       * readability (`Ctm` → `Time`).
+       */
+    data?: MT4TickInfo | null;
+    /**
+       * v2 error body. Code is the stable transport error code; ManagerCode is the raw MT4
+       * ResultCode (serialized as a string for a known enum member, or as a number for an
+       * unrecognised value returned by MT4); Message is a human-readable description.
+       */
+    error?: ApiError | null;
+    /**
+       * Response metadata. ActivityId is the W3C trace-id for correlation in Seq/SigNoz.
+       * Paging is present only on paginated list responses; otherwise it is omitted —
+       * the global JSON context policy serialises null fields, so we override that here
+       * with System.Text.Json.Serialization.JsonIgnoreCondition.WhenWritingNull.
+       */
+    meta?: ApiMeta | null;
+}

package/dist/generated/model/mT4TickInfoListApiResponse.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+import type { MT4TickInfo } from './mT4TickInfo';
+/**
+ * Unified v2 response envelope: data is the payload (null on error); error is the
+ * error object (null on success, always serialised); meta contains response metadata
+ * (activityId and optional paging). HTTP status is always 200.
+ */
+export interface MT4TickInfoListApiResponse {
+    /** @nullable */
+    data?: MT4TickInfo[] | null;
+    /**
+       * v2 error body. Code is the stable transport error code; ManagerCode is the raw MT4
+       * ResultCode (serialized as a string for a known enum member, or as a number for an
+       * unrecognised value returned by MT4); Message is a human-readable description.
+       */
+    error?: ApiError | null;
+    /**
+       * Response metadata. ActivityId is the W3C trace-id for correlation in Seq/SigNoz.
+       * Paging is present only on paginated list responses; otherwise it is omitted —
+       * the global JSON context policy serialises null fields, so we override that here
+       * with System.Text.Json.Serialization.JsonIgnoreCondition.WhenWritingNull.
+       */
+    meta?: ApiMeta | null;
+}

package/dist/generated/model/mT4TickRecord.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+/**
+ * v2 DTO for one historical tick from `TicksRequest`. Same fields as the
+ * wrapper's `TickRecord`; `Ctm` is renamed to `Time` at the API
+ * boundary (consistent with CPlugin.SaaSWebApps.WebAPI.DTOs.MT4.v2.MT4TickInfo). The wrapper's
+ * `TickRequestFlags` enum is exposed as a string to avoid the leaf-enum
+ * nested-generic serialization issue documented in feedback-stj-enum-leaf-nested.
+ */
+export interface MT4TickRecord {
+    /** Server-side tick timestamp (UTC) */
+    time?: string;
+    /** Bid price */
+    bid?: number;
+    /** Ask price */
+    ask?: number;
+    /** Index of the data feed source */
+    dataFeed?: number;
+    /**
+       * Tick flags as string — combination of `Raw`, `Normal`, `All`.
+       * String-typed for the same STJ source-gen reason as CPlugin.SaaSWebApps.WebAPI.DTOs.MT4.v2.MT4ServerLog.Code.
+       * @nullable
+       */
+    flags?: string | null;
+}

package/dist/generated/model/mT4TickRecordListApiResponse.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+import type { MT4TickRecord } from './mT4TickRecord';
+/**
+ * Unified v2 response envelope: data is the payload (null on error); error is the
+ * error object (null on success, always serialised); meta contains response metadata
+ * (activityId and optional paging). HTTP status is always 200.
+ */
+export interface MT4TickRecordListApiResponse {
+    /** @nullable */
+    data?: MT4TickRecord[] | null;
+    /**
+       * v2 error body. Code is the stable transport error code; ManagerCode is the raw MT4
+       * ResultCode (serialized as a string for a known enum member, or as a number for an
+       * unrecognised value returned by MT4); Message is a human-readable description.
+       */
+    error?: ApiError | null;
+    /**
+       * Response metadata. ActivityId is the W3C trace-id for correlation in Seq/SigNoz.
+       * Paging is present only on paginated list responses; otherwise it is omitted —
+       * the global JSON context policy serialises null fields, so we override that here
+       * with System.Text.Json.Serialization.JsonIgnoreCondition.WhenWritingNull.
+       */
+    meta?: ApiMeta | null;
+}

package/dist/generated/model/mT4Trade.d.ts

@@ -0,0 +1,83 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { ActivationType } from './activationType';
+import type { TradeCommand } from './tradeCommand';
+import type { TradeRecordReason } from './tradeRecordReason';
+import type { TradeRecordState } from './tradeRecordState';
+/**
+ * v2 DTO mirroring the wrapper's TradeRecord. The set of fields is curated
+ * for typical client use-cases — order monitoring, P&L reporting, trade
+ * history reconciliation. Internal padding/reserved/gateway-internal/raw
+ * underscore-prefixed fields are intentionally excluded. Span<>-typed
+ * helpers (ConvRates, ConvReserv, APIData) are excluded because System.Text.Json
+ * cannot serialize ref-struct-backed properties — those would force callers
+ * onto a custom converter for marginal value.
+ * Enum members (TradeCommand, TradeRecordState, TradeRecordReason,
+ * ActivationType) serialize as string names via V2JsonContext
+ * UseStringEnumConverter — e.g. "Buy" rather than 0.
+ */
+export interface MT4Trade {
+    /** Order ticket number */
+    order?: number;
+    /** Owner account login */
+    login?: number;
+    /**
+       * Symbol traded (e.g. EURUSD)
+       * @nullable
+       */
+    symbol?: string | null;
+    /** Symbol precision (number of digits after the decimal point) */
+    digits?: number;
+    /** Trade direction / pending order type (Buy/Sell/BuyLimit/etc) */
+    tradeCommand?: TradeCommand;
+    /** Volume stored ×100 (e.g. 15 means 0.15 lots — see VolumeLots) */
+    volume?: number;
+    /** Volume expressed in lots, for human consumption (Volume / 100) */
+    volumeLots?: number;
+    /** Lifecycle state of the trade record */
+    tradeRecordState?: TradeRecordState;
+    /** Price at which the order was opened */
+    openPrice?: number;
+    /** Stop-loss price (0 if unset) */
+    sl?: number;
+    /** Take-profit price (0 if unset) */
+    tp?: number;
+    /** Order open timestamp */
+    openTime?: string;
+    /** Order close timestamp (default for still-open orders) */
+    closeTime?: string;
+    /** Price at which the order was closed */
+    closePrice?: number;
+    /** Broker commission */
+    commission?: number;
+    /** Agent (IB) commission */
+    commissionAgent?: number;
+    /** Accumulated swap / rollover charges */
+    storage?: number;
+    /** Realised / floating profit */
+    profit?: number;
+    /** Taxes withheld */
+    taxes?: number;
+    /** Expert advisor magic number — client-supplied tag */
+    magic?: number;
+    /**
+       * Free-form order comment
+       * @nullable
+       */
+    comment?: string | null;
+    /** Expiration timestamp for pending orders */
+    expiration?: string;
+    /** Reason the trade record was created/modified (Client/Expert/Dealer/Stopout/etc) */
+    tradeRecordReason?: TradeRecordReason;
+    /** How a pending order was activated */
+    activationType?: ActivationType;
+    /** Last modification timestamp of the trade record */
+    timeStamp?: string;
+    /** Margin conversion rate (margin currency → deposit currency) */
+    marginRate?: number;
+}

package/dist/generated/model/mT4TradeApiResponse.d.ts

@@ -0,0 +1,43 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+import type { MT4Trade } from './mT4Trade';
+/**
+ * Unified v2 response envelope: data is the payload (null on error); error is the
+ * error object (null on success, always serialised); meta contains response metadata
+ * (activityId and optional paging). HTTP status is always 200.
+ */
+export interface MT4TradeApiResponse {
+    /**
+       * v2 DTO mirroring the wrapper's TradeRecord. The set of fields is curated
+       * for typical client use-cases — order monitoring, P&L reporting, trade
+       * history reconciliation. Internal padding/reserved/gateway-internal/raw
+       * underscore-prefixed fields are intentionally excluded. Span<>-typed
+       * helpers (ConvRates, ConvReserv, APIData) are excluded because System.Text.Json
+       * cannot serialize ref-struct-backed properties — those would force callers
+       * onto a custom converter for marginal value.
+       * Enum members (TradeCommand, TradeRecordState, TradeRecordReason,
+       * ActivationType) serialize as string names via V2JsonContext
+       * UseStringEnumConverter — e.g. "Buy" rather than 0.
+       */
+    data?: MT4Trade | null;
+    /**
+       * v2 error body. Code is the stable transport error code; ManagerCode is the raw MT4
+       * ResultCode (serialized as a string for a known enum member, or as a number for an
+       * unrecognised value returned by MT4); Message is a human-readable description.
+       */
+    error?: ApiError | null;
+    /**
+       * Response metadata. ActivityId is the W3C trace-id for correlation in Seq/SigNoz.
+       * Paging is present only on paginated list responses; otherwise it is omitted —
+       * the global JSON context policy serialises null fields, so we override that here
+       * with System.Text.Json.Serialization.JsonIgnoreCondition.WhenWritingNull.
+       */
+    meta?: ApiMeta | null;
+}

package/dist/generated/model/mT4TradeListApiResponse.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+import type { MT4Trade } from './mT4Trade';
+/**
+ * Unified v2 response envelope: data is the payload (null on error); error is the
+ * error object (null on success, always serialised); meta contains response metadata
+ * (activityId and optional paging). HTTP status is always 200.
+ */
+export interface MT4TradeListApiResponse {
+    /** @nullable */
+    data?: MT4Trade[] | null;
+    /**
+       * v2 error body. Code is the stable transport error code; ManagerCode is the raw MT4
+       * ResultCode (serialized as a string for a known enum member, or as a number for an
+       * unrecognised value returned by MT4); Message is a human-readable description.
+       */
+    error?: ApiError | null;
+    /**
+       * Response metadata. ActivityId is the W3C trace-id for correlation in Seq/SigNoz.
+       * Paging is present only on paginated list responses; otherwise it is omitted —
+       * the global JSON context policy serialises null fields, so we override that here
+       * with System.Text.Json.Serialization.JsonIgnoreCondition.WhenWritingNull.
+       */
+    meta?: ApiMeta | null;
+}

package/dist/generated/model/mT4TradeRestoreInput.d.ts

@@ -0,0 +1,54 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { TradeCommand } from './tradeCommand';
+/**
+ * v2 narrow input DTO for `BackupRestoreOrders`. Carries the trade
+ * identity + economic state that a disaster-recovery flow needs.
+ */
+export interface MT4TradeRestoreInput {
+    /** Order ticket (the input array position is the binding key for the result) */
+    order?: number;
+    /** Owner's login */
+    login?: number;
+    /**
+       * Symbol (e.g. `EURUSD`; max 12 ASCII chars on the wrapper side)
+       * @nullable
+       */
+    symbol?: string | null;
+    /** Trade command (buy / sell / pending / balance / etc.) */
+    tradeCommand?: TradeCommand;
+    /** Volume in 1/100 lots (15 = 0.15 lot) */
+    volume?: number;
+    /** Open price */
+    openPrice?: number;
+    /** Stop loss */
+    sl?: number;
+    /** Take profit */
+    tp?: number;
+    /** Close price (0 for still-open trades) */
+    closePrice?: number;
+    /** Trade profit/loss */
+    profit?: number;
+    /** Swap (rollover charge) */
+    storage?: number;
+    /** Commission */
+    commission?: number;
+    /** Open time (UTC) */
+    openTime?: string;
+    /** Close time (UTC; default for still-open) */
+    closeTime?: string;
+    /** Expiration time (UTC; default for non-pending orders) */
+    expiration?: string;
+    /** Magic number (EA identifier) */
+    magic?: number;
+    /**
+       * Free-form comment (max ~31 ASCII chars on the wrapper side)
+       * @nullable
+       */
+    comment?: string | null;
+}

package/dist/generated/model/mT4TradeRestoreResult.d.ts

@@ -0,0 +1,18 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+/**
+ * v2 DTO for a single per-order result of a backup-restore operation.
+ * Mirrors the wrapper's `TradeRestoreResult` — order ticket plus
+ * a 1-byte status flag.
+ */
+export interface MT4TradeRestoreResult {
+    /** Order ticket from the input array (matches by position) */
+    order?: number;
+    /** Per-order restore status: `0` = error, `1` = restored */
+    res?: number;
+}

package/dist/generated/model/mT4TradeRestoreResultListApiResponse.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+import type { MT4TradeRestoreResult } from './mT4TradeRestoreResult';
+/**
+ * Unified v2 response envelope: data is the payload (null on error); error is the
+ * error object (null on success, always serialised); meta contains response metadata
+ * (activityId and optional paging). HTTP status is always 200.
+ */
+export interface MT4TradeRestoreResultListApiResponse {
+    /** @nullable */
+    data?: MT4TradeRestoreResult[] | null;
+    /**
+       * v2 error body. Code is the stable transport error code; ManagerCode is the raw MT4
+       * ResultCode (serialized as a string for a known enum member, or as a number for an
+       * unrecognised value returned by MT4); Message is a human-readable description.
+       */
+    error?: ApiError | null;
+    /**
+       * Response metadata. ActivityId is the W3C trace-id for correlation in Seq/SigNoz.
+       * Paging is present only on paginated list responses; otherwise it is omitted —
+       * the global JSON context policy serialises null fields, so we override that here
+       * with System.Text.Json.Serialization.JsonIgnoreCondition.WhenWritingNull.
+       */
+    meta?: ApiMeta | null;
+}