Skip to main content
The Get Wallets endpoint allows you to retrieve all Devdraft wallets associated with your application. Devdraft wallets are blockchain wallets that can hold and transact with various stablecoins across different supported networks.

Endpoint Details

  • Method: GET
  • URL: /api/v0/wallets
  • Content-Type: application/json

Authentication

This endpoint requires API key authentication using both:
  • x-client-key: Your application’s client key
  • x-client-secret: Your application’s client secret
Include both headers in your request as shown in the examples below.

Request

This endpoint doesn’t require any request body or query parameters. The wallets returned are automatically filtered to only show wallets associated with your authenticated application.

Response

Success Response (200 OK)

Response Fields

Wallet Object

Balance Object

Supported Networks

Devdraft currently supports the following blockchain networks for wallets:
  • Ethereum (ethereum) - Ethereum mainnet
  • Solana (solana) - Solana blockchain
  • Polygon (polygon) - Polygon (Matic) network
  • Avalanche C-Chain (avalanche_c_chain) - Avalanche C-Chain
  • Tron (tron) - Tron network

Supported Currencies

  • USDC (usdc) - USD Coin (available on all networks)
  • EURC (eurc) - Euro Coin (available on Ethereum, Solana, Base)
  • USDT (usdt) - Tether USD (available on Ethereum, Polygon, Tron)
  • DAI (dai) - Dai Stablecoin (available on Ethereum, Polygon)
  • PYUSD (pyusd) - PayPal USD (available on Ethereum)
  • ETH (eth) - Ethereum (on Ethereum network)
  • SOL (sol) - Solana (on Solana network)
  • MATIC (matic) - Polygon (on Polygon network)
  • AVAX (avax) - Avalanche (on Avalanche C-Chain)

Example Requests

Error Responses

Wallet Management

  • App Wallets: Associated with your application, created automatically
  • Client Wallets: Associated with specific customers/clients
  • Treasury Wallets: Used for internal fund management
  • Real-time: Balances are fetched in real-time from blockchain networks
  • Multi-network: Wallets can hold tokens across multiple networks
  • Precision: All amounts returned as strings to preserve decimal precision
  • Application Scoping: Only your app’s wallets are returned
  • Rate Limiting: Standard rate limits apply (see rate limiting docs)
  • Audit Trail: All wallet operations are logged for compliance

Important Notes

Balance Precision: All balance amounts are returned as strings to preserve decimal precision and avoid floating-point arithmetic issues in your application.
Real-time Data: The wallet balances are fetched in real-time from the blockchain networks, ensuring you always get the most current balance information.
Performance: Consider caching wallet data for frequently accessed information, but always fetch fresh data for transaction-critical operations.

Use Cases

Portfolio Overview

Display all wallet balances to users in a dashboard

Asset Management

Track stablecoin holdings across different networks

Transaction Planning

Check available balances before initiating transfers

Reporting

Generate financial reports and statements

Monitoring

Monitor wallet activity and balance changes

Multi-Chain Strategy

Manage cross-chain liquidity and optimization

Next Steps

After retrieving your wallets, you can:
1

Analyze Portfolio

Review balances across different networks and currencies
2

Plan Transactions

Use wallet addresses and balances for transfer planning
3

Monitor Changes

Set up monitoring for balance changes and transactions
4

Integrate Dashboard

Display wallet data in your application’s user interface
  • POST /api/v0/transfers/direct-wallet - Create wallet-to-wallet transfer
  • POST /api/v0/transfers/stablecoin-conversion - Convert between stablecoins
  • GET /api/v0/transfers/{id} - Check transfer status
  • POST /api/v0/webhooks - Set up wallet balance notifications