@mywebapi.com/sdk 0.1.2 → 0.3.0

package/dist/generated/model/postSrvLiveUpdateStartParams.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/postSrvRestartParams.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/postSymbolSendTickParams.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/postTradeCheckStopsParams.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/postTradesSyncStartParams.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/postUserPasswordSetLoginParams.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/postUsersSyncStartParams.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/profitCalculationMode.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/requestMode.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/resultCode.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/serverRole.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/stringApiResponse.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/swapType.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/symbolExecMode.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/symbolPriceDirection.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/synchronizationMode.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/tickRequestFlags.d.ts

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

package/dist/generated/model/tradeActivationFlags.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 TradeActivationFlags = typeof TradeActivationFlags[keyof typeof TradeActivationFlags];
-export declare const TradeActivationFlags: {
-    readonly None: "None";
-    readonly NoLimit: "NoLimit";
-    readonly NoStop: "NoStop";
-    readonly NoSLimit: "NoSLimit";
-    readonly NoSL: "NoSL";
-    readonly NoTP: "NoTP";
-    readonly NoSO: "NoSO";
-    readonly NoExpiration: "NoExpiration";
-    readonly All: "All";
-};
+/**
+ * Flags: names of the set bits joined by ", " ("NoLimit, NoStop"), "None" when none is set; a set bit without a name is "Bit<n>" (bit number). Bits: NoLimit = 0x1, NoStop = 0x2, NoSLimit = 0x4, NoSL = 0x8, NoTP = 0x10, NoSO = 0x20, NoExpiration = 0x40. Accepted on input, never written: All = NoLimit, NoStop, NoSLimit, NoSL, NoTP, NoSO, NoExpiration.
+ * @pattern ^[A-Za-z][A-Za-z0-9]*(, [A-Za-z][A-Za-z0-9]*)*$
+ */
+export type TradeActivationFlags = string;

package/dist/generated/model/tradeCommand.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/tradeMode.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/tradeModifyFlags.d.ts

@@ -1,23 +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
  */
 /**
- * also used for Deal,Order,Position
+ * also used for Deal,Order,Position<br/>Flags: names of the set bits joined by ", " ("Admin, Manager"), "None" when none is set; a set bit without a name is "Bit<n>" (bit number). Bits: Admin = 0x1, Manager = 0x2, Position = 0x4, Restore = 0x8, ApiAdmin = 0x10, ApiManager = 0x20, ApiServer = 0x40, ApiGateway = 0x80. Accepted on input, never written: All = Admin, Manager, Position, Restore, ApiAdmin, ApiManager, ApiServer, ApiGateway.
+ * @pattern ^[A-Za-z][A-Za-z0-9]*(, [A-Za-z][A-Za-z0-9]*)*$
  */
-export type TradeModifyFlags = typeof TradeModifyFlags[keyof typeof TradeModifyFlags];
-export declare const TradeModifyFlags: {
-    readonly None: "None";
-    readonly Admin: "Admin";
-    readonly Manager: "Manager";
-    readonly Position: "Position";
-    readonly Restore: "Restore";
-    readonly ApiAdmin: "ApiAdmin";
-    readonly ApiManager: "ApiManager";
-    readonly ApiServer: "ApiServer";
-    readonly ApiGateway: "ApiGateway";
-    readonly All: "All";
-};
+export type TradeModifyFlags = string;

package/dist/generated/model/tradeRecordReason.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/tradeRecordState.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/usersRights.d.ts

@@ -1,32 +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
  */
 /**
- * MT5 user permission flags. Values mirror CIMTUser.EnUsersRights.
- *             Serializes as a string (not a number) via V2JsonContext.UseStringEnumConverter.
+ * MT5 user permission flags. Values mirror CIMTUser.EnUsersRights.<br/>Flags: names of the set bits joined by ", " ("Enabled, Password"), "None" when none is set; a set bit without a name is "Bit<n>" (bit number). Bits: Enabled = 0x1, Password = 0x2, TradeDisabled = 0x4, Investor = 0x8, Confirmed = 0x10, Trailing = 0x20, Expert = 0x40, Obsolete = 0x80, Reports = 0x100, Readonly = 0x200, ResetPass = 0x400, OTPEnabled = 0x800, SponsoredHosting = 0x2000, APIEnabled = 0x4000, PushNotification = 0x8000, Technical = 0x10000, ExcludeReports = 0x20000.
+ * @pattern ^[A-Za-z][A-Za-z0-9]*(, [A-Za-z][A-Za-z0-9]*)*$
  */
