@mywebapi.com/sdk 0.1.0

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

@@ -0,0 +1,319 @@
+/**
+ * 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, GetAdmBalanceCheckParams, GetUserRecordsRequestParams, GetUsersRequestParams, MT4BalanceDiffApiResponse, MT4BalanceDiffListApiResponse, MT4UserApiResponse, MT4UserCreate, MT4UserListApiResponse, MT4UserUpdate, MT4UsersGroupOp, PostAdmBalanceFixParams, PostUsersSyncStartParams } from './model';
+export type getUserRecordGetLoginResponse200 = {
+    data: MT4UserApiResponse;
+    status: 200;
+};
+export type getUserRecordGetLoginResponseSuccess = (getUserRecordGetLoginResponse200) & {
+    headers: Headers;
+};
+export type getUserRecordGetLoginResponse = (getUserRecordGetLoginResponseSuccess);
+export declare const getGetUserRecordGetLoginUrl: (tradePlatform: string, login: number) => string;
+/**
+ * Account record for a single login from the pump cache.
+ *
+ * Pump-cached read of the wrapper's `UserRecord`, mapped to the v2
+ * `MT4User` DTO. Secrets (passwords, OTP secret, API blob) are
+ * stripped at the mapper level — they cannot be exposed via this endpoint
+ * regardless of caller permissions. Returns NotFound envelope when the
+ * pump cache does not contain the requested login.
+ * @summary Get account (cached)
+ */
+export declare const getUserRecordGetLogin: (tradePlatform: string, login: number, options?: RequestInit) => Promise<getUserRecordGetLoginResponse>;
+export type getUserRecordRequestLoginResponse200 = {
+    data: MT4UserApiResponse;
+    status: 200;
+};
+export type getUserRecordRequestLoginResponseSuccess = (getUserRecordRequestLoginResponse200) & {
+    headers: Headers;
+};
+export type getUserRecordRequestLoginResponse = (getUserRecordRequestLoginResponseSuccess);
+export declare const getGetUserRecordRequestLoginUrl: (tradePlatform: string, login: number) => string;
+/**
+ * Account record for a single login — live round-trip to MT4 server.
+ *
+ * Manager variant — bypasses the pump cache and asks the MT4 server
+ * directly via `UserRecordsRequest` with a single-login array.
+ * Slower than `UserRecordGet` but guarantees fresh data (just
+ * changed group, balance fix, etc). Same curated DTO, same security
+ * guarantees — passwords/OTP/API blob never cross the boundary.
+ * @summary Get account (live)
+ */
+export declare const getUserRecordRequestLogin: (tradePlatform: string, login: number, options?: RequestInit) => Promise<getUserRecordRequestLoginResponse>;
+export type getUserRecordsRequestResponse200 = {
+    data: MT4UserListApiResponse;
+    status: 200;
+};
+export type getUserRecordsRequestResponseSuccess = (getUserRecordsRequestResponse200) & {
+    headers: Headers;
+};
+export type getUserRecordsRequestResponse = (getUserRecordsRequestResponseSuccess);
+export declare const getGetUserRecordsRequestUrl: (tradePlatform: string, params?: GetUserRecordsRequestParams) => string;
+/**
+ * Account records for a list of logins — live round-trip to MT4 server.
+ *
+ * Manager batch variant. Pass logins as repeated query parameters:
+ * `?logins=1001&logins=1002&logins=1003`. Server-side billing
+ * counts this as one Manager request regardless of the array length —
+ * prefer batch over a loop of single-login calls.
+ *
+ * Order in the response is **not** guaranteed to match the request — the
+ * wrapper returns a dictionary. Missing logins are silently omitted; the
+ * envelope is not an error envelope in that case.
+ * @summary Get accounts batch (live)
+ */
+export declare const getUserRecordsRequest: (tradePlatform: string, params?: GetUserRecordsRequestParams, options?: RequestInit) => Promise<getUserRecordsRequestResponse>;
+export type getAdmBalanceCheckLoginResponse200 = {
+    data: MT4BalanceDiffApiResponse;
+    status: 200;
+};
+export type getAdmBalanceCheckLoginResponseSuccess = (getAdmBalanceCheckLoginResponse200) & {
+    headers: Headers;
+};
+export type getAdmBalanceCheckLoginResponse = (getAdmBalanceCheckLoginResponseSuccess);
+export declare const getGetAdmBalanceCheckLoginUrl: (tradePlatform: string, login: number) => string;
+/**
+ * Admin balance integrity check for a single account.
+ *
+ * Manager (live) call. Returns the difference between the recorded
+ * account balance and what the MT4 server recomputes from closed
+ * orders + balance operations. `diff = 0` → balance is intact;
+ * non-zero → admin tooling can run `AdmBalanceFix` to recompute
+ * (forthcoming Wave 3 endpoint).
+ *
+ * Read-only operation despite the wrapper's "Adm" prefix (the prefix
+ * signals the elevated authorization requirement, not a write side
+ * effect).
+ * @summary Check account balance
+ */
+export declare const getAdmBalanceCheckLogin: (tradePlatform: string, login: number, options?: RequestInit) => Promise<getAdmBalanceCheckLoginResponse>;
+export type getAdmBalanceCheckResponse200 = {
+    data: MT4BalanceDiffListApiResponse;
+    status: 200;
+};
+export type getAdmBalanceCheckResponseSuccess = (getAdmBalanceCheckResponse200) & {
+    headers: Headers;
+};
+export type getAdmBalanceCheckResponse = (getAdmBalanceCheckResponseSuccess);
+export declare const getGetAdmBalanceCheckUrl: (tradePlatform: string, params?: GetAdmBalanceCheckParams) => string;
+/**
+ * Admin balance integrity check for a batch of accounts.
+ *
+ * Same semantics as the single-login variant but takes a list of logins
+ * via repeated query parameters: `?logins=1001&logins=1002`.
+ * One billed Manager request regardless of the array length. The response
+ * list contains entries only for accounts the server flagged with a
+ * non-zero diff — clean accounts are silently omitted. Clients should
+ * treat "missing from response" as "diff = 0".
+ * @summary Check account balances (batch)
+ */
+export declare const getAdmBalanceCheck: (tradePlatform: string, params?: GetAdmBalanceCheckParams, options?: RequestInit) => Promise<getAdmBalanceCheckResponse>;
+export type postAdmBalanceFixResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type postAdmBalanceFixResponseSuccess = (postAdmBalanceFixResponse200) & {
+    headers: Headers;
+};
+export type postAdmBalanceFixResponse = (postAdmBalanceFixResponseSuccess);
+export declare const getPostAdmBalanceFixUrl: (tradePlatform: string, params?: PostAdmBalanceFixParams) => string;
+/**
+ * Admin balance fix — recompute balances for the given logins.
+ *
+ * POST mutator. Asks MT4 server to take the diffs reported by
+ * `AdmBalanceCheck` and write them onto the accounts. Empty body —
+ * the logins are submitted as repeated query parameters
+ * (`?logins=1001&logins=1002`) to keep the URL shape parallel
+ * with the read variant and avoid the awkward "POST with int[] body"
+ * pattern.
+ *
+ * This DOES modify account balances. Pair every retry with an
+ * `Idempotency-Key` header; otherwise a retried fix can double-
+ * apply on an account whose original fix happened to land but whose
+ * response was lost on the wire.
+ * @summary Fix account balances
+ */
+export declare const postAdmBalanceFix: (tradePlatform: string, params?: PostAdmBalanceFixParams, options?: RequestInit) => Promise<postAdmBalanceFixResponse>;
+export type getUsersRequestResponse200 = {
+    data: MT4UserListApiResponse;
+    status: 200;
+};
+export type getUsersRequestResponseSuccess = (getUsersRequestResponse200) & {
+    headers: Headers;
+};
+export type getUsersRequestResponse = (getUsersRequestResponseSuccess);
+export declare const getGetUsersRequestUrl: (tradePlatform: string, params?: GetUsersRequestParams) => string;
+/**
+ * Manager (live) call returning a paged list of every account on the platform. When `?limit=` is omitted the response contains all users in one page (back-compat). Set `?limit=N` to bound page size; the response's `paging.nextCursor` drives the next call.
+ *
+ * Wrapper-side this still fetches the full users dictionary — paging
+ * reduces only the wire payload, not MT4 server load. Items are sorted
+ * by login ascending; pages are stable across concurrent inserts as
+ * long as the new login is greater than the previous page's last login.
+ * @summary List accounts (live)
+ */
+export declare const getUsersRequest: (tradePlatform: string, params?: GetUsersRequestParams, options?: RequestInit) => Promise<getUsersRequestResponse>;
+export type postUserRecordNewResponse200 = {
+    data: MT4UserApiResponse;
+    status: 200;
+};
+export type postUserRecordNewResponseSuccess = (postUserRecordNewResponse200) & {
+    headers: Headers;
+};
+export type postUserRecordNewResponse = (postUserRecordNewResponseSuccess);
+export declare const getPostUserRecordNewUrl: (tradePlatform: string) => string;
+/**
+ * Create a new account — Type 1 mutator.
+ *
+ * POST mutator. Pass the full `MT4UserCreate` DTO. Set
+ * `Login = 0` to let MT4 server assign the next free id, or
+ * request a specific id by setting `Login > 0` (the server
+ * rejects collisions with an MT4 error envelope).
+ *
+ * The wrapper accepts the account with empty password bytes; clients
+ * MUST follow up with `POST UserPasswordSet/{login}` before the
+ * account is usable.
+ *
+ * Idempotency-Key strongly recommended — a retried create without it
+ * can land twice when the original response was lost on the wire,
+ * burning a second login id from the broker's sequence.
+ * @summary Create account
+ */
+export declare const postUserRecordNew: (tradePlatform: string, mT4UserCreate?: MT4UserCreate, options?: RequestInit) => Promise<postUserRecordNewResponse>;
+export type postUserRecordUpdateLoginResponse200 = {
+    data: MT4UserApiResponse;
+    status: 200;
+};
+export type postUserRecordUpdateLoginResponseSuccess = (postUserRecordUpdateLoginResponse200) & {
+    headers: Headers;
+};
+export type postUserRecordUpdateLoginResponse = (postUserRecordUpdateLoginResponseSuccess);
+export declare const getPostUserRecordUpdateLoginUrl: (tradePlatform: string, login: number) => string;
+/**
+ * Update an account record — Type 1 mutator with secret-preservation read.
+ *
+ * <br>
+ * Surface-level Type 1 semantics: client submits the full `MT4UserUpdate`
+ * DTO and the server writes it back. Implementation requires an extra
+ * read step because the wrapper `UserRecord` struct contains
+ * secret/computed/read-only fields the v2 input DTO deliberately omits
+ * (Password, OTPSecret, LastDate, etc.). Without the read step those
+ * would be zeroed out by the write.
+ * <br>
+ * Flow:
+ * <list type="number"><item>Fetch the existing record via `UserRecordsRequest` (live, not pump cache).</item><item>Apply the DTO over the in-memory record using `ApplyTo`. Secrets and read-only fields are `[MapperIgnoreTarget]`'d so they survive.</item><item>Write the modified record back via `UserRecordUpdate`.</item></list><br><b>This is NOT Type 2.</b> Type 2 mutators (single-field) are deferred
+ * to a later release and will accept just the field name + value, doing
+ * the read-modify-write entirely server-side. Both flows happen to use
+ * the same read-modify-write structure on the implementation side — the
+ * difference is what the client submits.
+ * <br>
+ * Idempotency-Key is strongly recommended; without it a retried update
+ * risks silently overwriting concurrent edits that happened between
+ * the original send and the retry.
+ * @summary Update account
+ */
+export declare const postUserRecordUpdateLogin: (tradePlatform: string, login: number, mT4UserUpdate?: MT4UserUpdate, options?: RequestInit) => Promise<postUserRecordUpdateLoginResponse>;
+export type patchUserRecordLoginMT4Response200 = {
+    data: MT4UserApiResponse;
+    status: 200;
+};
+export type patchUserRecordLoginMT4ResponseSuccess = (patchUserRecordLoginMT4Response200) & {
+    headers: Headers;
+};
+export type patchUserRecordLoginMT4Response = (patchUserRecordLoginMT4ResponseSuccess);
+export declare const getPatchUserRecordLoginMT4Url: (tradePlatform: string, login: number) => string;
+/**
+ * Type 2 mutator — partial update of a user record. Client sends a JSON object containing only the fields to change; the server reads the current record live from MT4 (Manager, not pump), overlays the patch, and writes back. Echoes the merged record.
+ *
+ * Unknown keys in the patch body are silently ignored (forwards-compat).
+ * Field-level validation is delegated to MT4 server — invalid values
+ * surface as `MT4Error` envelopes. Secret-preservation and
+ * computed-field protection are handled by the existing Type 1 ApplyTo
+ * mapper's ignore list.
+ * @summary Patch account
+ */
+export declare const patchUserRecordLoginMT4: (tradePlatform: string, login: number, options?: RequestInit) => Promise<patchUserRecordLoginMT4Response>;
+export type getAdmUsersRequestSafeGroupResponse200 = {
+    data: MT4UserListApiResponse;
+    status: 200;
+};
+export type getAdmUsersRequestSafeGroupResponseSuccess = (getAdmUsersRequestSafeGroupResponse200) & {
+    headers: Headers;
+};
+export type getAdmUsersRequestSafeGroupResponse = (getAdmUsersRequestSafeGroupResponseSuccess);
+export declare const getGetAdmUsersRequestSafeGroupUrl: (tradePlatform: string, group: string) => string;
+/**
+ * All user accounts in a given group (admin scope) — the safe variant that honors permission checks server-side.
+ *
+ * Manager (live) call. Returns the curated `MT4User` projection
+ * for every account in the specified group. The wrapper's "Safe" suffix
+ * indicates it runs through `RunSafe` with the `Admin` rights
+ * guard — a manager lacking that permission receives a sensible error
+ * rather than a connection drop.
+ *
+ * Comma-separated group lists are accepted by the wrapper (it strips
+ * commas and trims whitespace internally); the simplest call pattern
+ * is a single group name. Large groups may return substantial
+ * payloads — pair with `Idempotency-Key` on retry.
+ * @summary List group accounts (admin)
+ */
+export declare const getAdmUsersRequestSafeGroup: (tradePlatform: string, group: string, options?: RequestInit) => Promise<getAdmUsersRequestSafeGroupResponse>;
+export type postUsersSyncStartResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type postUsersSyncStartResponseSuccess = (postUsersSyncStartResponse200) & {
+    headers: Headers;
+};
+export type postUsersSyncStartResponse = (postUsersSyncStartResponseSuccess);
+export declare const getPostUsersSyncStartUrl: (tradePlatform: string, params?: PostUsersSyncStartParams) => string;
+/**
+ * Opens a server-side incremental sync session for user records modified at or after timestamp.
+ *
+ * Manager-live POST (modifies server-side session state). The wrapper
+ * supports a follow-up `UsersSyncRead` call that drains the
+ * snapshot, but the read-side endpoint is currently deferred under
+ * wine x64 (see deferral note above this method). Pass
+ * `timestamp=0` to request all user records.
+ *
+ * `timestamp` is Unix epoch seconds (int32) in MT4 server-local
+ * time, not UTC. Returns a bare success envelope.
+ * @summary Start user-records sync
+ */
+export declare const postUsersSyncStart: (tradePlatform: string, params?: PostUsersSyncStartParams, options?: RequestInit) => Promise<postUsersSyncStartResponse>;
+export type postUsersGroupOpResponse200 = {
+    data: BooleanApiResponse;
+    status: 200;
+};
+export type postUsersGroupOpResponseSuccess = (postUsersGroupOpResponse200) & {
+    headers: Headers;
+};
+export type postUsersGroupOpResponse = (postUsersGroupOpResponseSuccess);
+export declare const getPostUsersGroupOpUrl: (tradePlatform: string) => string;
+/**
+ * Bulk operation on a list of account logins — change group, leverage, enable/disable, or delete in a single Manager round-trip.
+ *
+ * Manager (live) call. Wraps `UsersGroupOp(GroupCommandInfo, ICollection<int>)`.
+ * The body specifies the command and its parameter (NewGroup for
+ * SetGroup, Leverage for Leverage; both ignored for Delete/Enable/
+ * Disable) plus the list of target logins. The wrapper auto-fills
+ * the internal `Len` field from the logins array — clients do
+ * not set it.
+ *
+ * Wine x64 safe: the wrapper uses `AllocArraySafe` on the int
+ * login array (single contiguous pack, no UnpackObject loop) and
+ * `AllocSafe` on the GroupCommandInfo struct.
+ *
+ * Requires Manager or Administrator access rights on the manager
+ * account; the wrapper enforces this server-side. Idempotency-Key
+ * strongly recommended — bulk Delete / SetGroup operations are
+ * destructive on customer-visible state.
+ * @summary Bulk account operation
+ */
+export declare const postUsersGroupOp: (tradePlatform: string, mT4UsersGroupOp?: MT4UsersGroupOp, options?: RequestInit) => Promise<postUsersGroupOpResponse>;

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

