Variable DefiClaimTypeConst
DefiClaimType: {
LP_FEE: "LP_FEE";
REDEMPTION: "REDEMPTION";
REWARD_INVESTMENT: "REWARD_INVESTMENT";
REWARD_PROTOCOL: "REWARD_PROTOCOL";
} = ...
Type Declaration
-
ReadonlyLP_FEE: "LP_FEE"
-
ReadonlyREDEMPTION: "REDEMPTION"
-
ReadonlyREWARD_INVESTMENT: "REWARD_INVESTMENT"
-
ReadonlyREWARD_PROTOCOL: "REWARD_PROTOCOL"
Claim routing type. Determines which companion fields are required: -
REWARD_PROTOCOL: protocol-level rewards (e.g. Aave incentive, Radiant) — requiresdefiProtocolId+binanceChainId-REWARD_INVESTMENT: per-investment rewards — requiresinvestmentId-LP_FEE: Uniswap V3/V4 LP fees — requiresinvestmentId+nftId-REDEMPTION: redeem principal (Lista / Aster / Solv etc.) — requiresinvestmentId+redemptionIdProtocol constraints — not everyclaimTypeis valid for every protocol; an invalid combination is rejected (40453or40454): -REWARD_PROTOCOLis not supported for LP (liquidity-pool) protocols in this release. -REWARD_INVESTMENTis not supported for PancakeSwap V3 farming positions; useLP_FEEto claim farming incentives there. -LP_FEEapplies only to concentrated-liquidity (V3/V4) LP positions. -REDEMPTIONapplies only to protocols with a redemption / lock-up flow (Lista, Aster, Solv). The validclaimTypes for a specific position are returned in that position'spositionDetail.claimTypes(see the position list) — branch on that rather than hard-coding the mapping. Note: error messages may surface the protocol id with a chain prefix (e.g.bsc_pancakeswap4); the canonical id in API fields is the un-prefixed form (e.g.pancakeswap4).