@mywebapi.com/sdk 0.1.0

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

@@ -0,0 +1,169 @@
+/**
+ * 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 { BooleanApiResponse, GetDailyReportsRequestExParams, GetDailyReportsRequestParams, GetPerformanceRequestParams, GetReportsRequestParams, Int32MT4DailyReportListDictionaryApiResponse, MT4DailyReportListApiResponse, MT4PerformanceListApiResponse, MT4TradeListApiResponse, PostDailySyncStartParams } from './model';
+export type getPerformanceRequestResponse200 = {
+    data: MT4PerformanceListApiResponse;
+    status: 200;
+};
+export type getPerformanceRequestResponseSuccess = (getPerformanceRequestResponse200) & {
+    headers: Headers;
+};
+export type getPerformanceRequestResponse = (getPerformanceRequestResponseSuccess);
+export declare const getGetPerformanceRequestUrl: (tradePlatform: string, params?: GetPerformanceRequestParams) => string;
+/**
+ * Time series of MT4 server resource snapshots — CPU, memory, network, sockets, connected-users — captured at server-defined cadence.
+ *
+ * Manager-live read (round-trip to MT4 server). The MT4 server records
+ * these snapshots periodically (typically every five minutes, broker-
+ * configurable). Pass from as the earliest timestamp
+ * to include; the server returns every snapshot at or after that point
+ * up to the present, in ascending `Ctm` order. Useful for capacity
+ * dashboards, oncall incident timelines, and load investigations. Pump
+ * cache is NOT consulted — data reflects the authoritative server log.
+ * Returns an empty list (Ok envelope, not an error) when the window
+ * contains no snapshots.
+ * @summary Get server performance series
+ */
+export declare const getPerformanceRequest: (tradePlatform: string, params?: GetPerformanceRequestParams, options?: RequestInit) => Promise<getPerformanceRequestResponse>;
+export type getReportsRequestResponse200 = {
+    data: MT4TradeListApiResponse;
+    status: 200;
+};
+export type getReportsRequestResponseSuccess = (getReportsRequestResponse200) & {
+    headers: Headers;
+};
+export type getReportsRequestResponse = (getReportsRequestResponseSuccess);
+export declare const getGetReportsRequestUrl: (tradePlatform: string, params?: GetReportsRequestParams) => string;
+/**
+ * Closed-trade reports for a batch of account logins within a time window — the data set that drives broker financial reporting (PnL, commissions, taxes) and customer trade-history exports.
+ *
+ * Manager-live read (round-trip to MT4 server). Pass logins as repeated
+ * query parameters: `?logins=1001&logins=1002&logins=1003`.
+ * Server-side billing counts this as one Manager request regardless of
+ * batch size — prefer one batched call over a per-login loop.
+ *
+ * The wrapper returns a dictionary keyed by order ticket; the v2 envelope
+ * flattens it to a list. Missing logins are silently omitted (no error
+ * envelope). The optional name parameter selects a
+ * server-defined report template — leave it null/empty to use the
+ * default `"RTL_report"` template (closed trades within the window).
+ *
+ * Pump cache is NOT consulted — data reflects authoritative server
+ * history. Note: the wrapper comment warns that asking for a window
+ * where the manager account lacks the `Reports` permission may
+ * cause MT4 to drop the manager connection; this endpoint guards that
+ * indirectly via the API-side `ResourceAccess` check, but a broker
+ * that mis-configured the underlying manager rights can still observe
+ * transient connection bounces.
+ * @summary Get closed-trade reports
+ */
+export declare const getReportsRequest: (tradePlatform: string, params?: GetReportsRequestParams, options?: RequestInit) => Promise<getReportsRequestResponse>;
+export type getDailyReportsRequestResponse200 = {
+    data: MT4DailyReportListApiResponse;
+    status: 200;
+};
+export type getDailyReportsRequestResponseSuccess = (getDailyReportsRequestResponse200) & {
+    headers: Headers;
+};
+export type getDailyReportsRequestResponse = (getDailyReportsRequestResponseSuccess);
+export declare const getGetDailyReportsRequestUrl: (tradePlatform: string, params?: GetDailyReportsRequestParams) => string;
+/**
+ * End-of-day balance/equity/PnL snapshots for a batch of account logins within a date window — the broker daily-report data set, flat shape (one row per (login, day) pair).
+ *
+ * Manager-live read (round-trip to MT4 server). Pass logins as repeated
+ * query parameters: `?logins=1001&logins=1002&logins=1003`.
+ * Server-side billing counts this as one Manager request regardless of
+ * batch size — prefer one batched call over a per-login loop.
+ *
+ * Each row carries its own `Login` field, so the flat shape is
+ * joinable on the client side. The MT4 server returns dates in its
+ * local time zone, **not** UTC — clients should treat `Ctm` as
+ * "broker day boundary" and convert as appropriate.
+ *
+ * Note: the wrapper warns that asking for a window where the manager
+ * account lacks the `Automatic server reports` permission may
+ * cause MT4 to drop the manager connection. The API-side
+ * `ResourceAccess` check is an indirect guard; a broker that
+ * mis-configured the underlying manager rights can still observe
+ * transient connection bounces.
+ * @summary Get daily reports
+ */
+export declare const getDailyReportsRequest: (tradePlatform: string, params?: GetDailyReportsRequestParams, options?: RequestInit) => Promise<getDailyReportsRequestResponse>;
+export type getDailyReportsRequestExResponse200 = {
+    data: Int32MT4DailyReportListDictionaryApiResponse;
+    status: 200;
+};
+export type getDailyReportsRequestExResponseSuccess = (getDailyReportsRequestExResponse200) & {
+    headers: Headers;
+};
+export type getDailyReportsRequestExResponse = (getDailyReportsRequestExResponseSuccess);
+export declare const getGetDailyReportsRequestExUrl: (tradePlatform: string, params?: GetDailyReportsRequestExParams) => string;
+/**
+ * Same data set as `DailyReportsRequest`, but server-side grouped by login. Convenience shape for clients that pivot the data per-account (per-day rollups, account dashboards).
+ *
+ * Manager-live read — single round-trip to MT4 server, identical billing
+ * cost to `DailyReportsRequest`. The wrapper returns a sorted-list
+ * of sorted-lists (by login, then by date); the v2 envelope flattens
+ * the inner list to a chronologically-ordered `MT4DailyReport`
+ * array, leaving the outer keying by login.
+ *
+ * JSON shape: `{ "817542": [ ... ], "1001": [ ... ] }` — JSON
+ * object keys are strings, so int logins are stringified. Clients
+ * should parse keys back to int if needed.
+ * @summary Get daily reports (grouped)
+ */
+export declare const getDailyReportsRequestEx: (tradePlatform: string, params?: GetDailyReportsRequestExParams, options?: RequestInit) => Promise<getDailyReportsRequestExResponse>;
+export type postDailySyncStartResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type postDailySyncStartResponseSuccess = (postDailySyncStartResponse200) & {
+    headers: Headers;
+};
+export type postDailySyncStartResponse = (postDailySyncStartResponseSuccess);
+export declare const getPostDailySyncStartUrl: (tradePlatform: string, params?: PostDailySyncStartParams) => string;
+/**
+ * Opens a server-side incremental sync session for daily reports modified at or after timestamp. Follow up with `DailySyncRead` to retrieve the snapshot.
+ *
+ * Manager-live POST (modifies server-side session state). The two-call
+ * cycle `DailySyncStart → DailySyncRead` is the broker pattern for
+ * pulling only-changed-since-last-poll daily reports; pass
+ * `timestamp=0` to request all records.
+ *
+ * `timestamp` is a Unix epoch second (int32) in MT4 server-local
+ * time, not UTC. Wrapper marshals it directly to `__time32_t` —
+ * pre-1970 / post-2038 values are out of range.
+ *
+ * Returns a bare success envelope (no payload); the actual data comes
+ * from a subsequent `DailySyncRead` call.
+ * @summary Start daily-report sync
+ */
+export declare const postDailySyncStart: (tradePlatform: string, params?: PostDailySyncStartParams, options?: RequestInit) => Promise<postDailySyncStartResponse>;
+export type postDailySyncReadResponse200 = {
+    data: MT4DailyReportListApiResponse;
+    status: 200;
+};
+export type postDailySyncReadResponseSuccess = (postDailySyncReadResponse200) & {
+    headers: Headers;
+};
+export type postDailySyncReadResponse = (postDailySyncReadResponseSuccess);
+export declare const getPostDailySyncReadUrl: (tradePlatform: string) => string;
+/**
+ * Drains the daily-report snapshot opened by the most recent `DailySyncStart` call. Returns every record reserved by the server in that sync session.
+ *
+ * Manager-live POST (consumes server-side session state — the snapshot
+ * is dropped after a successful read). Empty payload (`[]`) is a
+ * valid response when the snapshot held no records; this is NOT an
+ * error.
+ *
+ * Call `DailySyncStart` first; calling `DailySyncRead` without
+ * a prior `DailySyncStart` may return an empty list or a non-Ok
+ * `managerAPICode` depending on server build.
+ * @summary Read daily-report sync
+ */
+export declare const postDailySyncRead: (tradePlatform: string, options?: RequestInit) => Promise<postDailySyncReadResponse>;

