Skip to main content
In a nutshell
The Blockradar Withdraw API allows you to send stablecoin assets from your wallets to external blockchain addresses. It supports single withdrawals, batch withdrawals to multiple recipients, and provides fee estimation before execution.
Blockradar Withdraw Interface

Prerequisites

Before using the Withdraw API, ensure you have:
1

API Key

Get your API key from the Blockradar Dashboard. Navigate to Developers to generate one.
2

Wallet Created

Create a wallet via the Create Wallet API or dashboard. You’ll need the walletId for withdrawal operations.
3

Asset ID

Get the assetId for the token you want to withdraw from Assets in the dashboard or via the Get Assets API.
4

Sufficient Balance

Ensure your wallet has enough balance of the asset to withdraw, plus native currency (ETH, BNB, MATIC, etc.) to cover network fees.

How It Works

The Withdraw API sends stablecoin assets from your Blockradar wallet to any external blockchain address:

Single Withdrawal

Send assets to one recipient address with a single API call.

Batch Withdrawal

Send assets to multiple recipients in a single API call, reducing overhead and simplifying bulk payouts.

Fee Estimation

Calculate network fees before execution to ensure sufficient balance and display costs to users.

Sign-Only Mode

Sign transactions without broadcasting for advanced use cases like offline signing or custom submission.

Master Wallet vs Child Address

The Withdraw API is available at two levels:

Master Wallet

Withdraw directly from your master wallet. Ideal for treasury operations and centralized fund management.

Child Address

Withdraw from individual child addresses. Perfect for user-specific operations and segregated fund management.

Endpoints


Single Withdrawal

Send assets to a single recipient address.

Request Parameters

Parameters marked with * are required for single withdrawals but are not needed if you’re using the assets array for batch withdrawals.

Single Withdrawal Example

Single Withdrawal Response


Batch Withdrawals

Send assets to multiple recipients in a single API call. Batch withdrawals are executed sequentially, and each withdrawal is processed as a separate blockchain transaction.

When to Use Batch Withdrawals

  • Bulk payouts: Pay multiple employees, vendors, or partners at once
  • Distributions: Send assets to multiple addresses
  • Multi-recipient transfers: Send different amounts to different addresses
  • Operational efficiency: Reduce API calls and simplify payout logic

Batch Request Parameters

For batch withdrawals, use the assets array instead of individual parameters: Each item in the assets array:

Batch Withdrawal Example

Batch Withdrawal Response

Handling Partial Failures

Batch withdrawals support partial success. If some withdrawals fail, others will still execute:

Batch Withdrawal Rules


Estimating Network Fees

Always estimate fees before executing withdrawals to ensure sufficient native token balance and to display accurate costs to users.

Single Fee Estimation

Single Fee Response

Batch Fee Estimation

Estimate fees for multiple withdrawals at once:

Batch Fee Response

Fee Response Fields


Sign-Only Mode

Sign transactions without broadcasting them to the blockchain. Useful for:
  • Offline signing: Prepare transactions for later submission
  • Multi-signature workflows: Collect signatures before submission
  • Transaction inspection: Review transaction details before broadcasting

Sign-Only Example

Sign-Only Response


Child Address Withdrawals

Withdraw from individual child addresses instead of the master wallet:
Child address withdrawals also support batch operations using the assets array, following the same format as master wallet batch withdrawals.

Webhook Events

Monitor withdrawal completion through webhooks:

Webhook Payload


Complete Flow Example

Here’s a full implementation showing the fee estimation → user confirmation → withdrawal flow:

Error Responses


Best Practices

Security

  • Validate addresses: Always verify recipient addresses before initiating withdrawals
  • Use references: Track withdrawals with unique reference IDs for reconciliation
  • Implement webhooks: Listen for withdraw.success and withdraw.failed events to confirm status
  • Check AML: Blockradar automatically screens addresses—review any flagged transactions

Fee Management

  • Estimate before execution: Always call the network-fee endpoint before withdrawals
  • Monitor native balance: Ensure sufficient ETH/BNB/MATIC for gas fees
  • Use batch for efficiency: Group multiple withdrawals to reduce API calls and operational overhead

Error Handling

  • Handle partial failures: In batch withdrawals, check both success and errors arrays
  • Implement retries: Use exponential backoff for transient failures
  • Log all transactions: Store transaction IDs and hashes for debugging and reconciliation

Performance

  • Use appropriate batch sizes: Larger batches reduce API calls but increase individual request time
  • Cache asset IDs: Store asset IDs locally to avoid repeated lookups
  • Implement rate limiting: Respect API rate limits to avoid throttling

API Reference

Master Wallet Endpoints

Child Address Endpoints


Support

The Withdraw API provides a flexible interface for sending stablecoin assets to external addresses. Start with single withdrawals and fee estimation, then incorporate batch operations for bulk payouts as your needs grow.