Get a user's pending vault withdrawal requests
GET/v1/data/vaults/withdrawals
Returns a user's pending withdrawal requests across every vault that has a withdrawal queue / cooldown (LSTs, savings cooldowns, ERC-7540 async vaults). The static LST/savings withdrawal registry is always probed; pass vaults to additionally read arbitrary ERC-7540 vaults by address.
Each entry is normalised to a uniform shape so the frontend treats every protocol identically — render the list, and when status === "claimable" build the claim via the matching action endpoint (/v1/actions/vaults/lst or /savings).
Response: { chainId, account, count, requests }, where each requests[] entry carries:
| field | meaning |
|---|---|
lst | the share-token the request was made against |
brand, symbol | UI labels |
requestId | protocol-native id (NFT tokenId, queue index, 7540 requestId, or a bucket name like waiting/unbonded) — pass back to the claim action |
amountUnderlying | wei the request returns on claim (expected amount for floating-rate queues) |
status | pending · claimable · claimed · expired |
readyAt | unix seconds the request becomes claimable (fixed-cooldown protocols only) |
yieldProfile, denomination | present when the vault is in the public-data lookup |
Empty per-vault results are dropped.
Request
Responses
- 200
- 400
Flat requests[] of pending withdrawal requests across all queued/cooldown vaults for account.
Validation error