@@ -0,0 +1,34 @@
+/**
+ * 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 { DateTimeApiResponse, MT5TimeApiResponse } from './model';
+export type getServerTimeMT5Response200 = {
+    data: DateTimeApiResponse;
+    status: 200;
+};
+export type getServerTimeMT5ResponseSuccess = (getServerTimeMT5Response200) & {
+    headers: Headers;
+};
+export type getServerTimeMT5Response = (getServerTimeMT5ResponseSuccess);
+export declare const getGetServerTimeMT5Url: (tradePlatform: string) => string;
+/**
+ * @summary Get server time
+ */
+export declare const getServerTimeMT5: (tradePlatform: string, options?: RequestInit) => Promise<getServerTimeMT5Response>;
+export type getTimeGetResponse200 = {
+    data: MT5TimeApiResponse;
+    status: 200;
+};
+export type getTimeGetResponseSuccess = (getTimeGetResponse200) & {
+    headers: Headers;
+};
+export type getTimeGetResponse = (getTimeGetResponseSuccess);
+export declare const getGetTimeGetUrl: (tradePlatform: string) => string;
+/**
+ * @summary Get server time configuration
+ */
+export declare const getTimeGet: (tradePlatform: string, options?: RequestInit) => Promise<getTimeGetResponse>;

package/dist/generated/mt5-v2-groups.d.ts

@@ -0,0 +1,36 @@
+/**
+ * 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 { MT5ConGroupApiResponse } from './model';
+export type getGroupGetGroupResponse200 = {
+    data: MT5ConGroupApiResponse;
+    status: 200;
+};
+export type getGroupGetGroupResponseSuccess = (getGroupGetGroupResponse200) & {
+    headers: Headers;
+};
+export type getGroupGetGroupResponse = (getGroupGetGroupResponseSuccess);
+export declare const getGetGroupGetGroupUrl: (tradePlatform: string, group: string) => string;
+/**
+ * @summary Get a group by name
+ */
+export declare const getGroupGetGroup: (tradePlatform: string, group: string, options?: RequestInit) => Promise<getGroupGetGroupResponse>;
+export type patchGroupRecordGroupMT5Response200 = {
+    data: MT5ConGroupApiResponse;
+    status: 200;
+};
+export type patchGroupRecordGroupMT5ResponseSuccess = (patchGroupRecordGroupMT5Response200) & {
+    headers: Headers;
+};
+export type patchGroupRecordGroupMT5Response = (patchGroupRecordGroupMT5ResponseSuccess);
+export declare const getPatchGroupRecordGroupMT5Url: (tradePlatform: string, group: string) => string;
+/**
+ * Send only the fields you want to change (JSON Merge Patch, RFC 7386);
+ * omitted fields keep their current values. Returns the updated record.
+ * @summary Partially update a group
+ */
+export declare const patchGroupRecordGroupMT5: (tradePlatform: string, group: string, options?: RequestInit) => Promise<patchGroupRecordGroupMT5Response>;

