@mywebapi.com/sdk 0.1.0

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

@@ -0,0 +1,65 @@
+/**
+ * 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 trade transaction — input AND output of `TradeTransaction`.
+ * The wrapper's `TradeTransInfo` is in/out: the caller fills the request
+ * fields (operation type, command, symbol, volume, price), submits via POST,
+ * and the server populates the resulting `Order` id (for Open) or
+ * echoes the modified record (for Modify/Close).
+ *
+ * Enum fields (`TradeTransactionType`, `TradeCommand`,
+ * `TradeRequestFlags`) are exposed as plain strings. Clients submit
+ * the enum name (e.g. `"Buy"`, `"OpenPending"`); the response
+ * echoes the names back. This dodges the leaf-enum nested-generic STJ
+ * source-gen quirk documented in feedback-stj-enum-leaf-nested.
+ */
+export interface MT4TradeTransaction {
+    /**
+       * Transaction type: OpenPending, OpenMarket, ModifyPending, ModifyTrade, DeletePending, CloseMarket, BalanceAdd, CreditAdd, etc.
+       * @nullable
+       */
+    tradeTransactionType?: string | null;
+    /**
+       * Trade command: Buy, Sell, BuyLimit, SellLimit, BuyStop, SellStop, Balance, Credit
+       * @nullable
+       */
+    tradeCommand?: string | null;
+    /**
+       * Request flags: None, MarketOpen, Partial, NoExpiration, etc.
+       * @nullable
+       */
+    tradeRequestFlags?: string | null;
+    /** Pending order expiration time. Default value means GTC. */
+    expiration?: string;
+    /** Order ticket. 0 on Open requests; server fills this on success. */
+    order?: number;
+    /** Login (account number). Required for Balance/Credit operations. */
+    orderBy?: number;
+    /**
+       * Symbol (max 12 chars)
+       * @nullable
+       */
+    symbol?: string | null;
+    /** Volume in MT4 internal units. 1 lot = 100, so e.g. 250 = 2.5 lots. */
+    volume?: number;
+    /** Order price */
+    price?: number;
+    /** Stop-loss price (0 = none) */
+    sl?: number;
+    /** Take-profit price (0 = none) */
+    tp?: number;
+    /** Instant-execution price deviation tolerance (points) */
+    ieDeviation?: number;
+    /**
+       * Free-form comment (broker-visible)
+       * @nullable
+       */
+    comment?: string | null;
+    /** CRC for transaction integrity; usually 0 (server fills). */
+    crc?: number;
+}

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

@@ -0,0 +1,44 @@
+/**
+ * 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 { MT4TradeTransaction } from './mT4TradeTransaction';
+/**
+ * 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 MT4TradeTransactionApiResponse {
+    /**
+       * v2 DTO for a trade transaction — input AND output of `TradeTransaction`.
+       * The wrapper's `TradeTransInfo` is in/out: the caller fills the request
+       * fields (operation type, command, symbol, volume, price), submits via POST,
+       * and the server populates the resulting `Order` id (for Open) or
+       * echoes the modified record (for Modify/Close).
+       *
+       * Enum fields (`TradeTransactionType`, `TradeCommand`,
+       * `TradeRequestFlags`) are exposed as plain strings. Clients submit
+       * the enum name (e.g. `"Buy"`, `"OpenPending"`); the response
+       * echoes the names back. This dodges the leaf-enum nested-generic STJ
+       * source-gen quirk documented in feedback-stj-enum-leaf-nested.
+       */
+    data?: MT4TradeTransaction | 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/mT4TradeUpdate.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
+ */
+/**
+ * Type 1 mutator input for the admin direct-edit endpoint
+ * `AdmTradeRecordModify`. Only the fields a back-office tool would
+ * legitimately need to adjust are exposed; everything else (order id,
+ * login, symbol, volume, open/close times, gateway internals, conversion
+ * rates, API data blobs) is preserved from the server-side read.
+ *
+ * <br>
+ * For typical stop-loss / take-profit edits prefer
+ * `POST TradeTransaction` with `tradeTransactionType=ModifyTrade`
+ * — that goes through the wrapper's audited path. This endpoint is the
+ * low-level admin override for back-office corrections.
+ */
+export interface MT4TradeUpdate {
+    /** Order ticket to edit (path parameter is the source of truth) */
+    order?: number;
+    /** New stop-loss price (0 = remove SL) */
+    sl?: number;
+    /** New take-profit price (0 = remove TP) */
+    tp?: number;
+    /** Magic number / EA tag */
+    magic?: number;
+    /**
+       * Comment (broker-visible)
+       * @nullable
+       */
+    comment?: string | null;
+    /** Manual commission override */
+    commission?: number;
+    /** Manual agent-commission override */
+    commissionAgent?: number;
+    /** Swap / storage override */
+    storage?: number;
+    /** Profit override (back-office correction only) */
+    profit?: number;
+    /** Taxes override */
+    taxes?: number;
+}

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