package/dist/generated/mt4-v2-server-admin-destructive.d.ts

@@ -0,0 +1,87 @@
+/**
+ * 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 { BooleanApiResponse, PostSrvChartsSyncParams, PostSrvFeedsRestartParams, PostSrvLiveUpdateStartParams, PostSrvRestartParams } from './model';
+export type postSrvRestartResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type postSrvRestartResponseSuccess = (postSrvRestartResponse200) & {
+    headers: Headers;
+};
+export type postSrvRestartResponse = (postSrvRestartResponseSuccess);
+export declare const getPostSrvRestartUrl: (tradePlatform: string, params?: PostSrvRestartParams) => string;
+/**
+ * Soft-restart of the MT4 server process. Destructive — requires `?confirm=true`.
+ *
+ * Manager (live) call to the wrapper's `SrvRestart()`. The current
+ * manager connection is dropped during the restart cycle — clients
+ * should expect the next request to surface a fresh login. Audit lines
+ * are emitted on both sides of the wrapper call (independently of the
+ * HTTP response).
+ * <br>
+ * The `?confirm=true` guard rejects calls without the literal
+ * query string. It is a deliberateness signal, NOT an authorization
+ * mechanism — admin rights are still enforced separately.
+ * @summary Restart server
+ */
+export declare const postSrvRestart: (tradePlatform: string, params?: PostSrvRestartParams, options?: RequestInit) => Promise<postSrvRestartResponse>;
+export type postSrvChartsSyncResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type postSrvChartsSyncResponseSuccess = (postSrvChartsSyncResponse200) & {
+    headers: Headers;
+};
+export type postSrvChartsSyncResponse = (postSrvChartsSyncResponseSuccess);
+export declare const getPostSrvChartsSyncUrl: (tradePlatform: string, params?: PostSrvChartsSyncParams) => string;
+/**
+ * Force chart-history resync across the plugin set. Destructive — requires `?confirm=true`.
+ *
+ * Manager (live) call to the wrapper's `SrvChartsSync()`. Forces
+ * the MT4 server to walk every plugin's chart-history feed and bring
+ * the local cache in sync. Idempotent — running twice is a no-op
+ * against an already-synced state.
+ * @summary Force chart resync
+ */
+export declare const postSrvChartsSync: (tradePlatform: string, params?: PostSrvChartsSyncParams, options?: RequestInit) => Promise<postSrvChartsSyncResponse>;
+export type postSrvLiveUpdateStartResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type postSrvLiveUpdateStartResponseSuccess = (postSrvLiveUpdateStartResponse200) & {
+    headers: Headers;
+};
+export type postSrvLiveUpdateStartResponse = (postSrvLiveUpdateStartResponseSuccess);
+export declare const getPostSrvLiveUpdateStartUrl: (tradePlatform: string, params?: PostSrvLiveUpdateStartParams) => string;
+/**
+ * Kick the LiveUpdate distributor. Destructive — requires `?confirm=true`.
+ *
+ * Manager (live) call to the wrapper's `SrvLiveUpdateStart()`.
+ * Starts (or restarts) the server's outbound LiveUpdate broadcast.
+ * Affects connected client terminals — they may receive an update prompt.
+ * @summary Start LiveUpdate distributor
+ */
+export declare const postSrvLiveUpdateStart: (tradePlatform: string, params?: PostSrvLiveUpdateStartParams, options?: RequestInit) => Promise<postSrvLiveUpdateStartResponse>;
+export type postSrvFeedsRestartResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type postSrvFeedsRestartResponseSuccess = (postSrvFeedsRestartResponse200) & {
+    headers: Headers;
+};
+export type postSrvFeedsRestartResponse = (postSrvFeedsRestartResponseSuccess);
+export declare const getPostSrvFeedsRestartUrl: (tradePlatform: string, params?: PostSrvFeedsRestartParams) => string;
+/**
+ * Restart all running data feeders. Destructive — requires `?confirm=true`.
+ *
+ * Manager (live) call to the wrapper's `SrvFeedsRestart()`.
+ * Cycles all running quote/news feeders. May cause a brief gap in
+ * the tick stream — typically a second or two. Idempotent.
+ * @summary Restart data feeders
+ */
+export declare const postSrvFeedsRestart: (tradePlatform: string, params?: PostSrvFeedsRestartParams, options?: RequestInit) => Promise<postSrvFeedsRestartResponse>;

