Withdraw from Yield

In this section, you’ll learn how to request ready-to-use transaction data (bytecode) for withdrawing from a yield position.

Prerequisites:

Protocol-Specific Approach

Use this when you want to work with a specific yield protocol. Request Transaction Data Fetch specific protocol information using:

GET /strategies/:id/bytecode

Required Parameters:

Parameter	Description	Example
action	Type of operation	`withdraw` or `request-withdraw`
amount	Amount in token’s smallest unit	`10000000`
wallet	Wallet that owns the position	`0x1234...`

The request-withdraw action is only for Ondo Global Markets strategies (tokenized stocks & ETFs), whose orders settle asynchronously. For every other yield strategy, use withdraw.

Preview quotes without a connected wallet. wallet also accepts the zero address (0x000…0) or a well-known burn address (e.g. 0x000…dEaD, 0x111…, 0x222…). The response is priced exactly like a real request but includes previewOnly: true and omits id, bytecode, userOperation, singleUseAddress, and orderUid — no Action is created, and the address is never persisted or synced to Moralis/Helius.

A previewOnly response has no bytecode to sign. Use the user’s real, owned wallet address for any request you intend to execute.

Pick the section that matches where the user wants to receive the withdrawn funds. Each shows the extra parameters, an example request, and the response you get back.

Simple withdraw

Withdraw to the strategy’s underlying token on the strategy’s own chain — no bridge. Only the required parameters above are needed, and crossChain.isCrossChain stays false. For supported ERC-4626 strategies, add withdrawAll=true when the user intends to redeem the wallet’s complete vault-share balance. Continue sending amount as the expected underlying amount; partial withdrawals must omit withdrawAll and remain asset-denominated. Example Request:

GET /strategies/aave-usdc-polygon/bytecode?action=withdraw&amount=10000000&wallet=0x1234...

Example Response:

{
  "feeCharged": "0",
  "chainIdIn": 137,
  "chainIdOut": 137,
  "id": "65f3a1c8e9b2d4f8a7c1d2e3",
  "crossChain": {
    "isCrossChain": false,
    "chainIdIn": 137,
    "chainIdOut": 137
  },
  "quote": null,
  "bytecode": [
    {
      "to": "0x794a61358D6845594F94dc1DB02A252b5b4814aD",
      "value": "0",
      "data": "0xe8eda9df...",
      "chainId": "137"
    }
  ]
}

Same-chain swap withdraw

Want to receive a different token on the strategy’s own chain? Pass toTokenAddress (with a toChainId/chainIdOut matching the strategy chain) to swap the withdrawn underlying into that token. The response appends the swap transaction(s) after the withdraw bytecode, and crossChain.isCrossChain stays false. Additional Parameters:

Parameter	Description	Example
toChainId or chainIdOut	Destination chain ID. Use the strategy chain for same-chain swaps. Required when `toTokenAddress` is provided.	`137` (Polygon)
toTokenAddress	Token address to receive after withdrawing (same-chain). When it differs from the underlying asset, the response appends swap transaction(s) after the withdraw.	`0x7ceB2...f619` (WETH)

When toTokenAddress is provided with a toChainId matching the strategy chain, the API automatically appends a same-chain swap from the strategy’s underlying asset to toTokenAddress after the withdraw. The amount parameter refers to the underlying amount withdrawn (before the swap), and crossChain.isCrossChain remains false.

Example Request: If you hold a position in a USDC strategy but want to receive WETH on the same chain, pass toTokenAddress to swap after withdrawing:

GET /strategies/aave-usdc-polygon/bytecode?action=withdraw&amount=10000000&wallet=0x1234...&toChainId=137&toTokenAddress=0x7ceB23fD6bC0adD59E62ac25578270cFf1b9f619

Example Response:

{
  "feeCharged": "0",
  "chainIdIn": 137,
  "chainIdOut": 137,
  "id": "65f3a1c8e9b2d4f8a7c1d2e3",
  "crossChain": {
    "isCrossChain": false,
    "chainIdIn": 137,
    "chainIdOut": 137
  },
  "quote": {
    "bridge": "1INCH",
    "sender": "0x1234...",
    "fromChainId": 137,
    "fromTokenAddress": "0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174",
    "toChainId": 137,
    "toTokenAddress": "0x7ceB23fD6bC0adD59E62ac25578270cFf1b9f619",
    "inputAmount": {
      "value": "10000000",
      "decimals": 6,
      "humanized": "10.0",
      "symbol": "USDC"
    },
    "outputAmount": {
      "value": "2500000000000000",
      "decimals": 18,
      "humanized": "0.0025",
      "symbol": "WETH"
    },
    "minimumOutputAmount": {
      "value": "2487500000000000",
      "decimals": 18,
      "humanized": "0.0024875",
      "symbol": "WETH"
    }
  },
  "bytecode": [
    {
      "to": "0x794a61358D6845594F94dc1DB02A252b5b4814aD",
      "value": "0",
      "data": "0x69328dec...",
      "chainId": "137"
    },
    {
      "to": "0x1111111254EEB25477B68fb85Ed929f73A960582",
      "value": "0",
      "data": "0x12aa3caf...",
      "chainId": "137"
    }
  ]
}

