Skip to main content
POST
Redeem vault fees with an EVM account

Authorizations

Authorization
string
header
required

A JWT signed using your CDP API Key Secret, encoded in base64. Refer to the Generate Bearer Token section of our Authentication docs for information on how to generate your Bearer Token.

Headers

X-Wallet-Auth
string
required

A JWT signed using your Wallet Secret, encoded in base64. Refer to the Generate Wallet Token section of our Authentication docs for more details on how to generate your Wallet Token.

X-Idempotency-Key
string

An optional string request header for making requests safely retryable. When included, duplicate requests with the same key will return identical responses. Refer to our Idempotency docs for more information on using idempotency keys.

Required string length: 1 - 128

Path Parameters

address
string
required

The 0x-prefixed address of the EVM account that is the vault's fee recipient.

Pattern: ^0x[0-9a-fA-F]{40}$

Body

application/json

A request to redeem the fee shares held by the vault's fee recipient EVM account for the vault's underlying asset (e.g. USDC). The account signs an EIP-2612 permit over its vault shares, and the share approval and redemption are executed in a single transaction.

vaultId
string
required

The globally unique ID of the vault, which is a UUID prefixed with the string vault_.

Pattern: ^vault_[a-f0-9-]{36}$
Example:

"vault_019f5f10-096a-7a23-86df-f479650d813f"

maxSlippageBps
integer

The maximum share-price movement tolerated between calldata construction and onchain execution, in basis points. Defaults to 100 bps (1%) when omitted.

Required range: 0 <= x <= 9999
Example:

100

Response

Successfully broadcast the fee redemption.

The result of a vault fee redemption from an EVM account after broadcast.

transactionHash
string
required

The hash of the broadcast fee redemption transaction, as a 0x-prefixed hex string.

Pattern: ^0x[0-9a-fA-F]{64}$
Example:

"0xf8f98fb6726fc936f24b2007df5cb20e2b8444ff3dfaa2a929335f432a9be2e7"