@mywebapi.com/sdk 0.1.0

package/dist/generated/model/int32ApiResponse.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
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+/**
+ * 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 Int32ApiResponse {
+    data?: number;
+    /**
+       * 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/int32MT4DailyReportListDictionaryApiResponse.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 { Int32MT4DailyReportListDictionaryApiResponseData } from './int32MT4DailyReportListDictionaryApiResponseData';
+/**
+ * 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 Int32MT4DailyReportListDictionaryApiResponse {
+    /** @nullable */
+    data?: Int32MT4DailyReportListDictionaryApiResponseData;
+    /**
+       * 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/int32MT4DailyReportListDictionaryApiResponseData.d.ts

@@ -0,0 +1,14 @@
+/**
+ * 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 { MT4DailyReport } from './mT4DailyReport';
+/**
+ * @nullable
+ */
+export type Int32MT4DailyReportListDictionaryApiResponseData = {
+    [key: string]: MT4DailyReport[] | null;
+} | null;

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

@@ -0,0 +1,13 @@
+/**
+ * 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 { JsonNodeOptions } from './jsonNodeOptions';
+export interface JsonNode {
+    readonly options?: JsonNodeOptions | null;
+    readonly parent?: JsonNode | null;
+    readonly root?: JsonNode | null;
+}

package/dist/generated/model/jsonNodeApiResponse.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
+ */
+import type { ApiError } from './apiError';
+import type { ApiMeta } from './apiMeta';
+import type { JsonNode } from './jsonNode';
+/**
+ * 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 JsonNodeApiResponse {
+    data?: JsonNode | 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/jsonNodeOptions.d.ts

@@ -0,0 +1,10 @@
+/**
+ * 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
+ */
+export interface JsonNodeOptions {
+    propertyNameCaseInsensitive?: boolean;
+}

package/dist/generated/model/mT4Access.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 firewall (access) rule. Curated subset of
+ * the wrapper's ConAccess struct — drops the 17-int Reserved padding.
+ * IpFrom/IpTo are widened from uint to long so the JSON-serialized
+ * numeric value fits inside JS Number safely (no precision loss).
+ */
+export interface MT4Access {
+    /**
+       * Firewall rule action — raw MT4 value preserved (FW_BLOCK / FW_PERMIT
+       * per the wrapper's enum encoding; surfaced as int because the wrapper
+       * itself surfaces it as int).
+       */
+    action?: number;
+    /** IP range start (uint widened to long for JSON safety) */
+    ipFrom?: number;
+    /** IP range end (uint widened to long for JSON safety) */
+    ipTo?: number;
+    /**
+       * Free-form comment for the rule
+       * @nullable
+       */
+    comment?: string | null;
+}