Unlike a bridge quote, a same-chain swap quote has fromChainId === toChainId (both the strategy chain), and crossChain.isCrossChain stays false — no cross-chain tracking is needed.

Cross-chain swap withdraw

Want the funds on another chain? Pass a toChainId/chainIdOut (with a toTokenAddress) that differs from the strategy’s chain. The response adds a quote object describing the bridge selection, the resolved tokens, and the expected/minimum output amount, and sets crossChain.isCrossChain to true. Additional Parameters:

Parameter	Description	Example
toChainId or chainIdOut	Destination chain ID for the withdrawn funds	`8453` (Base)
toTokenAddress	Destination token address. Required when `toChainId` or `chainIdOut` is provided. If `toChainId`/`chainIdOut` is omitted, `toTokenAddress` is also not required.	`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` (USDC on Base)

Example Request:

GET /strategies/aave-usdc-arbitrum/bytecode?action=withdraw&amount=10000000&wallet=0x1234...&toChainId=8453&toTokenAddress=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Example Response:

{
  "feeCharged": "0",
  "chainIdIn": 42161,
  "chainIdOut": 8453,
  "id": "6a04f2f75bf7233c6220b3ca",
  "crossChain": {
    "isCrossChain": true,
    "chainIdIn": 42161,
    "chainIdOut": 8453
  },
  "quote": {
    "bridge": "CCTP",
    "sender": "0x49A54d4d925868475Eb8d2cb2c784481ca755e8A",
    "fromChainId": 42161,
    "fromTokenAddress": "0x4F38e7a76b9C32Ab68FBf500E4d52806B15AB93b",
    "toChainId": 8453,
    "toTokenAddress": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "inputAmount": {
      "value": "999870",
      "decimals": 18,
      "humanized": "0.00000000000099987",
      "symbol": "KPK-podsUSDCy"
    },
    "outputAmount": {
      "value": "999000",
      "decimals": 6,
      "humanized": "0.999",
      "symbol": "USDC"
    },
    "minimumOutputAmount": {
      "value": "999000",
      "decimals": 6,
      "humanized": "0.999",
      "symbol": "USDC"
    },
    "chainIdIn": 42161,
    "chainIdOut": 8453
  },
  "bytecode": [
    { "to": "0x...", "value": "0", "data": "0x...", "chainId": "42161" }
  ]
}

The top-level id is used for execution tracking — store it and pass it to GET /actions/:id to track the cross-chain withdrawal through completion (see Checking Cross-Chain Withdrawal Status below).The quote object describes which bridge was selected (bridge), the expected outputAmount, and the worst-case minimumOutputAmount (slippage floor). Display these to the user before they sign.

Output format options

By default the endpoint returns raw bytecode. These optional parameters change the response format and apply to either withdraw type above.

Parameter	Description	Example
output	Response format: `bytecode` (default), `userOperation`, `fireblocks`, or `instructions` (Solana)	`fireblocks`
accountId	Fireblocks vault account ID. Required when `output=fireblocks`	`12`
webhookURL	Optional per-action webhook endpoint (URI). When set, action update webhooks are delivered to this URL instead of the customer default webhook URL.	`https://example.com/webhooks/strategy-action`

Example Request (Fireblocks output): If you are using Fireblocks custody, set output=fireblocks and pass your vault accountId. The wallet parameter must be a smart wallet previously provisioned via POST /fireblocks-smart-account (see Fireblocks Integration).

GET /strategies/aave-usdc-polygon/bytecode?action=withdraw&amount=10000000&wallet=0xSafeAddress&output=fireblocks&accountId=YOUR_VAULT_ACCOUNT_ID

Example Response:

{
  "feeCharged": "0",
  "chainIdIn": 137,
  "chainIdOut": 137,
  "id": "65f3a1c8e9b2d4f8a7c1d2e3",
  "crossChain": {
    "isCrossChain": false,
    "chainIdIn": 137,
    "chainIdOut": 137
  },
  "quote": null,
  "transactionData": {
    "transactionRequest": {
      "operation": "CONTRACT_CALL",
      "assetId": "MATIC_POLYGON",
      "source": {
        "type": "VAULT_ACCOUNT",
        "id": "YOUR_VAULT_ACCOUNT_ID"
      },
      "destination": {
        "type": "ONE_TIME_ADDRESS",
        "oneTimeAddress": {
          "address": "0xSafeAddress"
        }
      },
      "amount": "0",
      "extraParameters": {
        "contractCallData": "0x6a761202..."
      },
      "note": "withdraw aave-usdc-polygon",
      "failOnLowFee": true
    }
  }
}

The transactionData.transactionRequest payload can be submitted directly to the Fireblocks Transactions API (POST /v1/transactions) — no further encoding required. The Earn Owner vault must be configured as the signer (see Fireblocks Integration). After the withdrawal completes, transfer funds out of the smart wallet to your Omnibus wallet or any other destination.

Use GET /strategies to list available protocols, then pass the chosen strategy ID into the protocol-specific approach above.

Executing the Transaction

Batch all bytecode legs on the same chainId into one atomic transaction. See Executing Bytecode.

const { data: result } = await pods.get('/strategies/aave-usdc-polygon/bytecode', {
  params: { action: 'withdraw', amount: '10000000', wallet: walletAddress }
})

// Batch result.bytecode into ONE tx — do not send each leg separately
console.log('Legs to batch atomically:', result.bytecode.length)

Make sure you have sufficient balance in your position before attempting to withdraw. Check your open positions first using the check positions endpoint.

Checking Cross-Chain Withdrawal Status

Cross-chain withdrawals are asynchronous: the source-chain withdraw + bridge transaction is signed first, then the bridged funds are delivered on the destination chain. To track progress to completion, use the id returned in the bytecode response:

GET /actions/:id

Path Parameters:

Parameter	Description	Example
id	The `id` returned by `GET /strategies/:id/bytecode`	`6a04f2f75bf7233c6220b3ca`

Example Request:

GET /actions/6a04f2f75bf7233c6220b3ca

Example Response (withdrawal in flight):

{
  "id": "6a04f2f75bf7233c6220b3ca",
  "type": "CROSSCHAIN_INVESTMENT_WITHDRAW",
  "status": "PENDING",
  "strategyId": "65a1b2c3d4e5f6a7b8c9d0e1",
  "strategySlug": "aave-usdc-polygon",
  "initialDate": "2026-05-19T14:30:15Z",
  "createdAt": "2026-05-19T14:30:00Z",
  "originAddress": "0x49A54d4d925868475Eb8d2cb2c784481ca755e8A",
  "receiverAddress": "0x49A54d4d925868475Eb8d2cb2c784481ca755e8A",
  "amounts": {
    "assetIn": {
      "token": {
        "address": "0x4F38e7a76b9C32Ab68FBf500E4d52806B15AB93b",
        "symbol": "KPK-podsUSDCy",
        "decimals": 18
      },
      "chain": { "id": 42161, "name": "arbitrum" },
      "amountRaw": "999870",
      "amountHumanized": "0.00000000000099987",
      "amountInUSD": "1.00"
    },
    "assetOut": {
      "token": {
        "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "symbol": "USDC",
        "decimals": 6
      },
      "chain": { "id": 8453, "name": "base" },
      "amountRaw": "999000",
      "amountHumanized": "0.999",
      "amountInUSD": "1.00"
    }
  },
  "transactions": [
    {
      "chain": "arbitrum",
      "txHash": "0xabc...",
      "blockNumber": 19234567,
      "timestamp": "2026-05-19T14:30:15Z",
      "status": "SUCCESS",
      "underlyingAssetFeeValue": "0"
    },
    {
      "chain": "base",
      "txHash": null,
      "blockNumber": null,
      "timestamp": null,
      "status": "PENDING",
      "underlyingAssetFeeValue": null
    }
  ],
  "finishedAt": null,
  "underlyingAssetFeeValue": "0"
}

Status values:

Status	Meaning
`INITIAL`	Created, awaiting on-chain execution
`PENDING`	At least one transaction broadcast; awaiting confirmations
`SUCCESS`	All steps completed; funds arrived on the destination chain
`FAILED`	A step failed
`REFUND_REQUIRED`	Funds withdrawn but the bridge step failed; refund is needed
`REFUNDED`	Refund completed
`EXPIRED`	Quote expired before execution

