@mywebapi.com/sdk 0.1.0

package/dist/generated/model/mT4CommonApiResponse.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
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+import type { MT4Common } from './mT4Common';
+/**
+ * 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 MT4CommonApiResponse {
+    /**
+       * v2 DTO for MT4 server-wide common settings. Curated subset of the
+       * wrapper's ConCommon struct — exposes fields useful to clients while
+       * shielding the v2 contract from MetaQuotes schema drift.
+       */
+    data?: MT4Common | 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/mT4CommonUpdate.d.ts

@@ -0,0 +1,49 @@
+/**
+ * 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 Type 1 mutator DTO for MT4 server-wide common settings. Curated
+ * subset of the wrapper's `ConCommon` struct — exposes the fields
+ * most likely to need adjustment from a SaaS surface while leaving
+ * runtime counters, derived state, and the wrapper's internal arrays
+ * to the secret-preservation overlay on the controller side.
+ */
+export interface MT4CommonUpdate {
+    /**
+       * Trade server display name.
+       * @nullable
+       */
+    name?: string | null;
+    /**
+       * Broker / company display name.
+       * @nullable
+       */
+    owner?: string | null;
+    /** Server time zone offset from UTC, in hours. */
+    timeZone?: number;
+    /** DST correction setting (server-specific integer). */
+    daylightCorrection?: number;
+    /** Real time-zone (no DST) offset from UTC, in hours. */
+    timeZoneReal?: number;
+    /**
+       * NTP server hostname for clock sync.
+       * @nullable
+       */
+    timeSync?: string | null;
+    /** Minimum acceptable client build number. */
+    minClient?: number;
+    /** Minimum acceptable Manager API build number. */
+    minApi?: number;
+    /** How long (days) to keep mailbox messages. */
+    keepEmails?: number;
+    /** How long (days) to keep tick history. */
+    keepTicks?: number;
+    /** Anti-flood threshold (requests per second). */
+    antiFlood?: number;
+    /** Flood-control behaviour mode. */
+    floodControl?: number;
+}

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

@@ -0,0 +1,51 @@
+/**
+ * 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 mirroring the wrapper's `DailyReport`: one end-of-day
+ * balance/equity/PnL snapshot for a single account. Used by the broker
+ * daily-report family (per-login query, bulk pull, incremental sync).
+ * Internal underscore-prefixed unix-time field, the `Next` pointer
+ * chain, and the 3-int `Reserved` padding are intentionally excluded.
+ * Note: `Ctm` is reported by the MT4 server in its local time zone,
+ * not UTC — clients should treat it as "broker day boundary" and convert
+ * as appropriate.
+ */
+export interface MT4DailyReport {
+    /** Account login the report belongs to */
+    login?: number;
+    /** Day boundary timestamp (wrapper internal: __time32_t, server-local time) */
+    ctm?: string;
+    /**
+       * Trading group the account was in on that day
+       * @nullable
+       */
+    group?: string | null;
+    /**
+       * Free-form bank/payment identifier recorded with the day's deposits
+       * @nullable
+       */
+    bank?: string | null;
+    /** Balance at the start of the reporting day */
+    balancePrev?: number;
+    /** Balance at the end of the reporting day */
+    balance?: number;
+    /** Net deposits credited within the day (positive = inflow) */
+    deposit?: number;
+    /** Credit balance at end-of-day */
+    credit?: number;
+    /** Closed-position profit/loss realised within the day */
+    profitClosed?: number;
+    /** Floating (open-position) profit/loss at end-of-day */
+    profit?: number;
+    /** Equity at end-of-day (Balance + Credit + Profit) */
+    equity?: number;
+    /** Used margin at end-of-day */
+    margin?: number;
+    /** Free margin at end-of-day (Equity - Margin) */
+    marginFree?: number;
+}

