@mywebapi.com/sdk 0.1.0

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

@@ -0,0 +1,38 @@
+/**
+ * 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 { MT4MarginLevel } from './mT4MarginLevel';
+/**
+ * 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 MT4MarginLevelApiResponse {
+    /**
+       * v2 DTO mirroring the wrapper's MarginLevel record. All fields are kept
+       * because clients monitoring margin call / stop-out conditions need the
+       * complete state. ControllingType and LevelType remain as MT4 enums and
+       * serialize as string names via the V2JsonContext UseStringEnumConverter
+       * option (e.g. "Percent" rather than 0).
+       */
+    data?: MT4MarginLevel | 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/mT4MarginLevelListApiResponse.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 { MT4MarginLevel } from './mT4MarginLevel';
+/**
+ * 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 MT4MarginLevelListApiResponse {
+    /** @nullable */
+    data?: MT4MarginLevel[] | 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/mT4NewsSendRequest.d.ts

@@ -0,0 +1,31 @@
+/**
+ * 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 request DTO for `POST NewsSend` — pushes a single news item
+ * to the MT4 server, which fans it out to all connected client
+ * terminals. Wrapper signature: `ResultCode NewsSend(NewsTopic news)`.
+ */
+export interface MT4NewsSendRequest {
+    /**
+       * News headline (required, up to 256 chars)
+       * @nullable
+       */
+    topic?: string | null;
+    /**
+       * News category (optional, up to 64 chars)
+       * @nullable
+       */
+    category?: string | null;
+    /**
+       * News body text (required)
+       * @nullable
+       */
+    body?: string | null;
+    /** High-priority flag (`true` = priority 1, `false` = priority 0) */
+    highPriority?: boolean;
+}

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

@@ -0,0 +1,53 @@
+/**
+ * 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 a single news topic header as held in the wrapper's
+ * pumping cache. Curated subset of the wrapper's NewsTopic: enough to render
+ * a list / browse view of broker-distributed news (Key for follow-up
+ * NewsBodyGet / NewsBodyRequest, Time, Topic, Category, Keywords, Priority,
+ * LangId). The wrapper's `Body` property is intentionally excluded —
+ * it is x86-only at the unmanaged layer (the MT4 ManagerAPI lays out the
+ * body pointer as a 32-bit field and the wrapper throws
+ * System.PlatformNotSupportedException on x64) and is fetched
+ * separately via `NewsBodyGet(key)`.
+ */
+export interface MT4NewsTopic {
+    /**
+       * News key — the identifier used by `NewsBodyGet` and
+       * `NewsBodyRequest` to fetch the body for this topic.
+       */
+    key?: number;
+    /** Published time of the news topic (UTC). */
+    time?: string;
+    /**
+       * News headline / subject (max 256 chars at the wrapper layer).
+       * @nullable
+       */
+    topic?: string | null;
+    /**
+       * News category. Slash-separated path on the wrapper side (e.g.
+       * "Markets\Asian Markets News") used by the MT4 client terminal to
+       * build a tree view. Max 64 chars at the wrapper layer.
+       * @nullable
+       */
+    category?: string | null;
+    /**
+       * Comma-separated keyword list (max 256 chars). Used by quote-feed
+       * brokers as a symbol filter — for example `"!EURUSD, EUR*"`
+       * selects all EUR pairs except EURUSD.
+       * @nullable
+       */
+    keywords?: string | null;
+    /** News priority: 0 = general, 1 = high. */
+    priority?: number;
+    /**
+       * Windows LCID language id. 0 means unspecified; otherwise the low
+       * 16 bits of a Windows LCID (the language portion).
+       */
+    langId?: number;
+}

package/dist/generated/model/mT4NewsTopicApiResponse.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 { MT4NewsTopic } from './mT4NewsTopic';
+/**
+ * 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 MT4NewsTopicApiResponse {
+    /**
+       * v2 DTO describing a single news topic header as held in the wrapper's
+       * pumping cache. Curated subset of the wrapper's NewsTopic: enough to render
+       * a list / browse view of broker-distributed news (Key for follow-up
+       * NewsBodyGet / NewsBodyRequest, Time, Topic, Category, Keywords, Priority,
+       * LangId). The wrapper's `Body` property is intentionally excluded —
+       * it is x86-only at the unmanaged layer (the MT4 ManagerAPI lays out the
+       * body pointer as a 32-bit field and the wrapper throws
+       * System.PlatformNotSupportedException on x64) and is fetched
+       * separately via `NewsBodyGet(key)`.
+       */
+    data?: MT4NewsTopic | 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/mT4NewsTopicListApiResponse.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 { MT4NewsTopic } from './mT4NewsTopic';
+/**
+ * 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 MT4NewsTopicListApiResponse {
+    /** @nullable */
+    data?: MT4NewsTopic[] | 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/mT4NotificationsSendRequest.d.ts

