Aquanow
Legacy
Legacy
  • About Aquanow
    • Introduction
  • VERSION DIFFERENCES
    • Latest vs Legacy
  • User Guide
    • Trading
      • Order Book
      • Submitting Orders
      • Order Types / Strategies
      • Trade Management
    • Automated Conversions
      • Autopilot
    • Deposits & Withdrawals
      • Deposits
      • Withdrawals
      • Balances
      • Transaction History
      • Approval Workflows
    • Account Management
      • CSV Exports
      • Address Management
      • IP Whitelisting
      • User List
  • Integration Guide
    • API Keys
      • Rate and API Key Limits
    • Authentication
    • Staging environment
    • Postman
    • Supported Assets and Tickers
    • Testnet and Faucet
  • API Endpoints | V1.0
    • Accounts API
      • User Balances
      • API Keys
    • Transaction API
      • Get Transactions
      • Create Transactions
      • Approvals API
      • Get Withdrawal Fee Estimate
    • Executions API
      • GET or Query Orders
      • Trading Strategies
    • Market Data API
      • Authorized Market Data
  • API Endpoints | V2.0
    • Transaction API
      • Get Transactions
    • Executions API
      • GET or Query Orders
      • Trading Strategies
  • Webhooks
    • Subscribing to Webhooks
    • Transaction Webhook
  • Websockets
    • Introduction
    • Authenticated Websockets
      • Market Data Websocket
      • Reporting Websocket
  • Data Objects & Statuses
    • Websocket Objects
    • Transaction Objects
      • Approval Objects
      • Fee Estimate Objects
    • Accounts Objects
    • Executions Objects
      • Duration Order Objects
    • Market Data Objects
    • Statuses
  • FAQs and Misc. Information
    • FAQs
    • Misc. Information
Powered by GitBook
On this page
  1. User Guide
  2. Deposits & Withdrawals

Approval Workflows

Integrating user approval workflows with Aquanow

PreviousTransaction HistoryNextAccount Management

Clients with multiple users accessing the same trading account can create child users with different access rights, including trading and withdrawing.

Approval workflows adds a layer of control and oversight to our clients, ensuring that trades and withdrawals initiated by certain users are reviewed and approved by users with higher privileges. The parent account, or a child user with approver rights must approve the trade/withdrawal before it is processed and finalized. The approval process for this right is controlled in the "Pending Approvals" tab, which is at the right of Trade History.

Example Workflow: Child user with no withdrawal rights:

A child user with no withdraw rights logs in and initiates the withdrawal in the portal.

The withdrawal request remains in a Pending state until it receives approval from a user with higher privileges.

The child user that initiated the withdrawal can only view this request and cancel it on the Pending approvals screen. These users have no authority to approve it.

When a pending approval is approved, the request status is updated to "Approved" and the request begins processing. Afterwards, the trade/withdrawal can be viewed under the Trade/Transaction History tab, respectively.

Initiating a withdrawal of BTC