package/dist/generated/mt4-v2-server-admin.d.ts

@@ -0,0 +1,80 @@
+/**
+ * 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 { BooleanApiResponse, GetSrvFeedersParams, MT4FeederListApiResponse, MT4NotificationsSendRequest, StringApiResponse } from './model';
+export type getSrvFeedersResponse200 = {
+    data: MT4FeederListApiResponse;
+    status: 200;
+};
+export type getSrvFeedersResponseSuccess = (getSrvFeedersResponse200) & {
+    headers: Headers;
+};
+export type getSrvFeedersResponse = (getSrvFeedersResponseSuccess);
+export declare const getGetSrvFeedersUrl: (tradePlatform: string, params?: GetSrvFeedersParams) => string;
+/**
+ * List of running data feeders on the MT4 server (admin-only read).
+ *
+ * Manager (live) call to the wrapper's `SrvFeeders`. Returns the
+ * current set of running feeder configurations as opposed to
+ * `CfgRequestFeeder` which returns the static configuration. The
+ * data shape is the same as `CfgRequestFeeder` — `MT4Feeder`
+ * — and the credential (`Password`) is intentionally excluded.
+ * <br>
+ * Sorted by `Name` ascending. Paged with the same cursor codec as
+ * the rest of the v2 paged endpoints (`Name` is the cursor key).
+ * @summary List data feeders
+ */
+export declare const getSrvFeeders: (tradePlatform: string, params?: GetSrvFeedersParams, options?: RequestInit) => Promise<getSrvFeedersResponse>;
+export type getLicenseCheckLicenseNameResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type getLicenseCheckLicenseNameResponseSuccess = (getLicenseCheckLicenseNameResponse200) & {
+    headers: Headers;
+};
+export type getLicenseCheckLicenseNameResponse = (getLicenseCheckLicenseNameResponseSuccess);
+export declare const getGetLicenseCheckLicenseNameUrl: (tradePlatform: string, licenseName: string) => string;
+/**
+ * Check a license name against the MT4 server's license registry — admin-only read.
+ *
+ * Manager (live) call to the wrapper's `LicenseCheck(name)`.
+ * Returns a bare `bool` payload: `true` when the wrapper's
+ * result code is `Ok`, indicating the license is recognized;
+ * `false` on any non-Ok code (covers both "license not found"
+ * and "manager lacks permission to query the license registry").
+ * @summary Check license
+ */
+export declare const getLicenseCheckLicenseName: (tradePlatform: string, licenseName: string, options?: RequestInit) => Promise<getLicenseCheckLicenseNameResponse>;
+export type postNotificationsSendResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type postNotificationsSendResponseSuccess = (postNotificationsSendResponse200) & {
+    headers: Headers;
+};
+export type postNotificationsSendResponse = (postNotificationsSendResponseSuccess);
+export declare const getPostNotificationsSendUrl: (tradePlatform: string) => string;
+export declare const postNotificationsSend: (tradePlatform: string, mT4NotificationsSendRequest?: MT4NotificationsSendRequest, options?: RequestInit) => Promise<postNotificationsSendResponse>;
+export type getSrvFeederLogNameResponse200 = {
+    data: StringApiResponse;
+    status: 200;
+};
+export type getSrvFeederLogNameResponseSuccess = (getSrvFeederLogNameResponse200) & {
+    headers: Headers;
+};
+export type getSrvFeederLogNameResponse = (getSrvFeederLogNameResponseSuccess);
+export declare const getGetSrvFeederLogNameUrl: (tradePlatform: string, name: string) => string;
+/**
+ * Server log for a single feeder by name (admin-only read).
+ *
+ * Manager (live) call to the wrapper's `SrvFeederLog(name)`. Returns
+ * the feeder's log buffer as a string (empty when the feeder is unknown
+ * or has no recent log activity). Payload is the raw log text — not an
+ * array of lines — to preserve formatting at the wrapper boundary.
+ * @summary Get feeder log
+ */
+export declare const getSrvFeederLogName: (tradePlatform: string, name: string, options?: RequestInit) => Promise<getSrvFeederLogNameResponse>;

