Binance Connector JS
    Preparing search index...

    Class RestAPI

    Index

    Constructors

    constructor

    Methods

    addIpRestrictionForSubAccountApiKey createAVirtualSubAccount deleteIpListForASubAccountApiKey depositAssetsIntoTheManagedSubAccount enableFuturesForSubAccount enableOptionsForSubAccount futuresTransferForSubAccount getDetailOnSubAccountsFuturesAccount getDetailOnSubAccountsFuturesAccountV2 getDetailOnSubAccountsMarginAccount getFuturesPositionRiskOfSubAccount getFuturesPositionRiskOfSubAccountV2 getIpRestrictionForASubAccountApiKey getManagedSubAccountDepositAddress getMovePositionHistoryForSubAccount getSubAccountDepositAddress getSubAccountDepositHistory getSubAccountsStatusOnMarginOrFutures getSummaryOfSubAccountsFuturesAccount getSummaryOfSubAccountsFuturesAccountV2 getSummaryOfSubAccountsMarginAccount marginTransferForSubAccount movePositionForSubAccount queryManagedSubAccountAssetDetails queryManagedSubAccountFuturesAssetDetails queryManagedSubAccountList queryManagedSubAccountMarginAssetDetails queryManagedSubAccountSnapshot queryManagedSubAccountTransferLogMasterAccountInvestor queryManagedSubAccountTransferLogMasterAccountTrading queryManagedSubAccountTransferLogSubAccountTrading querySubAccountAssets querySubAccountAssetsAssetManagement querySubAccountFuturesAssetTransferHistory querySubAccountList querySubAccountSpotAssetsSummary querySubAccountSpotAssetTransferHistory querySubAccountTransactionStatistics queryUniversalTransferHistory sendRequest sendSignedRequest subAccountFuturesAssetTransfer subAccountTransferHistory transferToMaster transferToSubAccountOfSameMaster universalTransfer withdrawlAssetsFromTheManagedSubAccount

    Constructors

    Methods

    • Move position between sub-master, master-sub, or sub-sub accounts when necessary

      You need to Enable Trading permission for the API Key which requests this endpoint. This function only support VIP level 7-9. Only master account can use the function Quantity should be positive number only The function support normal account, PM PRO and PM PRO SPAN. Only support for from account has positions For all orders in the same orderArgs request, if any symbol’s total close position quantity is bigger than the symbol’s current position quantity, all batch orders in the same list will fail simultaneously. Only support cross margin mode The price for move position is MarkPrice only. Not support for MSA. Not support for the symbol under Reduce-Only.

      Weight: 150

      Parameters

      Returns Promise<RestApiResponse<MovePositionForSubAccountResponse>>

      Binance API Documentation

    • Generic function to send a request.

      Type Parameters

      • T

      Parameters

      • endpoint: string

        The API endpoint to call.

      • method: "GET" | "POST" | "DELETE" | "PUT" | "PATCH"

        HTTP method to use (GET, POST, DELETE, etc.).

      • params: Record<string, unknown> = {}

        Query parameters for the request.

      Returns Promise<RestApiResponse<T>>

      A promise resolving to the response data object.

    • Generic function to send a signed request.

      Type Parameters

      • T

      Parameters

      • endpoint: string

        The API endpoint to call.

      • method: "GET" | "POST" | "DELETE" | "PUT" | "PATCH"

        HTTP method to use (GET, POST, DELETE, etc.).

      • params: Record<string, unknown> = {}

        Query parameters for the request.

      Returns Promise<RestApiResponse<T>>

      A promise resolving to the response data object.

    • Universal Transfer

      You need to enable "internal transfer" option for the api key which requests this endpoint. Transfer from master account by default if fromEmail is not sent. Transfer to master account by default if toEmail is not sent. At least either fromEmail or toEmail need to be sent when the fromAccountType and the toAccountType are the same. Supported transfer scenarios: SPOT transfer to SPOT, USDT_FUTURE, COIN_FUTURE (regardless of master or sub) SPOT, USDT_FUTURE, COIN_FUTURE transfer to SPOT (regardless of master or sub) Master account SPOT transfer to sub-account MARGIN(Cross), ISOLATED_MARGIN Sub-account MARGIN(Cross), ISOLATED_MARGIN transfer to master account SPOT Sub-account MARGIN(Cross) transfer to Sub-account MARGIN(Cross) ALPHA to ALPHA (regardless of master or sub)

      Weight: 360

      Parameters

      Returns Promise<RestApiResponse<UniversalTransferResponse>>

      Binance API Documentation

    Settings

    Member Visibility

    On This Page

    Constructors
    Methods
    addIpRestrictionForSubAccountApiKeycreateAVirtualSubAccountdeleteIpListForASubAccountApiKeydepositAssetsIntoTheManagedSubAccountenableFuturesForSubAccountenableOptionsForSubAccountfuturesTransferForSubAccountgetDetailOnSubAccountsFuturesAccountgetDetailOnSubAccountsFuturesAccountV2getDetailOnSubAccountsMarginAccountgetFuturesPositionRiskOfSubAccountgetFuturesPositionRiskOfSubAccountV2getIpRestrictionForASubAccountApiKeygetManagedSubAccountDepositAddressgetMovePositionHistoryForSubAccountgetSubAccountDepositAddressgetSubAccountDepositHistorygetSubAccountsStatusOnMarginOrFuturesgetSummaryOfSubAccountsFuturesAccountgetSummaryOfSubAccountsFuturesAccountV2getSummaryOfSubAccountsMarginAccountmarginTransferForSubAccountmovePositionForSubAccountqueryManagedSubAccountAssetDetailsqueryManagedSubAccountFuturesAssetDetailsqueryManagedSubAccountListqueryManagedSubAccountMarginAssetDetailsqueryManagedSubAccountSnapshotqueryManagedSubAccountTransferLogMasterAccountInvestorqueryManagedSubAccountTransferLogMasterAccountTradingqueryManagedSubAccountTransferLogSubAccountTradingquerySubAccountAssetsquerySubAccountAssetsAssetManagementquerySubAccountFuturesAssetTransferHistoryquerySubAccountListquerySubAccountSpotAssetsSummaryquerySubAccountSpotAssetTransferHistoryquerySubAccountTransactionStatisticsqueryUniversalTransferHistorysendRequestsendSignedRequestsubAccountFuturesAssetTransfersubAccountTransferHistorytransferToMastertransferToSubAccountOfSameMasteruniversalTransferwithdrawlAssetsFromTheManagedSubAccount