-export type UsersRights = typeof UsersRights[keyof typeof UsersRights];
-export declare const UsersRights: {
-    readonly None: "None";
-    readonly Enabled: "Enabled";
-    readonly Password: "Password";
-    readonly TradeDisabled: "TradeDisabled";
-    readonly Investor: "Investor";
-    readonly Confirmed: "Confirmed";
-    readonly Trailing: "Trailing";
-    readonly Expert: "Expert";
-    readonly Obsolete: "Obsolete";
-    readonly Reports: "Reports";
-    readonly Readonly: "Readonly";
-    readonly ResetPass: "ResetPass";
-    readonly OTPEnabled: "OTPEnabled";
-    readonly SponsoredHosting: "SponsoredHosting";
-    readonly APIEnabled: "APIEnabled";
-    readonly PushNotification: "PushNotification";
-    readonly Technical: "Technical";
-    readonly ExcludeReports: "ExcludeReports";
-};
+export type UsersRights = string;

package/dist/generated/model/watchdogFailoverMode.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/watchdogState.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/webApiErrorCode.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.
@@ -20,5 +20,8 @@ export declare const WebApiErrorCode: {
     readonly Forbidden: "Forbidden";
     readonly NotFound: "NotFound";
     readonly MT5Error: "MT5Error";
+    readonly Timeout: "Timeout";
+    readonly OutcomeUnknown: "OutcomeUnknown";
+    readonly Busy: "Busy";
     readonly Internal: "Internal";
 };

package/dist/generated/mt4-v2-authentication.d.ts

@@ -1,11 +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
  */
 import type { BooleanApiResponse, PostUserPasswordSetLoginParams } from './model';