package/dist/generated/mt4-v2-sidecar-batch-reads.d.ts

@@ -0,0 +1,82 @@
+/**
+ * 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 { GetTradesSnapshotParams, GetTradesSyncReadParams, GetUsersSnapshotParams, GetUsersSyncReadParams, MT4TradeListApiResponse, MT4UserListApiResponse } from './model';
+export type getUsersSnapshotResponse200 = {
+    data: MT4UserListApiResponse;
+    status: 200;
+};
+export type getUsersSnapshotResponseSuccess = (getUsersSnapshotResponse200) & {
+    headers: Headers;
+};
+export type getUsersSnapshotResponse = (getUsersSnapshotResponseSuccess);
+export declare const getGetUsersSnapshotUrl: (tradePlatform: string, params?: GetUsersSnapshotParams) => string;
+/**
+ * Atomic snapshot of all registered users on the MT4 server.
+ *
+ * Manager (live) call to the wrapper's `UsersSnapshot()`.
+ * Iterates `UnpackObject<UserRecord>(i)` over the native
+ * array — on mtmanapi64.dll the per-struct cost combined with
+ * ASLR alignment triggers access violations after some iterations,
+ * so this endpoint is sidecar-only.
+ * @summary Snapshot all users
+ */
+export declare const getUsersSnapshot: (tradePlatform: string, params?: GetUsersSnapshotParams, options?: RequestInit) => Promise<getUsersSnapshotResponse>;
+export type getUsersSyncReadResponse200 = {
+    data: MT4UserListApiResponse;
+    status: 200;
+};
+export type getUsersSyncReadResponseSuccess = (getUsersSyncReadResponse200) & {
+    headers: Headers;
+};
+export type getUsersSyncReadResponse = (getUsersSyncReadResponseSuccess);
+export declare const getGetUsersSyncReadUrl: (tradePlatform: string, params?: GetUsersSyncReadParams) => string;
+/**
+ * Read user records buffered by a prior `UsersSyncStart` call.
+ *
+ * Manager (live) call to the wrapper's `UsersSyncRead()`.
+ * Must be preceded by `POST UsersSyncStart` on the main x64
+ * API to seed the server-side snapshot. Same UnpackObject hazard
+ * as `UsersSnapshot` — sidecar-only.
+ * @summary Read user-records sync
+ */
+export declare const getUsersSyncRead: (tradePlatform: string, params?: GetUsersSyncReadParams, options?: RequestInit) => Promise<getUsersSyncReadResponse>;
+export type getTradesSnapshotResponse200 = {
+    data: MT4TradeListApiResponse;
+    status: 200;
+};
+export type getTradesSnapshotResponseSuccess = (getTradesSnapshotResponse200) & {
+    headers: Headers;
+};
+export type getTradesSnapshotResponse = (getTradesSnapshotResponseSuccess);
+export declare const getGetTradesSnapshotUrl: (tradePlatform: string, params?: GetTradesSnapshotParams) => string;
+/**
+ * Atomic snapshot of all open/pending trades on the MT4 server.
+ *
+ * Manager (live) call to the wrapper's `TradesSnapshot()`.
+ * Same UnpackObject-loop hazard as the user batch reads. Sidecar-only.
+ * @summary Snapshot all trades
+ */
+export declare const getTradesSnapshot: (tradePlatform: string, params?: GetTradesSnapshotParams, options?: RequestInit) => Promise<getTradesSnapshotResponse>;
+export type getTradesSyncReadResponse200 = {
+    data: MT4TradeListApiResponse;
+    status: 200;
+};
+export type getTradesSyncReadResponseSuccess = (getTradesSyncReadResponse200) & {
+    headers: Headers;
+};
+export type getTradesSyncReadResponse = (getTradesSyncReadResponseSuccess);
+export declare const getGetTradesSyncReadUrl: (tradePlatform: string, params?: GetTradesSyncReadParams) => string;
+/**
+ * Read trade records buffered by a prior `TradesSyncStart` call.
+ *
+ * Manager (live) call to the wrapper's `TradesSyncRead()`.
+ * Must be preceded by `POST TradesSyncStart` on the main x64
+ * API. Same UnpackObject hazard — sidecar-only.
+ * @summary Read trade-records sync
+ */
+export declare const getTradesSyncRead: (tradePlatform: string, params?: GetTradesSyncReadParams, options?: RequestInit) => Promise<getTradesSyncReadResponse>;