package/dist/generated/model/mT4DailyReportListApiResponse.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 { MT4DailyReport } from './mT4DailyReport';
+/**
+ * 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 MT4DailyReportListApiResponse {
+    /** @nullable */
+    data?: MT4DailyReport[] | 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/mT4DataServer.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
+ */
+/**
+ * v2 DTO for a single MT4 access-server (DataServer) configuration entry.
+ * Curated subset of the wrapper's ConDataServer — drops the internal
+ * Reserved1/Reserved2 padding and the Next pointer chain. Loading and
+ * IpInternal are widened from uint to long for JSON-safe numeric
+ * serialization.
+ */
+export interface MT4DataServer {
+    /**
+       * Server address as "host:port" or "host"
+       * @nullable
+       */
+    server?: string | null;
+    /** Server IP (raw wrapper int — sign-preserved; high-bit IPs may serialize as negative) */
+    ip?: number;
+    /**
+       * Free-form server description
+       * @nullable
+       */
+    description?: string | null;
+    /** Whether the server can act as a proxy (0/1; raw wrapper int preserved) */
+    isProxy?: number;
+    /** Connection priority: 0-7 base, 255 = idle */
+    priority?: number;
+    /** Reported server load (UINT_MAX = no information reported) */
+    loading?: number;
+    /** Internal IP address (widened uint → long) */
+    ipInternal?: number;
+    /** Failover-witness flag (0 / 1) */
+    isWitness?: number;
+}

package/dist/generated/model/mT4DataServerApiResponse.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 { MT4DataServer } from './mT4DataServer';
+/**
+ * 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 MT4DataServerApiResponse {
+    /**
+       * v2 DTO for a single MT4 access-server (DataServer) configuration entry.
+       * Curated subset of the wrapper's ConDataServer — drops the internal
+       * Reserved1/Reserved2 padding and the Next pointer chain. Loading and
+       * IpInternal are widened from uint to long for JSON-safe numeric
+       * serialization.
+       */
+    data?: MT4DataServer | 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/mT4DataServerListApiResponse.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 { MT4DataServer } from './mT4DataServer';
+/**
+ * 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 MT4DataServerListApiResponse {
+    /** @nullable */
+    data?: MT4DataServer[] | 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/mT4ExternalCommandBinaryRequest.d.ts

@@ -0,0 +1,20 @@
+/**
+ * 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 binary `ExternalCommand` roundtrips (sidecar-only).
+ * The MT4 server's plugin API has no enforced wire-format — clients
+ * agree with their plugin on the binary layout and pass arbitrary
+ * bytes through this endpoint.
+ */
+export interface MT4ExternalCommandBinaryRequest {
+    /**
+       * Binary payload to send to the plugin (base64-encoded)
+       * @nullable
+       */
+    data?: string | null;
+}

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

@@ -0,0 +1,17 @@
+/**
+ * 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 the response of `ExternalCommandBinary` (sidecar-only).
+ */
+export interface MT4ExternalCommandBinaryResponse {
+    /**
+       * Binary payload received from the first plugin that returned RET_OK (base64-encoded)
+       * @nullable
+       */
+    data?: string | null;
+}

package/dist/generated/model/mT4ExternalCommandBinaryResponseApiResponse.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 { MT4ExternalCommandBinaryResponse } from './mT4ExternalCommandBinaryResponse';
+/**
+ * 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 MT4ExternalCommandBinaryResponseApiResponse {
+    /** v2 DTO for the response of `ExternalCommandBinary` (sidecar-only). */
+    data?: MT4ExternalCommandBinaryResponse | 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/mT4Feeder.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 { DataFeedMode } from './dataFeedMode';
+/**
+ * v2 DTO for a single MT4 quote/news feeder configuration. Curated
+ * subset of the wrapper's ConFeeder — drops the wrapper's Unused
+ * reserved blob AND the `Password` field (datafeed credentials).
+ */
+export interface MT4Feeder {
+    /**
+       * Feeder name (used as cursor key — assumed unique)
+       * @nullable
+       */
+    name?: string | null;
+    /**
+       * Datafeed loader filename (DLL or script path)
+       * @nullable
+       */
+    file?: string | null;
+    /**
+       * Upstream feeder server address
+       * @nullable
+       */
+    server?: string | null;
+    /**
+       * Datafeed login (upstream credential identifier)
+       * @nullable
+       */
+    login?: string | null;
+    /**
+       * Keywords for news filtering
+       * @nullable
+       */
+    keywords?: string | null;
+    /** Enable flag (0 = disabled, 1 = enabled — raw wrapper int) */
+    enable?: number;
+    /** Feed mode (quotes / news / both — wrapper enum) */
+    dataFeedMode?: DataFeedMode;
+    /** Maximum freeze time in seconds before considered stalled (default ~120) */
+    timeout?: number;
+    /** Reconnect delay before "sleep" attempts threshold (default ~5s) */
+    timeoutReconnect?: number;
+    /** Reconnect delay after "sleep" attempts threshold (default ~60s) */
+    timeoutSleep?: number;
+    /** Reconnect count before switching to sleep timeout */
+    attempsSleep?: number;
+    /** News language id */
+    newsLangId?: number;
+}

