Subscription Request
Subscribe method. Must be
subscribeArray of topics to subscribe to. Must include
withdrawalExample: ["withdrawal"]Ticket created using the endpoint POST https://api.ripio.com/trade/ticket
Stream Response
Each WebSocket message includes a sequential numeric id. Each topic has its own unique sequence, and for private topics, the sequence is unique to each topic and user. It’s important to note that some topics will send a “welcome message”, which will have an id value of -1. Additionally, this sequence may be reset between connections, so be sure to update this value locally whenever you reconnect.
Topic name (always
withdrawal)Timestamp in milliseconds
Withdrawal details object
Subscription Example
Stream Response Example - Cryptocurrency Withdrawal
Stream Response Example - Fiat Withdrawal
Withdrawal Status Lifecycle
- pending: Withdrawal request created but not yet processed
- confirmed: Withdrawal sent and confirmed
- failed: Withdrawal failed and was not sent
Withdrawal Types
External Withdrawals
- To external blockchain addresses
- Requires blockchain confirmation
- Include miner fees
- Network dependent timing
- Bitcoin: ~10 minutes (6 confirmations)
- Ethereum: ~2 minutes (12 confirmations)
Internal Transfers
- Between BitcoinTrade accounts
- No blockchain involved
- No miner fees
- Confirm immediately
- Marked with
is_internal: true
Fee Structure
Platform Fee
- BitcoinTrade withdrawal fee
- Shown in
feefield - May vary by currency
- Deducted from withdrawal
Network Fee
- Blockchain miner fee
- Shown in
miner_feefield - For external withdrawals only
- Varies with network congestion
Total Cost
Total deducted = Platform fee + Miner feeKey Fields
| Field | Description |
|---|---|
| amount | Withdrawal amount |
| fee | BitcoinTrade fee |
| miner_fee | Network miner fee |
| status | Current state |
| hash | Blockchain transaction ID |
| is_internal | Internal transfer flag |
Blockchain Networks
| Network | Code | Currency |
|---|---|---|
| Bitcoin | bitcoin | BTC |
| Ethereum | ethereum | ETH |
| Bitcoin Cash | bitcoincash | BCH |
| And others | - | - |
Timing by Currency
| Currency | Type | Typical Confirmation |
|---|---|---|
| BTC | External | 10-30 minutes |
| ETH | External | 2-5 minutes |
| BCH | External | 3-10 minutes |
| BRL | Internal | Immediate |
| Others | Variable | Variable |
Calculation Examples
Usage Notes
- Authentication Required: Requires valid ticket from WebSocket authentication
- Real-time Updates: Receive notification when withdrawal is processed
- Multiple Notifications: Receive updates as status changes (pending → confirmed)
- Network Variable: Confirmation time depends on blockchain network
- Fee Information: Both platform and miner fees shown
Pending vs Confirmed
- Pending: Withdrawal submitted but not yet on blockchain
- Confirmed: Transaction sent to blockchain and confirmed
- Recommended: Wait for confirmed status before considering funds received
Use Cases
- Fund Tracking: Monitor outgoing funds
- Balance Updates: Update balance when withdrawal completes
- Withdrawal Confirmation: Confirm withdrawal success
- Fee Accounting: Record fees paid
- Transaction History: Build withdrawal history
- Compliance: Track all withdrawals for reporting