package/dist/generated/mt4-v2-sidecar-externalcommand.d.ts

@@ -0,0 +1,43 @@
+/**
+ * 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 { MT4ExternalCommandBinaryRequest, MT4ExternalCommandBinaryResponseApiResponse } from './model';
+export type postExternalCommandBinaryResponse200 = {
+    data: MT4ExternalCommandBinaryResponseApiResponse;
+    status: 200;
+};
+export type postExternalCommandBinaryResponseSuccess = (postExternalCommandBinaryResponse200) & {
+    headers: Headers;
+};
+export type postExternalCommandBinaryResponse = (postExternalCommandBinaryResponseSuccess);
+export declare const getPostExternalCommandBinaryUrl: (tradePlatform: string) => string;
+/**
+ * Pass arbitrary binary payload to the MT4 server's plugin pipeline.
+ *
+ * <br>
+ * Manager (live) call via the wrapper's
+ * `ExternalCommandCustom<byte[], byte[]>` overload with a
+ * pass-through byte-array marshaller. The first installed plugin
+ * that returns `RET_OK` wins; its response bytes become the
+ * payload's `Data` field.
+ * <br>
+ * Wire format: `byte[]` serializes as base64 in JSON. Clients
+ * agree with the plugin author on the binary layout.
+ * <br><b>Why sidecar-only:</b> the wrapper's binary variants rely on
+ * `Marshal.SizeOf` + native `ExternalCommand` dispatch.
+ * On `mtmanapi64.dll` the signed/unsigned marshalling
+ * diverges from `mtmanapi.dll` — same payload byte-for-byte
+ * can decode differently on x64. The x86 sidecar process loads the
+ * 32-bit DLL where the marshalling is the original one.
+ * <br>
+ * The wrapper's third `ExternalCommandCustom` overload that
+ * takes an `ICustomSerializer` interface is genuinely not
+ * REST-translatable — it requires the caller to provide C#
+ * serialization logic in-process. Not exposed.
+ * @summary Send plugin command (binary)
+ */
+export declare const postExternalCommandBinary: (tradePlatform: string, mT4ExternalCommandBinaryRequest?: MT4ExternalCommandBinaryRequest, options?: RequestInit) => Promise<postExternalCommandBinaryResponse>;