package/dist/generated/mt5-v2-managers.d.ts

@@ -0,0 +1,21 @@
+/**
+ * Generated by orval v8.19.0 🍺
+ * Do not edit manually.
+ * JSON-Pure WebAPI for MT4/MT5
+ * It uses native MetaQuote ManagerAPI for both MT4 and MT5 connection. Plus, it keep pumping connection active, so all *Get calls will run much faster, than *Request.<br/>Here partially used the idea of JSON-Pure API, only HTTP code 200 is acceptable. Other codes signal about errors on server side, which are out of control of client, like wrong parameters, platform unavailability, etc.
+ * OpenAPI spec version: 2.0
+ */
+import type { MT5ConManagerApiResponse } from './model';
+export type getManagerCurrentResponse200 = {
+    data: MT5ConManagerApiResponse;
+    status: 200;
+};
+export type getManagerCurrentResponseSuccess = (getManagerCurrentResponse200) & {
+    headers: Headers;
+};
+export type getManagerCurrentResponse = (getManagerCurrentResponseSuccess);
+export declare const getGetManagerCurrentUrl: (tradePlatform: string) => string;
+/**
+ * @summary Get the current session manager
+ */
+export declare const getManagerCurrent: (tradePlatform: string, options?: RequestInit) => Promise<getManagerCurrentResponse>;