@@ -0,0 +1,29 @@
+/**
+ * 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
+ */
+/**
+ * Request body for the v2 `NotificationsSend` admin endpoint —
+ * pushes a single message to one or more MT4 clients identified by
+ * account login. Maps onto the wrapper's
+ * `NotificationsSend2(int[] logins, string message)`.
+ */
+export interface MT4NotificationsSendRequest {
+    /**
+       * Account logins to deliver the notification to (server-side fan-out
+       * — the wrapper sends one notification per recipient in a single
+       * Manager-API call).
+       * @nullable
+       */
+    logins?: number[] | null;
+    /**
+       * Notification text. Single-line; the MT4 mobile client displays it
+       * as the push body. Controller enforces a length cap to keep the
+       * payload tractable on the unmanaged side.
+       * @nullable
+       */
+    message?: string | null;
+}

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

@@ -0,0 +1,24 @@
+/**
+ * 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 an online user session entry. Curated subset of the
+ * wrapper's OnlineRecord — exposes the login id and group name, which is
+ * what callers actually need to know who is connected. IP, Counter and
+ * internal Reserved fields are intentionally omitted: IP is potentially
+ * PII and not always meaningful (NAT, proxies), Counter/Reserved are
+ * wrapper bookkeeping.
+ */
+export interface MT4Online {
+    /** Trading account number (login) */
+    login?: number;
+    /**
+       * Group name the account belongs to
+       * @nullable
+       */
+    group?: string | null;
+}

package/dist/generated/model/mT4OnlineListApiResponse.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 { MT4Online } from './mT4Online';
+/**
+ * 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 MT4OnlineListApiResponse {
+    /** @nullable */
+    data?: MT4Online[] | 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/mT4Performance.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 a single MT4 server performance snapshot — one row in the
+ * time-series that `PerformanceRequest` returns. Mirrors the wrapper's
+ * `PerformanceInfo` struct: a periodic resource sample (server-defined
+ * cadence, typically every 5 minutes) covering CPU, memory, network, socket
+ * count, and connected-user count at CPlugin.SaaSWebApps.WebAPI.DTOs.MT4.v2.MT4Performance.Ctm. Used for capacity
+ * planning, dashboards, and incident timelines. The wrapper's private
+ * underscore-prefixed unix-time field is masked by CPlugin.SaaSWebApps.WebAPI.DTOs.MT4.v2.MT4Performance.Ctm.
+ */
+export interface MT4Performance {
+    /** Snapshot timestamp (wrapper internal: __time32_t) */
+    ctm?: string;
+    /** Connected-users count at the snapshot */
+    users?: number;
+    /** CPU load, percent (0..100) */
+    cpu?: number;
+    /** Free memory at the snapshot, in kilobytes */
+    freeMem?: number;
+    /** Network throughput at the snapshot, in kilobytes per second */
+    network?: number;
+    /** Open-sockets count at the snapshot */
+    sockets?: number;
+}

package/dist/generated/model/mT4PerformanceListApiResponse.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 { MT4Performance } from './mT4Performance';
+/**
+ * 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 MT4PerformanceListApiResponse {
+    /** @nullable */
+    data?: MT4Performance[] | 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/mT4Plugin.d.ts

@@ -0,0 +1,36 @@
+/**
+ * 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 MT4 plugin metadata (sidecar-only). Mirrors wrapper's
+ * `ConPlugin` with its embedded `PluginInfo` flattened.
+ */
+export interface MT4Plugin {
+    /**
+       * Plugin DLL filename (max 256 chars on the wrapper side)
+       * @nullable
+       */
+    file?: string | null;
+    /**
+       * Plugin display name (from `PluginInfo.Name`)
+       * @nullable
+       */
+    name?: string | null;
+    /** Plugin version (from `PluginInfo.Version`) */
+    version?: number;
+    /**
+       * Plugin copyright string
+       * @nullable
+       */
+    copyright?: string | null;
+    /** Enabled flag (raw int — 0 = disabled, non-zero = enabled) */
+    enabled?: number;
+    /** Configurable flag (plugin exposes editable parameters) */
+    configurable?: number;
+    /** Manager-terminal-accessible flag */
+    managerAccess?: number;
+}