package/dist/generated/mt4-v2-sidecar-messaging.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
+ */
+import type { BooleanApiResponse, MT4MailBoxListApiResponse, MT4MailSendRequest, MT4NewsSendRequest } from './model';
+export type postNewsSendResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type postNewsSendResponseSuccess = (postNewsSendResponse200) & {
+    headers: Headers;
+};
+export type postNewsSendResponse = (postNewsSendResponseSuccess);
+export declare const getPostNewsSendUrl: (tradePlatform: string) => string;
+/**
+ * Push a news item to all connected client terminals. Requires 'Send news' admin right.
+ *
+ * Manager (live) call to the wrapper's `NewsSend(NewsTopic news)`.
+ * Sidecar-only because `mtmanapi64.dll` throws
+ * `PlatformNotSupportedException` on the body setter.
+ * @summary Send news to terminals
+ */
+export declare const postNewsSend: (tradePlatform: string, mT4NewsSendRequest?: MT4NewsSendRequest, options?: RequestInit) => Promise<postNewsSendResponse>;
+export type postMailSendResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type postMailSendResponseSuccess = (postMailSendResponse200) & {
+    headers: Headers;
+};
+export type postMailSendResponse = (postMailSendResponseSuccess);
+export declare const getPostMailSendUrl: (tradePlatform: string) => string;
+/**
+ * Send an email to one or more client logins. Requires 'Email' admin right.
+ *
+ * Manager (live) call to the wrapper's
+ * `MailSend(MailBox mail, ICollection<int> logins)`.
+ * The wrapper itself refuses to run on x64 (
+ * `throw new WrapperException("MailSend cannot be called in x64 environment")`),
+ * so this endpoint exists only in the sidecar build.
+ * @summary Send mail to accounts
+ */
+export declare const postMailSend: (tradePlatform: string, mT4MailSendRequest?: MT4MailSendRequest, options?: RequestInit) => Promise<postMailSendResponse>;
+export type getMailsRequestResponse200 = {
+    data: MT4MailBoxListApiResponse;
+    status: 200;
+};
+export type getMailsRequestResponseSuccess = (getMailsRequestResponse200) & {
+    headers: Headers;
+};
+export type getMailsRequestResponse = (getMailsRequestResponseSuccess);
+export declare const getGetMailsRequestUrl: (tradePlatform: string) => string;
+/**
+ * List all mail messages currently stored on the MT4 server.
+ *
+ * Manager (live) call to the wrapper's `MailsRequest()`.
+ * Returns the server-side mailbox store as a flat list of
+ * `MT4MailBox` entries. Read-only; no batching parameters
+ * (the wrapper has no native pagination).
+ * @summary List server mail
+ */
+export declare const getMailsRequest: (tradePlatform: string, options?: RequestInit) => Promise<getMailsRequestResponse>;