Poll this endpoint until status reaches a terminal value (SUCCESS, FAILED, REFUNDED, or EXPIRED). The transactions array lists each on-chain hash as it is confirmed.

Same-chain withdrawals do not need this polling — the withdraw completes inline with the user’s signed transaction. The id is still returned for record-keeping and can be queried the same way.

Webhook Notifications

As an alternative to polling, Pods can push every status transition to a URL you control. The payload is identical to GET /actions/:id, so you can drive the same UI off either source.

Default webhook URL configuration is currently provisioned manually — contact the Pods team to register your default webhookURL (and any optional custom headers, e.g. an HMAC signature header). For a single withdrawal request, pass webhookURL on the bytecode endpoint to override the customer-level default. Self-service configuration via the admin panel is coming soon.

Transport:

Field	Value
Method	`POST`
URL	Your `webhookURL`
`Content-Type`	`application/json`
Custom headers	Any headers you configure with the team are sent on every request

Body shape:

{
  "messageType": "ACTION_UPDATE",
  "data": {
    /* same object returned by GET /actions/:id */
  }
}

Example payload (cross-chain withdrawal reaching SUCCESS):

{
  "messageType": "ACTION_UPDATE",
  "data": {
    "id": "6a04f2f75bf7233c6220b3ca",
    "type": "CROSSCHAIN_INVESTMENT_WITHDRAW",
    "status": "SUCCESS",
    "strategyId": "65a1b2c3d4e5f6a7b8c9d0e1",
    "strategySlug": "aave-usdc-polygon",
    "initialDate": "2026-05-19T14:30:15Z",
    "createdAt": "2026-05-19T14:30:00Z",
    "originAddress": "0x49A54d4d925868475Eb8d2cb2c784481ca755e8A",
    "receiverAddress": "0x49A54d4d925868475Eb8d2cb2c784481ca755e8A",
    "amounts": {
      "assetIn": {
        "token": {
          "address": "0x4F38e7a76b9C32Ab68FBf500E4d52806B15AB93b",
          "symbol": "KPK-podsUSDCy",
          "decimals": 18
        },
        "chain": { "id": 42161, "name": "arbitrum" },
        "amountRaw": "999870",
        "amountHumanized": "0.00000000000099987",
        "amountInUSD": "1.00"
      },
      "assetOut": {
        "token": {
          "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "symbol": "USDC",
          "decimals": 6
        },
        "chain": { "id": 8453, "name": "base" },
        "amountRaw": "999000",
        "amountHumanized": "0.999",
        "amountInUSD": "1.00"
      }
    },
    "transactions": [
      {
        "chain": "arbitrum",
        "txHash": "0xabc...",
        "blockNumber": 248123456,
        "timestamp": "2026-05-19T14:30:15Z",
        "status": "SUCCESS"
      },
      {
        "chain": "base",
        "txHash": "0xdef...",
        "blockNumber": 19234999,
        "timestamp": "2026-05-19T14:33:02Z",
        "status": "SUCCESS"
      }
    ],
    "finishedAt": "2026-05-19T14:33:02Z"
  }
}

Delivery semantics:

A request fires for every status change, so you may receive multiple deliveries per withdrawal (INITIAL → PENDING → SUCCESS).
Pods expects a 2xx response. Non-2xx responses are recorded but not automatically retried; reconcile with GET /actions/:id if you need at-least-once guarantees.
Respond as quickly as possible; do the heavy work asynchronously on your side.

Next Steps

Check Positions

View your remaining positions

New Deposit

Make a new deposit

Protocol Info

Check protocol information

Overview

Guides

Integrations

Agents

Withdraw from Yield

Protocol-Specific Approach

Simple withdraw

Same-chain swap withdraw

Cross-chain swap withdraw

Output format options

Executing the Transaction

Checking Cross-Chain Withdrawal Status

Webhook Notifications

Next Steps

Check Positions

New Deposit

Protocol Info

​Protocol-Specific Approach

​Simple withdraw

​Same-chain swap withdraw

​Cross-chain swap withdraw

​Output format options

​Executing the Transaction

​Checking Cross-Chain Withdrawal Status

​Webhook Notifications

​Next Steps

Check Positions

New Deposit

Protocol Info

Protocol-Specific Approach

Simple withdraw

Same-chain swap withdraw

Cross-chain swap withdraw

Output format options

Executing the Transaction

Checking Cross-Chain Withdrawal Status

Webhook Notifications

Next Steps