@@ -0,0 +1,141 @@
+/**
+ * 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 trading account. Curated subset of the wrapper's
+ * `UserRecord` — exposes identity, contact, financial and flag fields
+ * that callers actually need.
+ *
+ * Deliberately omitted from v2 (vs v1's full UserRecord shape):
+ *   * Password / PasswordInvestor / PasswordPhone / OtpSecret / ApiData /
+ *     SecureReserved — credentials and secrets must never cross the v2
+ *     boundary regardless of access level.
+ *   * Unused / Reserved2 / EnableReserved / TimeStamp — wrapper bookkeeping
+ *     with no caller-visible semantics.
+ *
+ * Account flags are exposed as a single CPlugin.SaaSWebApps.WebAPI.DTOs.MT4.v2.MT4User.EnableFlags bitfield
+ * (the wrapper's native representation). Bit semantics are documented under
+ * that property — splitting it into separate booleans would hide the fact
+ * that MetaQuotes occasionally reuses bit positions across builds.
+ */
+export interface MT4User {
+    /** Trading account number (login) */
+    login?: number;
+    /**
+       * Group name the account belongs to
+       * @nullable
+       */
+    group?: string | null;
+    /**
+       * Display name of the account holder
+       * @nullable
+       */
+    name?: string | null;
+    /** UTC timestamp when the account was created */
+    registrationDate?: string;
+    /** UTC timestamp of the last MT4 server interaction */
+    lastDate?: string;
+    /**
+       * External customer identifier (e.g. CRM/KYC link). Wrapper's `Id` field.
+       * @nullable
+       */
+    externalId?: string | null;
+    /**
+       * MT4-internal status string (e.g. live/demo state)
+       * @nullable
+       */
+    status?: string | null;
+    /**
+       * Country (free text per broker's enrolment workflow)
+       * @nullable
+       */
+    country?: string | null;
+    /**
+       * City
+       * @nullable
+       */
+    city?: string | null;
+    /**
+       * State / region
+       * @nullable
+       */
+    state?: string | null;
+    /**
+       * Postal / ZIP code
+       * @nullable
+       */
+    zipCode?: string | null;
+    /**
+       * Street address
+       * @nullable
+       */
+    address?: string | null;
+    /**
+       * Lead source / referral channel tag
+       * @nullable
+       */
+    leadSource?: string | null;
+    /**
+       * Contact phone
+       * @nullable
+       */
+    phone?: string | null;
+    /**
+       * Contact email
+       * @nullable
+       */
+    email?: string | null;
+    /**
+       * Free-form back-office comment
+       * @nullable
+       */
+    comment?: string | null;
+    /** Account leverage (e.g. 100 means 1:100) */
+    leverage?: number;
+    /** IB / agent account number that referred this client */
+    agentAccount?: number;
+    /** Last connection IP as raw int (use platform helpers to format) */
+    lastIP?: number;
+    /** Current balance */
+    balance?: number;
+    /** Credit on the account */
+    credit?: number;
+    /** Balance at the start of the previous calendar month */
+    prevMonthBalance?: number;
+    /** Balance at the previous reporting close */
+    prevBalance?: number;
+    /** Equity at the start of the previous calendar month */
+    prevMonthEquity?: number;
+    /** Equity at the previous reporting close */
+    prevEquity?: number;
+    /** Interest rate (broker-defined, often used for swaps) */
+    interestRate?: number;
+    /** Tax rate applied to the account */
+    taxes?: number;
+    /**
+       * Account flag bitfield (wrapper's `EnableFlags`). Documented bits:
+       *   * 0x01 = account enabled (login allowed)
+       *   * 0x02 = client may change password
+       *   * 0x04 = account is read-only (no trading)
+       *   * 0x08 = OTP enrolment required at login
+       * Bit positions reflect MT4 build 1455. Verify against the current MT4
+       * Manager docs if pinning behaviour to a specific bit.
+       */
+    enableFlags?: number;
+    /** 0 = no reports, non-zero = nightly email reports enabled */
+    sendReports?: number;
+    /**
+       * MetaQuotes ID for mobile push notifications (0 if not linked).
+       * Typed as `long` in v2 even though current builds store it in
+       * 32 bits — the wrapper exposes a wider underlying type and a checked
+       * narrowing cast would crash for accounts whose mqid sits above
+       * Int32.MaxValue. Future-proofs the contract against MQ widening.
+       */
+    mqid?: number;
+    /** UI tint color in terminal client lists */
+    userColor?: number;
+}

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

@@ -0,0 +1,48 @@
+/**
+ * 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 { MT4User } from './mT4User';
+/**
+ * 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 MT4UserApiResponse {
+    /**
+       * v2 DTO describing a trading account. Curated subset of the wrapper's
+       * `UserRecord` — exposes identity, contact, financial and flag fields
+       * that callers actually need.
+       *
+       * Deliberately omitted from v2 (vs v1's full UserRecord shape):
+       *   * Password / PasswordInvestor / PasswordPhone / OtpSecret / ApiData /
+       *     SecureReserved — credentials and secrets must never cross the v2
+       *     boundary regardless of access level.
+       *   * Unused / Reserved2 / EnableReserved / TimeStamp — wrapper bookkeeping
+       *     with no caller-visible semantics.
+       *
+       * Account flags are exposed as a single CPlugin.SaaSWebApps.WebAPI.DTOs.MT4.v2.MT4User.EnableFlags bitfield
+       * (the wrapper's native representation). Bit semantics are documented under
+       * that property — splitting it into separate booleans would hide the fact
+       * that MetaQuotes occasionally reuses bit positions across builds.
+       */
+    data?: MT4User | 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/mT4UserCreate.d.ts

@@ -0,0 +1,63 @@
+/**
+ * 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
+ */
+/**
+ * Type 1 mutator input — full create shape for `UserRecordNew`.
+ * Same writable fields as CPlugin.SaaSWebApps.WebAPI.DTOs.MT4.v2.MT4UserUpdate minus the explicit
+ * `Balance`/`Credit` (those should come through dedicated balance
+ * operations after the account exists). The wrapper allocates the next free
+ * login id when `Login = 0`; clients may also request a specific id by
+ * setting `Login > 0` (the server rejects collisions).
+ *
+ * Password / OTP / API-data fields are NOT on this DTO. After successful
+ * creation, set the initial password via a separate
+ * `POST UserPasswordSet/{login}` call. The wrapper accepts the new
+ * account with empty password bytes; the password endpoint lifts it to
+ * usable credentials.
+ */
+export interface MT4UserCreate {
+    /**
+       * Optional preferred login. `0` = let server assign the next free
+       * id. `> 0` = request this exact id (server rejects collisions
+       * via wrapper error code).
+       */
+    login?: number;
+    /** @nullable */
+    group?: string | null;
+    /** @nullable */
+    name?: string | null;
+    /** @nullable */
+    externalId?: string | null;
+    /** @nullable */
+    status?: string | null;
+    /** @nullable */
+    country?: string | null;
+    /** @nullable */
+    city?: string | null;
+    /** @nullable */
+    state?: string | null;
+    /** @nullable */
+    zipCode?: string | null;
+    /** @nullable */
+    address?: string | null;
+    /** @nullable */
+    leadSource?: string | null;
+    /** @nullable */
+    phone?: string | null;
+    /** @nullable */
+    email?: string | null;
+    /** @nullable */
+    comment?: string | null;
+    leverage?: number;
+    agentAccount?: number;
+    interestRate?: number;
+    taxes?: number;
+    enableFlags?: number;
+    sendReports?: number;
+    mqid?: number;
+    userColor?: number;
+}

package/dist/generated/model/mT4UserListApiResponse.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 { MT4User } from './mT4User';
+/**
+ * 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 MT4UserListApiResponse {
+    /** @nullable */
+    data?: MT4User[] | 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/mT4UserRestoreInput.d.ts

@@ -0,0 +1,46 @@
+/**
+ * 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 narrow input DTO for `BackupRestoreUsers`. Carries the
+ * account identity + persistent metadata + money/leverage state that a
+ * disaster-recovery flow needs to recreate.
+ */
+export interface MT4UserRestoreInput {
+    /** Account login (record key) */
+    login?: number;
+    /**
+       * Group name
+       * @nullable
+       */
+    group?: string | null;
+    /**
+       * Account holder display name
+       * @nullable
+       */
+    name?: string | null;
+    /**
+       * Email address
+       * @nullable
+       */
+    email?: string | null;
+    /**
+       * Country
+       * @nullable
+       */
+    country?: string | null;
+    /** Trading leverage (e.g. 100 for 1:100) */
+    leverage?: number;
+    /** Account balance (broker base currency) */
+    balance?: number;
+    /** Account credit (e.g. promotional bonus) */
+    credit?: number;
+    /** Account enabled flag (0 = disabled, 1 = enabled — raw wrapper int) */
+    enable?: number;
+    /** Read-only flag (1 = cannot open positions) */
+    enableReadOnly?: number;
+}

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

@@ -0,0 +1,122 @@
+/**
+ * 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
+ */
+/**
+ * Type 1 mutator input — full-replace shape for `UserRecordUpdate`.
+ * Client submits every non-secret, non-read-only, non-computed field; the
+ * handler reads the current record from MT4 server, copies the secrets and
+ * read-only fields off it, applies this DTO over the rest, and writes the
+ * modified structure back.
+ *
+ * Read-only fields that do NOT appear here (preserved by the server-side
+ * read step):
+ *   * `Login` — passed as a path parameter, immutable identity.
+ *   * `RegistrationDate` — set once on creation, never updated.
+ *   * `LastDate`, `LastIP` — assigned by MT4 server during login.
+ *   * `PrevMonthBalance`, `PrevBalance`, `PrevMonthEquity`,
+ *     `PrevEquity` — derived server-side at reporting close.
+ *
+ * Secret fields that do NOT appear here (preserved by the server-side
+ * read step; use dedicated endpoints to change them):
+ *   * `Password`, `PasswordInvestor`, `PasswordPhone` —
+ *     change via `POST UserPasswordSet`.
+ *   * `OTPSecret` — provisioned via separate admin flow.
+ *   * `APIData` — wrapper-internal blob, never client-controlled.
+ *
+ * <br><b>Note on Balance/Credit:</b> these fields ARE accepted here because the
+ * wrapper `UserRecordUpdate` writes them directly. However, the audit-
+ * trail-preserving way to move money is the dedicated balance operation
+ * endpoints (forthcoming) — submitting Balance via this DTO bypasses the
+ * audit log on MT4 server side.
+ */
+export interface MT4UserUpdate {
+    /**
+       * Group name the account belongs to
+       * @nullable
+       */
+    group?: string | null;
+    /**
+       * Display name of the account holder
+       * @nullable
+       */
+    name?: string | null;
+    /**
+       * External customer identifier (CRM/KYC link)
+       * @nullable
+       */
+    externalId?: string | null;
+    /**
+       * MT4-internal status string
+       * @nullable
+       */
+    status?: string | null;
+    /**
+       * Country
+       * @nullable
+       */
+    country?: string | null;
+    /**
+       * City
+       * @nullable
+       */
+    city?: string | null;
+    /**
+       * State / region
+       * @nullable
+       */
+    state?: string | null;
+    /**
+       * Postal / ZIP code
+       * @nullable
+       */
+    zipCode?: string | null;
+    /**
+       * Street address
+       * @nullable
+       */
+    address?: string | null;
+    /**
+       * Lead source / referral channel tag
+       * @nullable
+       */
+    leadSource?: string | null;
+    /**
+       * Contact phone
+       * @nullable
+       */
+    phone?: string | null;
+    /**
+       * Contact email
+       * @nullable
+       */
+    email?: string | null;
+    /**
+       * Free-form back-office comment
+       * @nullable
+       */
+    comment?: string | null;
+    /** Account leverage (e.g. 100 means 1:100) */
+    leverage?: number;
+    /** IB / agent account number that referred this client */
+    agentAccount?: number;
+    /** Current balance (prefer dedicated balance ops for audit trail) */
+    balance?: number;
+    /** Credit on the account */
+    credit?: number;
+    /** Interest rate */
+    interestRate?: number;
+    /** Tax rate */
+    taxes?: number;
+    /** Account flag bitfield — see MT4User.EnableFlags for bit semantics */
+    enableFlags?: number;
+    /** 0 = no reports, non-zero = nightly email reports enabled */
+    sendReports?: number;
+    /** MetaQuotes ID for mobile push notifications */
+    mqid?: number;
+    /** UI tint color in terminal client lists */
+    userColor?: number;
+}

package/dist/generated/model/mT4UsersGroupOp.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 request body for `UsersGroupOp` — bulk group-membership / leverage /
+ * enable-disable / delete operation across a list of account logins.
+ */
+export interface MT4UsersGroupOp {
+    /**
+       * Bulk operation: `"Delete"`, `"Enable"`, `"Disable"`, `"Leverage"`, or `"SetGroup"`.
+       * @nullable
+       */
+    command?: string | null;
+    /**
+       * Target group name (max 15 chars + NUL). Only used by `SetGroup`.
+       * @nullable
+       */
+    newGroup?: string | null;
+    /** New leverage value (e.g. 100, 200, 500). Only used by `Leverage`. */
+    leverage?: number;
+    /**
+       * List of account logins (account numbers) to apply the operation to. Must be non-empty.
+       * @nullable
+       */
+    logins?: number[] | null;
+}