package/dist/generated/mt5-v2-symbols.d.ts

@@ -0,0 +1,36 @@
+/**
+ * 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 { MT5SymbolApiResponse } from './model';
+export type getSymbolGetSymbolResponse200 = {
+    data: MT5SymbolApiResponse;
+    status: 200;
+};
+export type getSymbolGetSymbolResponseSuccess = (getSymbolGetSymbolResponse200) & {
+    headers: Headers;
+};
+export type getSymbolGetSymbolResponse = (getSymbolGetSymbolResponseSuccess);
+export declare const getGetSymbolGetSymbolUrl: (tradePlatform: string, symbol: string) => string;
+/**
+ * @summary Get a symbol by name
+ */
+export declare const getSymbolGetSymbol: (tradePlatform: string, symbol: string, options?: RequestInit) => Promise<getSymbolGetSymbolResponse>;
+export type patchSymbolRecordSymbolResponse200 = {
+    data: MT5SymbolApiResponse;
+    status: 200;
+};
+export type patchSymbolRecordSymbolResponseSuccess = (patchSymbolRecordSymbolResponse200) & {
+    headers: Headers;
+};
+export type patchSymbolRecordSymbolResponse = (patchSymbolRecordSymbolResponseSuccess);
+export declare const getPatchSymbolRecordSymbolUrl: (tradePlatform: string, symbol: string) => string;
+/**
+ * Send only the fields you want to change (JSON Merge Patch, RFC 7386);
+ * omitted fields keep their current values. Returns the updated record.
+ * @summary Partially update a symbol
+ */
+export declare const patchSymbolRecordSymbol: (tradePlatform: string, symbol: string, options?: RequestInit) => Promise<patchSymbolRecordSymbolResponse>;