+import { customFetch } from '../mutator';
 export type postUserPasswordCheckLoginResponse200 = {
     data: BooleanApiResponse;
     status: 200;
@@ -27,9 +28,11 @@ export declare const getPostUserPasswordCheckLoginUrl: (tradePlatform: string, l
  * Read-only operation: no state changes. Idempotency-Key on this endpoint
  * is supported but rarely useful — pin if your retry policy expects the
  * same answer across attempts.
+ *
+ * **Timeout:** 15 s by default, adjustable per request with the `X-Request-Timeout` header. When the trade server does not answer in time: The operation may still be completed by the server (`X-Request-Outcome: unknown`): check its result before repeating it.
  * @summary Verify account password
  */
-export declare const postUserPasswordCheckLogin: (tradePlatform: string, login: number, postUserPasswordCheckLoginBody?: string, options?: RequestInit) => Promise<postUserPasswordCheckLoginResponse>;
+export declare const postUserPasswordCheckLogin: (tradePlatform: string, login: number, postUserPasswordCheckLoginBody?: string, options?: Parameters<typeof customFetch>[1]) => Promise<postUserPasswordCheckLoginResponse>;
 export type postUserPasswordSetLoginResponse200 = {
     data: BooleanApiResponse;
     status: 200;
@@ -59,6 +62,9 @@ export declare const getPostUserPasswordSetLoginUrl: (tradePlatform: string, log
  * though the password is the same), which is harmless but generates audit
  * noise. With the header, the second call short-circuits to the cached
  * response.
+ *
+ *
+ * **Timeout:** 15 s by default, adjustable per request with the `X-Request-Timeout` header. When the trade server does not answer in time: The operation may still be completed by the server (`X-Request-Outcome: unknown`): check its result before repeating it.
  * @summary Set account password
  */
-export declare const postUserPasswordSetLogin: (tradePlatform: string, login: number, postUserPasswordSetLoginBody?: string, params?: PostUserPasswordSetLoginParams, options?: RequestInit) => Promise<postUserPasswordSetLoginResponse>;
+export declare const postUserPasswordSetLogin: (tradePlatform: string, login: number, postUserPasswordSetLoginBody?: string, params?: PostUserPasswordSetLoginParams, options?: Parameters<typeof customFetch>[1]) => Promise<postUserPasswordSetLoginResponse>;

package/dist/generated/mt4-v2-backup-destructive.d.ts

@@ -1,11 +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
  */
 import type { BooleanApiResponse, MT4TradeRestoreInput, MT4TradeRestoreResultListApiResponse, MT4UserRestoreInput, PostBackupRestoreOrdersParams, PostBackupRestoreUsersParams } from './model';
+import { customFetch } from '../mutator';
 export type postBackupRestoreUsersResponse200 = {
     data: BooleanApiResponse;
     status: 200;
@@ -29,9 +30,12 @@ export declare const getPostBackupRestoreUsersUrl: (tradePlatform: string, param
  * whether the write happened. Without the key, retry will double-write.
  * <br>
  * Batch cap: 10000 records per call. Larger restores must be split.
+ *
+ *
+ * **Timeout:** 60 s by default, adjustable per request with the `X-Request-Timeout` header. When the trade server does not answer in time: The operation may still be completed by the server (`X-Request-Outcome: unknown`): check its result before repeating it.
  * @summary Restore users from backup
  */
-export declare const postBackupRestoreUsers: (tradePlatform: string, mT4UserRestoreInput?: MT4UserRestoreInput[], params?: PostBackupRestoreUsersParams, options?: RequestInit) => Promise<postBackupRestoreUsersResponse>;
+export declare const postBackupRestoreUsers: (tradePlatform: string, mT4UserRestoreInput?: MT4UserRestoreInput[], params?: PostBackupRestoreUsersParams, options?: Parameters<typeof customFetch>[1]) => Promise<postBackupRestoreUsersResponse>;
 export type postBackupRestoreOrdersResponse200 = {
     data: MT4TradeRestoreResultListApiResponse;
     status: 200;
@@ -52,6 +56,9 @@ export declare const getPostBackupRestoreOrdersUrl: (tradePlatform: string, para
  * <br>
  * Idempotency-Key header is <b>strongly recommended</b>. Batch cap:
  * 10000 records per call.
+ *
+ *
+ * **Timeout:** 60 s by default, adjustable per request with the `X-Request-Timeout` header. When the trade server does not answer in time: The operation may still be completed by the server (`X-Request-Outcome: unknown`): check its result before repeating it.
  * @summary Restore orders from backup
  */
-export declare const postBackupRestoreOrders: (tradePlatform: string, mT4TradeRestoreInput?: MT4TradeRestoreInput[], params?: PostBackupRestoreOrdersParams, options?: RequestInit) => Promise<postBackupRestoreOrdersResponse>;
+export declare const postBackupRestoreOrders: (tradePlatform: string, mT4TradeRestoreInput?: MT4TradeRestoreInput[], params?: PostBackupRestoreOrdersParams, options?: Parameters<typeof customFetch>[1]) => Promise<postBackupRestoreOrdersResponse>;

package/dist/generated/mt4-v2-backup.d.ts

@@ -1,11 +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
  */
 import type { GetBackupRequestOrdersFileParams, GetBackupRequestUsersFileParams, MT4BackupInfoListApiResponse, MT4TradeListApiResponse, MT4UserListApiResponse } from './model';
+import { customFetch } from '../mutator';
 export type getBackupInfoUsersModeResponse200 = {
     data: MT4BackupInfoListApiResponse;
     status: 200;
@@ -25,9 +26,12 @@ export declare const getGetBackupInfoUsersModeUrl: (tradePlatform: string, mode:
  * <br>`mode` is the server-defined backup mode selector (typical
  * values: `0` = daily, `1` = weekly — confirm against your
  * server's `ConBackup` configuration).
+ *
+ *
+ * **Timeout:** 30 s by default, adjustable per request with the `X-Request-Timeout` header. When the trade server does not answer in time: Nothing was changed; the request is safe to repeat.
  * @summary List user backup files
  */
-export declare const getBackupInfoUsersMode: (tradePlatform: string, mode: number, options?: RequestInit) => Promise<getBackupInfoUsersModeResponse>;
+export declare const getBackupInfoUsersMode: (tradePlatform: string, mode: number, options?: Parameters<typeof customFetch>[1]) => Promise<getBackupInfoUsersModeResponse>;
 export type getBackupInfoOrdersModeResponse200 = {
     data: MT4BackupInfoListApiResponse;
     status: 200;
@@ -44,9 +48,11 @@ export declare const getGetBackupInfoOrdersModeUrl: (tradePlatform: string, mode
  * `BackupInfoOrders(int mode)`. Order-side counterpart of
  * `BackupInfoUsers` — same shape, different catalog.
  * Read-only operation.
+ *
+ * **Timeout:** 30 s by default, adjustable per request with the `X-Request-Timeout` header. When the trade server does not answer in time: Nothing was changed; the request is safe to repeat.
  * @summary List order backup files
  */
-export declare const getBackupInfoOrdersMode: (tradePlatform: string, mode: number, options?: RequestInit) => Promise<getBackupInfoOrdersModeResponse>;
+export declare const getBackupInfoOrdersMode: (tradePlatform: string, mode: number, options?: Parameters<typeof customFetch>[1]) => Promise<getBackupInfoOrdersModeResponse>;
 export type getBackupRequestUsersFileResponse200 = {
     data: MT4UserListApiResponse;
     status: 200;
@@ -73,9 +79,12 @@ export declare const getGetBackupRequestUsersFileUrl: (tradePlatform: string, fi
  * optional `limit` query truncates the response server-side
  * (default 10000, max 100000). The wrapper still loads the full
  * file regardless of limit — limit only caps the JSON response size.
+ *
+ *
+ * **Timeout:** 30 s by default, adjustable per request with the `X-Request-Timeout` header. When the trade server does not answer in time: Nothing was changed; the request is safe to repeat.
  * @summary Read users from backup
  */
-export declare const getBackupRequestUsersFile: (tradePlatform: string, file: string, params?: GetBackupRequestUsersFileParams, options?: RequestInit) => Promise<getBackupRequestUsersFileResponse>;
+export declare const getBackupRequestUsersFile: (tradePlatform: string, file: string, params?: GetBackupRequestUsersFileParams, options?: Parameters<typeof customFetch>[1]) => Promise<getBackupRequestUsersFileResponse>;
 export type getBackupRequestOrdersFileResponse200 = {
     data: MT4TradeListApiResponse;
     status: 200;
@@ -93,6 +102,8 @@ export declare const getGetBackupRequestOrdersFileUrl: (tradePlatform: string, f
  * counterpart of `BackupRequestUsers`. Same caveats:
  * read-only, full file loaded server-side regardless of `limit`,
  * destructive restore is a separate (Wave 4b) operation.
+ *
+ * **Timeout:** 30 s by default, adjustable per request with the `X-Request-Timeout` header. When the trade server does not answer in time: Nothing was changed; the request is safe to repeat.
  * @summary Read orders from backup
  */
-export declare const getBackupRequestOrdersFile: (tradePlatform: string, file: string, params?: GetBackupRequestOrdersFileParams, options?: RequestInit) => Promise<getBackupRequestOrdersFileResponse>;
+export declare const getBackupRequestOrdersFile: (tradePlatform: string, file: string, params?: GetBackupRequestOrdersFileParams, options?: Parameters<typeof customFetch>[1]) => Promise<getBackupRequestOrdersFileResponse>;

package/dist/generated/mt4-v2-common.d.ts

@@ -1,11 +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
  */
 import type { DateTimeApiResponse, GetJournalRequestParams, MT4CommonApiResponse, MT4ServerLogListApiResponse } from './model';
+import { customFetch } from '../mutator';
 export type getServerTimeMT4Response200 = {
     data: DateTimeApiResponse;
     status: 200;
@@ -20,9 +21,11 @@ export declare const getGetServerTimeMT4Url: (tradePlatform: string) => string;
  *
  * Smoke-test endpoint exercising the v2 envelope. Returns current MT4
  * server time wrapped in ApiResponse<DateTime>.
+ *
+ * **Timeout:** 10 s by default, adjustable per request with the `X-Request-Timeout` header. When the trade server does not answer in time: Nothing was changed; the request is safe to repeat.
  * @summary Get server time
  */
-export declare const getServerTimeMT4: (tradePlatform: string, options?: RequestInit) => Promise<getServerTimeMT4Response>;
+export declare const getServerTimeMT4: (tradePlatform: string, options?: Parameters<typeof customFetch>[1]) => Promise<getServerTimeMT4Response>;
 export type getManagerCommonResponse200 = {
     data: MT4CommonApiResponse;
     status: 200;
@@ -38,9 +41,11 @@ export declare const getGetManagerCommonUrl: (tradePlatform: string) => string;
  * Returns MT4Common DTO — server name, broker, server version/build,
  * time zone. Schema is decoupled from the wrapper's ConCommon: v2
  * clients are protected from MetaQuotes schema changes.
+ *
+ * **Timeout:** 10 s by default, adjustable per request with the `X-Request-Timeout` header. When the trade server does not answer in time: Nothing was changed; the request is safe to repeat.
  * @summary Get manager common settings
  */
-export declare const getManagerCommon: (tradePlatform: string, options?: RequestInit) => Promise<getManagerCommonResponse>;
+export declare const getManagerCommon: (tradePlatform: string, options?: Parameters<typeof customFetch>[1]) => Promise<getManagerCommonResponse>;
 export type getJournalRequestResponse200 = {
     data: MT4ServerLogListApiResponse;
     status: 200;
@@ -61,6 +66,8 @@ export declare const getGetJournalRequestUrl: (tradePlatform: string, params?: G
  * Heavier endpoint — large date windows return large arrays. Pair with
  * reasonable `from`/`to` bounds; consider `Idempotency-Key`
  * for retry safety on slow links.
+ *
+ * **Timeout:** 30 s by default, adjustable per request with the `X-Request-Timeout` header. When the trade server does not answer in time: Nothing was changed; the request is safe to repeat.
  * @summary Get server journal
  */
-export declare const getJournalRequest: (tradePlatform: string, params?: GetJournalRequestParams, options?: RequestInit) => Promise<getJournalRequestResponse>;
+export declare const getJournalRequest: (tradePlatform: string, params?: GetJournalRequestParams, options?: Parameters<typeof customFetch>[1]) => Promise<getJournalRequestResponse>;