package/dist/generated/model/mT4PluginConfig.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 a single plugin parameter pair (sidecar-only).
+ * Mirrors wrapper's `PluginCfg`.
+ */
+export interface MT4PluginConfig {
+    /**
+       * Parameter name
+       * @nullable
+       */
+    name?: string | null;
+    /**
+       * Parameter value (free-form string)
+       * @nullable
+       */
+    value?: string | null;
+}

package/dist/generated/model/mT4PluginListApiResponse.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 { MT4Plugin } from './mT4Plugin';
+/**
+ * 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 MT4PluginListApiResponse {
+    /** @nullable */
+    data?: MT4Plugin[] | 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/mT4PluginParam.d.ts

@@ -0,0 +1,22 @@
+/**
+ * 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 { MT4Plugin } from './mT4Plugin';
+import type { MT4PluginConfig } from './mT4PluginConfig';
+/**
+ * v2 DTO for an MT4 plugin together with its parameter set (sidecar-only).
+ * Mirrors wrapper's `ConPluginParam`.
+ */
+export interface MT4PluginParam {
+    /** Plugin metadata */
+    plugin?: MT4Plugin | null;
+    /**
+       * Plugin parameter array (name/value pairs)
+       * @nullable
+       */
+    params?: MT4PluginConfig[] | null;
+}

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

@@ -0,0 +1,35 @@
+/**
+ * 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 { MT4PluginParam } from './mT4PluginParam';
+/**
+ * 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 MT4PluginParamApiResponse {
+    /**
+       * v2 DTO for an MT4 plugin together with its parameter set (sidecar-only).
+       * Mirrors wrapper's `ConPluginParam`.
+       */
+    data?: MT4PluginParam | 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/mT4PluginParamListApiResponse.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 { MT4PluginParam } from './mT4PluginParam';
+/**
+ * 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 MT4PluginParamListApiResponse {
+    /** @nullable */
+    data?: MT4PluginParam[] | 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/mT4ServerLog.d.ts

@@ -0,0 +1,45 @@
+/**
+ * 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 MT4 server journal entry. Returned by `JournalRequest`
+ * when querying server-side logs for a date window. Same field set as the
+ * wrapper's `ServerLog` — the wrapper struct is already minimal, no
+ * secrets to drop. `Code` serialises as a string via
+ * CPlugin.SaaSWebApps.WebAPI.Code.Json.V2JsonContext's `UseStringEnumConverter`.
+ */
+export interface MT4ServerLog {
+    /**
+       * Log level / message category (Ok / Trade / Login / Warn / Err / Att).
+       * <br>
+       * Exposed as a plain string instead of an enum because STJ source-gen's
+       * global `UseStringEnumConverter` doesn't consistently apply to
+       * leaf-enum fields reachable only via nested generics
+       * (`List<MT4ServerLog>.Code`). Property-level
+       * `[JsonConverter(typeof(JsonStringEnumConverter<T>))]` also
+       * failed for the same reason — the source generator does not bind the
+       * attribute at the leaf. Mapping at the mapper level (enum.ToString())
+       * is the most reliable path that survives the source generator.
+       * @nullable
+       */
+    code?: string | null;
+    /**
+       * Server-side timestamp as the wrapper formats it (string, not DateTime — preserved verbatim)
+       * @nullable
+       */
+    time?: string | null;
+    /**
+       * Client IP recorded for the event (empty for server-internal events)
+       * @nullable
+       */
+    ip?: string | null;
+    /**
+       * Free-text log message
+       * @nullable
+       */
+    message?: string | null;
+}

package/dist/generated/model/mT4ServerLogListApiResponse.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 { MT4ServerLog } from './mT4ServerLog';
+/**
+ * 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 MT4ServerLogListApiResponse {
+    /** @nullable */
+    data?: MT4ServerLog[] | 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;
+}