Import
Usage
Parameters
All parameters are optional and can be combined to narrow the results.| Parameter | Type | Required | Description |
|---|---|---|---|
yieldType | YieldType | No | Filter by yield strategy (CORE, TREASURY, or FRONTIER) |
chains | number[] | No | Filter by chain IDs (e.g., [1, 8453]) |
address | string | No | Filter by exact token address (cache-only) |
symbol | string | No | Filter by token symbol (cache-only) |
The
yieldType and chains filters are applied at the API level. The
address and symbol filters are applied client-side against the cached
asset data.Return Type
ReturnsSupportedAsset[] — token metadata only. This type intentionally does not include depositable or withdrawable flags because those are per-account properties. See VaultSupportedAsset below for per-account flags.
- Type Definition
- Example Response
Examples
- By Chain
- Combined Filters
- With React Query
- Asset Selector
Account-Level Availability
Thedepositable and withdrawable flags live on each account’s supportedAssets array as VaultSupportedAsset, not on the global SupportedAsset returned here. The same token may be depositable on one account but not another.
Checking Permit Support
To determine the optimal deposit flow for a token, useprepareDepositAuthorization() which automatically detects permit support at the contract level:
Error Handling
| Error Message Pattern | Description | Resolution |
|---|---|---|
"SDK not initialized" | SDK not initialized | Call initAmplifySDK() first |
"No vault found" | No account matches parameters | Verify yieldType and chainId |
Related
- YieldType - Yield strategy types
- Deposit Workflow - Using assets for deposits
- Deposits Guide - Complete deposit examples