package/dist/generated/mt5-v2-trades.d.ts

@@ -0,0 +1,53 @@
+/**
+ * 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 { GetDealByGroupMaskParams, GetOrderByGroupMaskParams, GetPositionByGroupMaskParams, MT5DealListApiResponse, MT5OrderListApiResponse, MT5PositionListApiResponse } from './model';
+export type getPositionByGroupMaskResponse200 = {
+    data: MT5PositionListApiResponse;
+    status: 200;
+};
+export type getPositionByGroupMaskResponseSuccess = (getPositionByGroupMaskResponse200) & {
+    headers: Headers;
+};
+export type getPositionByGroupMaskResponse = (getPositionByGroupMaskResponseSuccess);
+export declare const getGetPositionByGroupMaskUrl: (tradePlatform: string, mask: string, params?: GetPositionByGroupMaskParams) => string;
+/**
+ * Returns open positions for all logins in groups matching the mask,
+ * ordered by Position ID ascending. Use the cursor for the next page.
+ * @summary List positions by group
+ */
+export declare const getPositionByGroupMask: (tradePlatform: string, mask: string, params?: GetPositionByGroupMaskParams, options?: RequestInit) => Promise<getPositionByGroupMaskResponse>;
+export type getOrderByGroupMaskResponse200 = {
+    data: MT5OrderListApiResponse;
+    status: 200;
+};
+export type getOrderByGroupMaskResponseSuccess = (getOrderByGroupMaskResponse200) & {
+    headers: Headers;
+};
+export type getOrderByGroupMaskResponse = (getOrderByGroupMaskResponseSuccess);
+export declare const getGetOrderByGroupMaskUrl: (tradePlatform: string, mask: string, params?: GetOrderByGroupMaskParams) => string;
+/**
+ * Returns active and pending orders for all logins in groups matching the mask,
+ * ordered by Order ID ascending. Use the cursor for the next page.
+ * @summary List orders by group
+ */
+export declare const getOrderByGroupMask: (tradePlatform: string, mask: string, params?: GetOrderByGroupMaskParams, options?: RequestInit) => Promise<getOrderByGroupMaskResponse>;
+export type getDealByGroupMaskResponse200 = {
+    data: MT5DealListApiResponse;
+    status: 200;
+};
+export type getDealByGroupMaskResponseSuccess = (getDealByGroupMaskResponse200) & {
+    headers: Headers;
+};
+export type getDealByGroupMaskResponse = (getDealByGroupMaskResponseSuccess);
+export declare const getGetDealByGroupMaskUrl: (tradePlatform: string, mask: string, params?: GetDealByGroupMaskParams) => string;
+/**
+ * Returns deals for all logins in groups matching the mask, ordered by Deal ID ascending.
+ * Returns the full history by default. Use the cursor for the next page.
+ * @summary List deals by group
+ */
+export declare const getDealByGroupMask: (tradePlatform: string, mask: string, params?: GetDealByGroupMaskParams, options?: RequestInit) => Promise<getDealByGroupMaskResponse>;