package/dist/generated/model/mT4AccessApiResponse.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 { MT4Access } from './mT4Access';
+/**
+ * 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 MT4AccessApiResponse {
+    /**
+       * v2 DTO for a single MT4 firewall (access) rule. Curated subset of
+       * the wrapper's ConAccess struct — drops the 17-int Reserved padding.
+       * IpFrom/IpTo are widened from uint to long so the JSON-serialized
+       * numeric value fits inside JS Number safely (no precision loss).
+       */
+    data?: MT4Access | 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/mT4AccessListApiResponse.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 { MT4Access } from './mT4Access';
+/**
+ * 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 MT4AccessListApiResponse {
+    /** @nullable */
+    data?: MT4Access[] | 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/mT4Backup.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 { ArcBackupExecutionPeriod } from './arcBackupExecutionPeriod';
+import type { ArcBackupStorePeriod } from './arcBackupStorePeriod';
+import type { BackupExecutionPeriod } from './backupExecutionPeriod';
+import type { BackupStorePeriod } from './backupStorePeriod';
+import type { ExportExecutionPeriod } from './exportExecutionPeriod';
+import type { ServerRole } from './serverRole';
+import type { WatchdogFailoverMode } from './watchdogFailoverMode';
+import type { WatchdogState } from './watchdogState';
+/**
+ * v2 DTO for the MT4 server's backup configuration (wrapper's ConBackup).
+ * Curated subset — drops the WatchPassword field (slave-server credential)
+ * for security. All other wrapper public fields are preserved, enums are
+ * surfaced as enum types (V2JsonContext serializes them as strings via
+ * UseStringEnumConverter=true).
+ */
+export interface MT4Backup {
+    /**
+       * Filesystem path where full backups are written
+       * @nullable
+       */
+    fullBackupPath?: string | null;
+    /** Full backup schedule period (1h / 4h / 1d) */
+    fullBackupPeriod?: BackupExecutionPeriod;
+    /** How long full backups are retained (1m / 3m / 6m / 1y) */
+    fullBackupStore?: BackupStorePeriod;
+    /** Full backup time-shift in minutes */
+    fullBackupShift?: number;
+    /** Last full backup completion timestamp (UTC) */
+    fullBackupLastTime?: string;
+    /**
+       * Path to external processing directory
+       * @nullable
+       */
+    externalPath?: string | null;
+    /** Archive backup schedule period (5m / 15m / 30m / 1h) */
+    archivePeriod?: ArcBackupExecutionPeriod;
+    /** How long archive backups are retained (1w / 2w / 1m / 3m / 6m) */
+    archiveStore?: ArcBackupStorePeriod;
+    /** Archive backup time-shift in minutes */
+    archiveShift?: number;
+    /** Last archive backup completion timestamp (UTC) */
+    archiveLastTime?: string;
+    /**
+       * Comma-separated list of exported securities
+       * @nullable
+       */
+    exportSecurities?: string | null;
+    /**
+       * Path to export script
+       * @nullable
+       */
+    exportPath?: string | null;
+    /** Export schedule period (1m / 5m / 15m / 30m / 1h) */
+    exportPeriod?: ExportExecutionPeriod;
+    /** Last export completion timestamp (UTC) */
+    exportLastTime?: string;
+    /** Server role in HA pair (stand-alone / master / slave) */
+    watchRole?: ServerRole;
+    /**
+       * Opposite server's IP:port string (not secret)
+       * @nullable
+       */
+    watchOpposite?: string | null;
+    /** Watchdog IP (32-bit, raw wrapper representation) */
+    watchIp?: number;
+    /** Watchdog state */
+    watchState?: WatchdogState;
+    /** Watchdog failover mode */
+    watchFailover?: WatchdogFailoverMode;
+    /** Watchdog response timeout, seconds */
+    watchTimeout?: number;
+    /** Watchdog login */
+    watchLogin?: number;
+    /** Watchdog last-seen timestamp (raw int — wrapper does not auto-convert) */
+    watchTimestamp?: number;
+}

package/dist/generated/model/mT4BackupApiResponse.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 { MT4Backup } from './mT4Backup';
+/**
+ * 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 MT4BackupApiResponse {
+    /**
+       * v2 DTO for the MT4 server's backup configuration (wrapper's ConBackup).
+       * Curated subset — drops the WatchPassword field (slave-server credential)
+       * for security. All other wrapper public fields are preserved, enums are
+       * surfaced as enum types (V2JsonContext serializes them as strings via
+       * UseStringEnumConverter=true).
+       */
+    data?: MT4Backup | 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/mT4BackupInfo.d.ts

@@ -0,0 +1,27 @@
+/**
+ * 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 backup file descriptor. Curated subset of
+ * the wrapper's `BackupInfo` — drops the 6-int reserved blob and
+ * keeps only the three consumer-facing fields.
+ */
+export interface MT4BackupInfo {
+    /**
+       * Backup file name (basename, server-relative)
+       * @nullable
+       */
+    file?: string | null;
+    /**
+       * File size in bytes. Source field is a 32-bit signed int —
+       * widened to `long` here to give the client JSON-safe
+       * numeric range without re-shaping after a future wrapper fix.
+       */
+    size?: number;
+    /** File modification time (UTC, from MetaQuotes `__time32_t`) */
+    time?: string;
+}

package/dist/generated/model/mT4BackupInfoListApiResponse.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 { MT4BackupInfo } from './mT4BackupInfo';
+/**
+ * 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 MT4BackupInfoListApiResponse {
+    /** @nullable */
+    data?: MT4BackupInfo[] | 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/mT4BalanceDiff.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 returned by `AdmBalanceCheck`. Reports the difference between
+ * the account's recorded balance and what the MT4 server recomputes from
+ * closed orders + balance operations. `Diff = 0` means the integrity
+ * check passed; non-zero means the recorded balance has drifted and would
+ * be set to `recorded + Diff` if `AdmBalanceFix` ran.
+ */
+export interface MT4BalanceDiff {
+    /** Account login */
+    login?: number;
+    /** Difference (signed). Zero means balance integrity check passed. */
+    diff?: number;
+}

package/dist/generated/model/mT4BalanceDiffApiResponse.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 { MT4BalanceDiff } from './mT4BalanceDiff';
+/**
+ * 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 MT4BalanceDiffApiResponse {
+    /**
+       * v2 DTO returned by `AdmBalanceCheck`. Reports the difference between
+       * the account's recorded balance and what the MT4 server recomputes from
+       * closed orders + balance operations. `Diff = 0` means the integrity
+       * check passed; non-zero means the recorded balance has drifted and would
+       * be set to `recorded + Diff` if `AdmBalanceFix` ran.
+       */
+    data?: MT4BalanceDiff | 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/mT4BalanceDiffListApiResponse.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 { MT4BalanceDiff } from './mT4BalanceDiff';
+/**
+ * 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 MT4BalanceDiffListApiResponse {
+    /** @nullable */
+    data?: MT4BalanceDiff[] | 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/mT4ChartBar.d.ts

@@ -0,0 +1,27 @@
+/**
+ * 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 OHLC chart bar. Curated from the wrapper's `RateInfoEx`;
+ * drops the internal `SymbolMultiply`/`Digits` scaling helpers
+ * (callers don't need them — the wrapper's `buildRI` already
+ * normalised Open/High/Low/Close from raw int prices into floating point).
+ */
+export interface MT4ChartBar {
+    /** Bar timestamp (UTC, start of the bar's period) */
+    time?: string;
+    /** Open price */
+    open?: number;
+    /** High price during the bar */
+    high?: number;
+    /** Low price during the bar */
+    low?: number;
+    /** Close price */
+    close?: number;
+    /** Trading volume during the bar (lots × 100 in MT4 convention) */
+    volume?: number;
+}

package/dist/generated/model/mT4ChartBarListApiResponse.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 { MT4ChartBar } from './mT4ChartBar';
+/**
+ * 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 MT4ChartBarListApiResponse {
+    /** @nullable */
+    data?: MT4ChartBar[] | 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/mT4ChartWriteRequest.d.ts

@@ -0,0 +1,21 @@
+/**
+ * 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 { MT4ChartBar } from './mT4ChartBar';
+/**
+ * v2 request body for the `ChartAdd` / `ChartUpdate` / `ChartDelete`
+ * trio. Wraps the bars list so the request shape stays extensible — future
+ * metadata (e.g. `SkipIntegrityCheck`) can be added without a breaking
+ * change to clients that only sent `Rates`.
+ */
+export interface MT4ChartWriteRequest {
+    /**
+       * OHLC bars to add / update / delete. Must be non-empty.
+       * @nullable
+       */
+    rates?: MT4ChartBar[] | null;
+}

package/dist/generated/model/mT4Common.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 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.
+ */
+export interface MT4Common {
+    /**
+       * Trade server name
+       * @nullable
+       */
+    name?: string | null;
+    /**
+       * Broker / company display name
+       * @nullable
+       */
+    owner?: string | null;
+    /** Trade server build number */
+    build?: number;
+    /** Trade server version */
+    version?: number;
+    /** Server time zone offset from UTC, in hours (DST-adjusted) */
+    timeZone?: number;
+}