package/dist/generated/mt4-v2-sidecar-plugins.d.ts

@@ -0,0 +1,100 @@
+/**
+ * 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 { BooleanApiResponse, MT4PluginListApiResponse, MT4PluginParam, MT4PluginParamApiResponse, MT4PluginParamListApiResponse } from './model';
+export type getPluginsGetResponse200 = {
+    data: MT4PluginListApiResponse;
+    status: 200;
+};
+export type getPluginsGetResponseSuccess = (getPluginsGetResponse200) & {
+    headers: Headers;
+};
+export type getPluginsGetResponse = (getPluginsGetResponseSuccess);
+export declare const getGetPluginsGetUrl: (tradePlatform: string) => string;
+/**
+ * List MT4 server plugins currently configured (pump-side cache).
+ *
+ * Manager-pump call to the wrapper's `PluginsGet()`. The
+ * wrapper marks this `[Obsolete]` on x64 (mtmanapi64.dll has
+ * silently-changing plugin layouts); the x86 sidecar process loads
+ * mtmanapi.dll where the layout is stable, so the call is safe.
+ * @summary List plugins (cached)
+ */
+export declare const getPluginsGet: (tradePlatform: string, options?: RequestInit) => Promise<getPluginsGetResponse>;
+export type getPluginParamGetPosResponse200 = {
+    data: MT4PluginParamApiResponse;
+    status: 200;
+};
+export type getPluginParamGetPosResponseSuccess = (getPluginParamGetPosResponse200) & {
+    headers: Headers;
+};
+export type getPluginParamGetPosResponse = (getPluginParamGetPosResponseSuccess);
+export declare const getGetPluginParamGetPosUrl: (tradePlatform: string, pos: number) => string;
+/**
+ * Get a single plugin's parameters by position in the `PluginsGet` list.
+ *
+ * Manager-pump call to the wrapper's `PluginParamGet(pos, out ConPluginParam)`.
+ * The `ConPluginParam.Params` auto-dereferences a 32-bit pointer —
+ * safe on x86, sign-extension hazard on x64. Sidecar-only.
+ * @summary Get plugin parameters
+ */
+export declare const getPluginParamGetPos: (tradePlatform: string, pos: number, options?: RequestInit) => Promise<getPluginParamGetPosResponse>;
+export type postPluginUpdateResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type postPluginUpdateResponseSuccess = (postPluginUpdateResponse200) & {
+    headers: Headers;
+};
+export type postPluginUpdateResponse = (postPluginUpdateResponseSuccess);
+export declare const getPostPluginUpdateUrl: (tradePlatform: string) => string;
+/**
+ * Apply a plugin parameter update via the pump-side wrapper. Requires admin rights.
+ *
+ * Manager-live call to the wrapper's `PluginUpdate(ConPluginParam cpp)`.
+ * Body is `MT4PluginParam` (the same shape `PluginParamGet` returns).
+ * @summary Update plugin parameter
+ */
+export declare const postPluginUpdate: (tradePlatform: string, mT4PluginParam?: MT4PluginParam, options?: RequestInit) => Promise<postPluginUpdateResponse>;
+export type getCfgRequestPluginResponse200 = {
+    data: MT4PluginParamListApiResponse;
+    status: 200;
+};
+export type getCfgRequestPluginResponseSuccess = (getCfgRequestPluginResponse200) & {
+    headers: Headers;
+};
+export type getCfgRequestPluginResponse = (getCfgRequestPluginResponseSuccess);
+export declare const getGetCfgRequestPluginUrl: (tradePlatform: string) => string;
+/**
+ * Read the plugin configuration (Manager-live).
+ *
+ * Manager (live) call to the wrapper's `CfgRequestPlugin()`.
+ * Returns the full plugin set with their parameter arrays — the
+ * Manager-side equivalent of `PluginsGet` + per-plugin
+ * `PluginParamGet` in one round-trip.
+ * @summary Get plugin config (live)
+ */
+export declare const getCfgRequestPlugin: (tradePlatform: string, options?: RequestInit) => Promise<getCfgRequestPluginResponse>;
+export type postCfgUpdatePluginResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type postCfgUpdatePluginResponseSuccess = (postCfgUpdatePluginResponse200) & {
+    headers: Headers;
+};
+export type postCfgUpdatePluginResponse = (postCfgUpdatePluginResponseSuccess);
+export declare const getPostCfgUpdatePluginUrl: (tradePlatform: string) => string;
+/**
+ * Update plugin configuration (Manager-live).
+ *
+ * Manager (live) call to the wrapper's
+ * `CfgUpdatePlugin(ConPlugin cp, PluginCfg[] cfgs)`. Body is
+ * `MT4PluginParam` — the plugin metadata plus its parameter
+ * array. Returns a bare-bool envelope.
+ * @summary Update plugin config
+ */
+export declare const postCfgUpdatePlugin: (tradePlatform: string, mT4PluginParam?: MT4PluginParam, options?: RequestInit) => Promise<postCfgUpdatePluginResponse>;