Skip to main content
Equivalent to SDK’s getVaultsByConfig() and getSupportedAssets(). The GraphQL API returns all contract addresses needed for direct integration in a single request. This is the same API the Amplify SDK uses internally.

Endpoint

Headers

Query

Variables (all optional)

Example Request

Response

Response Types

Multiple configs can reference the same account (one per deposit token). Deduplicate by vault.id — each account has a single set of contract addresses and a supportedAssets array listing all tokens.
withdrawQueueModuleId and communityCodeDepositorModuleId can be null for accounts that don’t support external withdrawals or deposits.

Contract Address Mapping

The GraphQL field communityCodeDepositorModuleId is a legacy name. The contract it points to is the DistributorCodeDepositor. Use this address wherever the documentation refers to the distributorCodeDepositorAddress.

Available Yield Types


REST API (Simpler Alternative)

If you only need to list account–asset pairs without full contract addresses, you can use the REST endpoint.

Endpoint

Query Parameters

Example Request

Response

Response Types

The REST endpoint only returns vaultAddress (the BoringVault). For the full set of contract addresses needed for deposits, withdrawals, and cancellations, use the GraphQL API above.

Withdraw-Eligible Assets

Filter by withdrawable: true in either API:
  • GraphQL: Filter vault.supportedAssets where withdrawable == true
  • REST: GET /v2/amplify/vaultAssets?filter=withdrawable%3Dtrue&pageSize=100