@mywebapi.com/sdk 0.1.2 → 0.3.0

package/dist/client.d.ts

@@ -4,6 +4,7 @@ import type { RetryPolicy } from './retry';
 import { type EnvironmentSelector } from './environments';
 import { type UnwrapEnvelope } from './mutator';
 import type { PagedResult } from './pagination';
+import { type RequestOptions } from './request-timeout';
 /** A trade platform the authenticated principal can access.
  *
  *  Shape mirrors the server `TradePlatform` entity (serialized camelCase by STJ).
@@ -83,6 +84,21 @@ export interface CPluginWebApiClientOptions {
     fetch?: typeof fetch;
     /** Override individual retry-policy fields. */
     retry?: Partial<RetryPolicy>;
+    /**
+     * Minimum client deadline per request in milliseconds, covering token acquisition,
+     * the request and the response body. Defaults to 30 seconds. For operations with a
+     * server timeout the deadline is extended automatically to that timeout plus 30 s,
+     * so the server's `Timeout` / `OutcomeUnknown` / `Busy` answer is received rather
+     * than cut off by a local abort.
+     */
+    timeoutMs?: number;
+    /**
+     * Client-wide server timeout in seconds (1–300), sent as `X-Request-Timeout` to every
+     * operation that accepts it. A per-call `requestTimeout` overrides it. Omit to use each
+     * operation's server default (trade 5 s, read 10 s, change 15 s, history 30 s,
+     * maintenance 60 s).
+     */
+    requestTimeout?: number;
 }
 /** Combine environment selector with client credentials. */
 export type CPluginWebApiClientInit = EnvironmentSelector & CPluginWebApiClientOptions;