package/dist/generated/model/mT4FeederApiResponse.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
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+import type { MT4Feeder } from './mT4Feeder';
+/**
+ * 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 MT4FeederApiResponse {
+    /**
+       * v2 DTO for a single MT4 quote/news feeder configuration. Curated
+       * subset of the wrapper's ConFeeder — drops the wrapper's Unused
+       * reserved blob AND the `Password` field (datafeed credentials).
+       */
+    data?: MT4Feeder | 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/mT4FeederListApiResponse.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 { MT4Feeder } from './mT4Feeder';
+/**
+ * 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 MT4FeederListApiResponse {
+    /** @nullable */
+    data?: MT4Feeder[] | 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/mT4GatewayAccount.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 { EnGatewayAccountFlags } from './enGatewayAccountFlags';
+/**
+ * v2 DTO for a single MT4 STP gateway-account configuration entry.
+ * Curated subset of the wrapper's ConGatewayAccount — drops the
+ * 23-int Reserved block AND the `Password` field (STP MT4
+ * credential to the external server). NotifyLogins is preserved
+ * as int[8] because the wrapper exposes a fixed-size 8-slot array.
+ */
+export interface MT4GatewayAccount {
+    /** Whether the gateway-account entry is active */
+    enable?: boolean;
+    /**
+       * Public name of the gateway account
+       * @nullable
+       */
+    name?: string | null;
+    /** Internal id (stable identifier) */
+    id?: number;
+    /** Gateway type (obsolete in modern MT4 builds — preserved for API completeness) */
+    type?: number;
+    /** STP MT4 login (account number on the external server) */
+    login?: number;
+    /**
+       * External MT4 server address (host:port string)
+       * @nullable
+       */
+    address?: string | null;
+    /**
+       * Logins of broker managers receiving internal-email gateway notifications (fixed-size 8 slots)
+       * @nullable
+       */
+    notifyLogins?: number[] | null;
+    /** Gateway-account flag bitmap (wrapper enum, serialized as string) */
+    flags?: EnGatewayAccountFlags;
+}

package/dist/generated/model/mT4GatewayAccountApiResponse.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 { MT4GatewayAccount } from './mT4GatewayAccount';
+/**
+ * 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 MT4GatewayAccountApiResponse {
+    /**
+       * v2 DTO for a single MT4 STP gateway-account configuration entry.
+       * Curated subset of the wrapper's ConGatewayAccount — drops the
+       * 23-int Reserved block AND the `Password` field (STP MT4
+       * credential to the external server). NotifyLogins is preserved
+       * as int[8] because the wrapper exposes a fixed-size 8-slot array.
+       */
+    data?: MT4GatewayAccount | 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/mT4GatewayAccountListApiResponse.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 { MT4GatewayAccount } from './mT4GatewayAccount';
+/**
+ * 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 MT4GatewayAccountListApiResponse {
+    /** @nullable */
+    data?: MT4GatewayAccount[] | 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/mT4GatewayMarkup.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
+ */
+/**
+ * v2 DTO for a single MT4 gateway markup rule. Curated subset of the
+ * wrapper's ConGatewayMarkup — drops the 16-int Reserved padding.
+ * Source describes the external symbol (or a wildcard/group mask)
+ * being mapped onto Symbol on this server, with per-side spread
+ * adjustments BidMarkup and AskMarkup expressed in pips.
+ */
+export interface MT4GatewayMarkup {
+    /** Whether the markup rule is active */
+    enable?: boolean;
+    /**
+       * External symbol name, mask, or symbol-group identifier
+       * @nullable
+       */
+    source?: string | null;
+    /**
+       * Local symbol name this markup applies to
+       * @nullable
+       */
+    symbol?: string | null;
+    /**
+       * Gateway-account name (obsolete in modern MT4 builds — preserved for API completeness)
+       * @nullable
+       */
+    accountName?: string | null;
+    /** Gateway-account internal id (obsolete — see AccountName note) */
+    accountId?: number;
+    /** Bid-side markup in pips (added to the external bid quote) */
+    bidMarkup?: number;
+    /** Ask-side markup in pips (added to the external ask quote) */
+    askMarkup?: number;
+}