Skip to main content
Most read-only data your UI needs to render deposit and withdrawal flows — supply caps, minimum order sizes, per-asset fees, and SLAs — is returned inline on the discovery response (GET /v2/amplify/vaults). A single dedicated helper, GET /v2/amplify/calculateWithdrawalFee, computes the exact fee for a specific offerAmount + wantAsset redemption so you can preview it before the user submits a withdrawal. Neither requires an RPC connection — the backend reads the indexer and on-chain state for you.

Dedicated Helpers

EndpointDescription
GET /v2/amplify/calculateWithdrawalFeeCompute the fee a user would be charged for a specific offerAmount + wantAsset redemption

Fields Returned by /v2/amplify/vaults

The following per-deployment fields are already present on the discovery response — there are no separate endpoints for them:
FieldShapeDescription
depositSupplyCap{ raw, formatted, decimals, hasCap }Maximum total deposit. hasCap=false means the cap is maxUint256 (effectively uncapped)
minimumWithdrawalOrderSize{ raw, formatted, decimals }Minimum shareAmount accepted by /v2/amplify/withdraw
assets[].depositFees / assets[].withdrawFees{ bps, percentage }Per-asset fees (basis points + human-readable percentage)
assets[].withdrawalSLAsProtobuf duration strings (e.g. "86400s")Expected delay, expiry buffer, queue and accountant-rate SLAs
Fetch them once during account discovery and cache them client-side; they change rarely.

Common Error Responses

StatusMeaning
400Invalid parameters
404Account or fee module not found for the given vaultAddress + chainId
503Upstream RPC or indexer unavailable