@@ -93,7 +109,11 @@ type CleanNamespace<M, P extends string> = {
 type MT4Namespace = CleanNamespace<BoundModule<typeof mt4Authentication> & BoundModule<typeof mt4BackupDestructive> & BoundModule<typeof mt4Backup> & BoundModule<typeof mt4Common> & BoundModule<typeof mt4Config> & BoundModule<typeof mt4Groups> & BoundModule<typeof mt4History> & BoundModule<typeof mt4Mail> & BoundModule<typeof mt4Margins> & BoundModule<typeof mt4News> & BoundModule<typeof mt4Online> & BoundModule<typeof mt4Plugins> & BoundModule<typeof mt4Prices> & BoundModule<typeof mt4Reports> & BoundModule<typeof mt4ServerAdminDestructive> & BoundModule<typeof mt4ServerAdmin> & BoundModule<typeof mt4Symbols> & BoundModule<typeof mt4Trades> & BoundModule<typeof mt4Users> & BoundModule<typeof mt4SidecarMessaging> & BoundModule<typeof mt4SidecarPlugins> & BoundModule<typeof mt4SidecarBatchReads> & BoundModule<typeof mt4SidecarExternalCommand>, 'MT4'>;
 type MT5Namespace = CleanNamespace<BoundModule<typeof mt5Common> & BoundModule<typeof mt5Groups> & BoundModule<typeof mt5Managers> & BoundModule<typeof mt5Symbols> & BoundModule<typeof mt5Trades> & BoundModule<typeof mt5Users>, 'MT5'>;
 type BoundModule<M> = {
-    [K in keyof M]: M[K] extends (...args: infer A) => Promise<infer R> ? (...args: A) => Promise<UnwrapEnvelope<UnwrapEnvelope<R>>> : M[K];
+    [K in keyof M]: M[K] extends (...args: infer A) => Promise<infer R> ? (...args: WithRequestOptions<A>) => Promise<UnwrapEnvelope<UnwrapEnvelope<R>>> : M[K];
+};
+type IsExactly<X, Y> = (<T>() => T extends X ? 1 : 2) extends (<T>() => T extends Y ? 1 : 2) ? true : false;
+type WithRequestOptions<A extends unknown[]> = {
+    [I in keyof A]: IsExactly<NonNullable<A[I]>, RequestInit> extends true ? RequestOptions | undefined : A[I];
 };
 /**
  * Unified entry point for the CPlugin SaaS WebAPI v2 — MT4 and MT5 trading platform management.

package/dist/deadline.d.ts

@@ -0,0 +1 @@
+export declare function withDeadline<T>(timeoutMs: number, caller: AbortSignal | null | undefined, operation: (signal: AbortSignal) => Promise<T>): Promise<T>;

package/dist/environments.d.ts

@@ -2,6 +2,7 @@ export type EnvironmentName = 'prod' | 'staging' | 'custom';
 export interface ResolvedEnvironment {
     apiBaseUrl: string;
     authority: string;
+    allowInsecureLoopback?: boolean;
 }
 export type EnvironmentSelector = {
     env: 'prod' | 'staging';
@@ -9,5 +10,7 @@ export type EnvironmentSelector = {
     env: 'custom';
     apiBaseUrl: string;
     authority: string;
+    allowInsecureLoopback?: boolean;
 };
+export declare function validateServiceUrl(raw: string, name: string, allowInsecureLoopback?: boolean): string;
 export declare function resolveEnvironment(sel: EnvironmentSelector): ResolvedEnvironment;

package/dist/errors.d.ts

@@ -1,4 +1,31 @@
-export type WebApiErrorCode = 'Ok' | 'NoConnect' | 'Validation' | 'MT4Error' | 'Forbidden' | 'NotFound' | 'MT5Error' | 'Internal';
+/**
+ * Envelope error codes.
+ *
+ * - `Timeout` — a read did not finish within the request timeout; nothing was changed, safe to repeat.
+ * - `OutcomeUnknown` — a trade or change did not finish within the request timeout and may still be
+ *   applied by the server; also returned while a request with the same `Idempotency-Key` is still
+ *   running. Never repeat blindly: repeat with the same `Idempotency-Key`, or check the result first.
+ * - `Busy` — refused before it was sent to the trading server; nothing was executed, safe to repeat.
+ */
+export type WebApiErrorCode = 'Ok' | 'NoConnect' | 'Validation' | 'MT4Error' | 'Forbidden' | 'NotFound' | 'MT5Error' | 'Timeout' | 'OutcomeUnknown' | 'Busy' | 'Internal';
+/**
+ * Value of the `X-Request-Outcome` response header — set when the caller did not get the result:
+ *
+ * - `timeout` — a read ran out of time; nothing was changed.
+ * - `unknown` — a trade or change ran out of time after it was sent; it may still be applied.
+ * - `not-started` — refused before it was sent to the trading server; nothing was executed.
+ * - `in-progress` — a request with the same `Idempotency-Key` is still running; this one was not executed.
+ */
+export type RequestOutcome = 'timeout' | 'unknown' | 'not-started' | 'in-progress';
+/** Parses an `X-Request-Outcome` header value; undefined when absent or not recognised. */
+export declare function parseRequestOutcome(value: string | null | undefined): RequestOutcome | undefined;
+/** Response details the transport attaches to an `ApiError`. */
+export interface ApiErrorDetails {
+    /** `X-Request-Outcome` of the response. */
+    outcome?: RequestOutcome | undefined;
+    /** `X-Request-Timeout-Applied` of the response, in seconds. */
+    appliedTimeout?: number | undefined;
+}
 export interface PagingMeta {
     nextCursor?: string | null;
     hasMore: boolean;
@@ -17,11 +44,32 @@ export interface ApiEnvelope<T> {
     error?: ApiErrorBody | null;
     meta?: ApiMeta | null;
 }
+export declare function codeForHttpStatus(status: number): Exclude<WebApiErrorCode, 'Ok'>;
 export declare class ApiError extends Error {
     readonly code: WebApiErrorCode;
     readonly description: string | undefined;
     readonly activityId: string | undefined;
     readonly managerCode: string | number | undefined;
     readonly status: number;
-    constructor(body: ApiErrorBody, meta: ApiMeta | null | undefined, status: number);
+    /** What happened to the request when it did not complete (`X-Request-Outcome`). */
+    readonly outcome: RequestOutcome | undefined;
+    /** Server timeout that was applied to the request, in seconds (`X-Request-Timeout-Applied`). */
+    readonly appliedTimeout: number | undefined;
+    constructor(body: ApiErrorBody, meta: ApiMeta | null | undefined, status: number, details?: ApiErrorDetails);
 }
+/**
+ * True when the server reports that the operation may still be applied, or that a request
+ * with the same `Idempotency-Key` is still running. Do not repeat it blindly: repeat it with
+ * the same `Idempotency-Key` (the server then returns the original result once it exists and
+ * never executes it twice), or check the resulting state first.
+ *
+ * ! A client-side deadline abort or a network error on a POST/PATCH is equally uncertain,
+ *   but it is not an `ApiError`, so this function returns false for it.
+ */
+export declare function isOutcomeUnknown(error: unknown): error is ApiError;
+/**
+ * True when the server reports that the request changed nothing and may be repeated as is:
+ * `Busy` (refused before it was sent to the trading server) or `Timeout` (a read that ran
+ * out of time). The SDK never repeats these automatically; the caller decides when.
+ */
+export declare function isRetryable(error: unknown): error is ApiError;

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,19 +1,12 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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 type EnCommReasonFlags = typeof EnCommReasonFlags[keyof typeof EnCommReasonFlags];
-export declare const EnCommReasonFlags: {
-    readonly None: "None";
-    readonly Client: "Client";
-    readonly Expert: "Expert";
-    readonly Dealer: "Dealer";
-    readonly ExternalClient: "ExternalClient";
-    readonly Mobile: "Mobile";
-    readonly Web: "Web";
-    readonly Signal: "Signal";
-    readonly All: "All";
-};
+/**
+ * Flags: names of the set bits joined by ", " ("Client, Expert"), "None" when none is set; a set bit without a name is "Bit<n>" (bit number). Bits: Client = 0x1, Expert = 0x2, Dealer = 0x4, ExternalClient = 0x8, Mobile = 0x10, Web = 0x20, Signal = 0x40. Accepted on input, never written: All = Client, Expert, Dealer, ExternalClient, Mobile, Web, Signal.
+ * @pattern ^[A-Za-z][A-Za-z0-9]*(, [A-Za-z][A-Za-z0-9]*)*$
+ */
+export type EnCommReasonFlags = string;

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,16 +1,12 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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 type EnExpirationFlags = typeof EnExpirationFlags[keyof typeof EnExpirationFlags];
-export declare const EnExpirationFlags: {
-    readonly None: "None";
-    readonly GtC: "GtC";
-    readonly Day: "Day";
-    readonly Specified: "Specified";
-    readonly SpecifiedDay: "SpecifiedDay";
-    readonly All: "All";
-};
+/**
+ * Flags: names of the set bits joined by ", " ("GtC, Day"), "None" when none is set; a set bit without a name is "Bit<n>" (bit number). Bits: GtC = 0x1, Day = 0x2, Specified = 0x4, SpecifiedDay = 0x8. Accepted on input, never written: All = GtC, Day, Specified, SpecifiedDay.
+ * @pattern ^[A-Za-z][A-Za-z0-9]*(, [A-Za-z][A-Za-z0-9]*)*$
+ */
+export type EnExpirationFlags = string;

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

@@ -1,15 +1,12 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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 type EnFillingFlags = typeof EnFillingFlags[keyof typeof EnFillingFlags];
-export declare const EnFillingFlags: {
-    readonly None: "None";
-    readonly FoK: "FoK";
-    readonly IoC: "IoC";
-    readonly BoC: "BoC";
-    readonly All: "All";
-};
+/**
+ * Flags: names of the set bits joined by ", " ("FoK, IoC"), "None" when none is set; a set bit without a name is "Bit<n>" (bit number). Bits: FoK = 0x1, IoC = 0x2, BoC = 0x4. Accepted on input, never written: All = FoK, IoC, BoC.
+ * @pattern ^[A-Za-z][A-Za-z0-9]*(, [A-Za-z][A-Za-z0-9]*)*$
+ */
+export type EnFillingFlags = string;

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,12 +1,12 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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 type EnInstantFlags = typeof EnInstantFlags[keyof typeof EnInstantFlags];
-export declare const EnInstantFlags: {
-    readonly None: "None";
-    readonly All: "All";
-};
+/**
+ * Flags: names of the set bits joined by ", " ("FastConfirmation"), "None" when none is set; a set bit without a name is "Bit<n>" (bit number). Bits: FastConfirmation = 0x1.
+ * @pattern ^[A-Za-z][A-Za-z0-9]*(, [A-Za-z][A-Za-z0-9]*)*$
+ */
+export type EnInstantFlags = string;

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,12 +1,12 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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 type EnMarginCalcFlags = typeof EnMarginCalcFlags[keyof typeof EnMarginCalcFlags];
-export declare const EnMarginCalcFlags: {
-    readonly None: "None";
-    readonly ClearAcc: "ClearAcc";
-};
+/**
+ * Flags: names of the set bits joined by ", " ("ClearAcc"), "None" when none is set; a set bit without a name is "Bit<n>" (bit number). Bits: ClearAcc = 0x1.
+ * @pattern ^[A-Za-z][A-Za-z0-9]*(, [A-Za-z][A-Za-z0-9]*)*$
+ */
+export type EnMarginCalcFlags = string;

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

@@ -1,17 +1,12 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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 type EnMarginFlags = typeof EnMarginFlags[keyof typeof EnMarginFlags];
-export declare const EnMarginFlags: {
-    readonly None: "None";
-    readonly CheckProcess: "CheckProcess";
-    readonly CheckSLTP: "CheckSLTP";
-    readonly HedgeLargeLeg: "HedgeLargeLeg";
-    readonly ExcludePl: "ExcludePl";
-    readonly All: "All";
-    readonly RecalcRates: "RecalcRates";
-};
+/**
+ * Flags: names of the set bits joined by ", " ("CheckProcess, CheckSLTP"), "None" when none is set; a set bit without a name is "Bit<n>" (bit number). Bits: CheckProcess = 0x1, CheckSLTP = 0x2, HedgeLargeLeg = 0x4, ExcludePl = 0x8, RecalcRates = 0x10. Accepted on input, never written: All = CheckProcess, CheckSLTP, HedgeLargeLeg, ExcludePl.
+ * @pattern ^[A-Za-z][A-Za-z0-9]*(, [A-Za-z][A-Za-z0-9]*)*$
+ */
+export type EnMarginFlags = string;

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.

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

@@ -1,5 +1,5 @@
 /**
- * Generated by orval v8.19.0 🍺
+ * Generated by orval 🍺
  * 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.