package/dist/generated/mt5-v2-users.d.ts

@@ -0,0 +1,36 @@
+/**
+ * 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 { MT5UserApiResponse } from './model';
+export type getUserGetLoginResponse200 = {
+    data: MT5UserApiResponse;
+    status: 200;
+};
+export type getUserGetLoginResponseSuccess = (getUserGetLoginResponse200) & {
+    headers: Headers;
+};
+export type getUserGetLoginResponse = (getUserGetLoginResponseSuccess);
+export declare const getGetUserGetLoginUrl: (tradePlatform: string, login: number) => string;
+/**
+ * @summary Get a user by login
+ */
+export declare const getUserGetLogin: (tradePlatform: string, login: number, options?: RequestInit) => Promise<getUserGetLoginResponse>;
+export type patchUserRecordLoginMT5Response200 = {
+    data: MT5UserApiResponse;
+    status: 200;
+};
+export type patchUserRecordLoginMT5ResponseSuccess = (patchUserRecordLoginMT5Response200) & {
+    headers: Headers;
+};
+export type patchUserRecordLoginMT5Response = (patchUserRecordLoginMT5ResponseSuccess);
+export declare const getPatchUserRecordLoginMT5Url: (tradePlatform: string, login: number) => string;
+/**
+ * Send only the fields you want to change (JSON Merge Patch, RFC 7386);
+ * omitted fields keep their current values. Returns the updated record.
+ * @summary Partially update a user
+ */
+export declare const patchUserRecordLoginMT5: (tradePlatform: string, login: number, options?: RequestInit) => Promise<patchUserRecordLoginMT5Response>;

package/dist/index.d.ts

@@ -0,0 +1,12 @@
+export { CPluginWebApiClient } from './client';
+export type { CPluginWebApiClientOptions, CPluginWebApiClientInit, TradePlatform } from './client';
+export { resolveEnvironment } from './environments';
+export type { EnvironmentName, ResolvedEnvironment, EnvironmentSelector } from './environments';
+export { ApiError } from './errors';
+export type { WebApiErrorCode, PagingMeta, ApiMeta, ApiErrorBody, ApiEnvelope, } from './errors';
+export { paginate, collectAll } from './pagination';
+export type { PagedResult } from './pagination';
+export { StaticTokenProvider, ClientCredentialsTokenProvider, OAuth2TokenError, type TokenProvider, type ClientCredentialsOptions, } from './auth';
+export { defaultPolicy, type RetryPolicy } from './retry';
+export { MT4V2SignalRClient, MT4V2SignalRError, type MT4V2SignalRClientOptions, type SignalRClientExtras, type ConnectionStatusPayload, type TickPayload, type MarginCallPayload, type TradeUpdatePayload, type UserUpdatePayload, type SymbolUpdatePayload, } from './signalr';
+export { MT5V2SignalRClient, type MT5V2SignalRClientOptions, type MT5ConnectionStatusPayload, type MT5MarginCallPayload, } from './signalr.mt5';