Overview
The depo.to API provides simple REST endpoints to generate and manage deposit addresses across 5 blockchains (Ethereum, Arbitrum, Optimism, Polygon, Solana). Accept USDC from any supported chain and have it automatically bridge to Base network via integrated bridge providers.Get your API key: Visit depo.to/dashboard to create an account and generate your API key
Base URL
Authentication
All API requests require an API key in thex-api-key header:
API Endpoints
Create Address Group
POST /wallet/createGenerate deposit addresses for a target chain and assetGet Address Group
GET /wallet/get/{groupId}Retrieve addresses and transaction historyList Address Groups
GET /auth/addressesGet all address groups for your accountUpdate Address Group
PUT /wallet/{groupId}Modify sponsoring settingsGet Supported Chains
GET /chainsList all supported blockchainsGet Sponsor Balance
GET /wallet/balanceCheck your sponsor account balanceQuick Start
Here’s a complete example to create an address group and retrieve deposit addresses:How It Works
1
Create Address Group
Call
/wallet/create with targetChain: "base", the destination wallet address, and targetAsset: "USDC"2
Receive Deposit Addresses
Get deposit addresses for all supported source chains
3
User Sends USDC
Your user sends USDC to any of the generated addresses from their preferred chain
4
Automatic Bridging
depo.to automatically detects deposits (checks every 5 minutes) and bridges to Base via the integrated bridge providers
5
USDC Arrives on Base
USDC arrives at the destination address in 1-15 minutes (minus bridge, gas, & swap fees)
Rate Limits
API requests are rate-limited based on your plan. See Pricing for more details. Rate limit headers are included in responses:Error Handling
All errors follow a consistent format:HTTP Status Codes
| Code | Description |
|---|---|
| 200 | Success |
| 400 | Bad Request - Invalid parameters |
| 401 | Unauthorized - Invalid API key |
| 404 | Not Found - Resource doesn’t exist |
| 429 | Too Many Requests - Rate limit exceeded |
| 500 | Internal Server Error |
Example Error Handling
Best Practices
Secure API Keys
Secure API Keys
- Store API keys in environment variables
- Never commit keys to version control
- Use different keys for development and production
- Rotate keys regularly
Cache Addresses
Cache Addresses
Deposit addresses don’t change - cache them to reduce API calls:
Implement Retry Logic
Implement Retry Logic
Handle transient errors with exponential backoff:
Monitor Transaction Status
Monitor Transaction Status
Poll the
/wallet/addresses endpoint to track deposits: