Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.
Coming Soon

Withdraw from Aave to Solana

Pre-release — The Intents Connect API is currently in development. If you're interested in early access, get in touch with the team.

Below is an example flow withdrawing from Aave using a Solana wallet using the Intents Connect API.

You'll need to run an execution to get the estimated output amount, estimate costs for the destination chain action, and sign the intent (withdraw from Aave). As a result, you'll withdraw from Aave into your Solana wallet.

Make sure to understand Execution Lifecycle before you proceed with the implementation.

1

List supported tokens

Use List supported tokens to find the assetId values you will need. You'll need to use the Intents API for that.

const response = await fetch(`https://intents-connect-alpha-api.aurora.dev/api/v1/supported_tokens`);
const tokens = await response.json();
Response explanation

The response includes tokens with their assetId in this format:

  • SOL tokens: nep141:sol.omft.near

  • USDC on Base: nep141:base-0x833589fcd6edb6e08f4c7c32d4f71b54bda02913.omft.near

[
  {
    "assetId": "nep141:sol.omft.near",
    "decimals": 9,
    "blockchain": "sol",
    "symbol": "SOL",
    "price": 84.79,
    "priceUpdatedAt": "2026-04-23T17:44:00.452Z"
  },
  {
    "assetId": "nep141:base-0x833589fcd6edb6e08f4c7c32d4f71b54bda02913.omft.near",
    "decimals": 6,
    "blockchain": "base",
    "symbol": "USDC",
    "price": 0.999706,
    "priceUpdatedAt": "2026-04-23T17:44:00.452Z",
    "contractAddress": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913"
  }
]
2

Request an execution

Use Request an execution endpoint.

const response = await fetch(`https://intents-connect-alpha-api.aurora.dev/api/v1/executions/${solanaWalletAccount}`, {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    // Generate your API key at https://studio.aurora.dev
    'x-api-key': 'API_KEY',
  },
  body: JSON.stringify({
    "dry": false,
    "metadata": {
      "intent": "aave_withdraw",
      "title": "Withdraw from Aave"
    },
    "outOperation": true,
    "quote": {
      "amount": "197373",
      "destinationAsset": "nep141:sol.omft.near",
      "originAsset": "nep141:base-0x833589fcd6edb6e08f4c7c32d4f71b54bda02913.omft.near",
      "slippageTolerance": 100
    },
    "steps": [
      {
        "functionSignature": "withdraw(address,uint256,address)",
        "parameters": [
          "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "197373",
          "0xFe6EF968D2F7B2e9CCCF92150d96c930C3CC4a4E"
        ],
        "to": "0xA238Dd80C259a72e81d7e4664a9801593F98d1c5",
        "value": "0"
      },
      {
        "functionSignature": "transfer(address,uint256)",
        "parameters": [
          "{DEPOSIT_ADDRESS}",
          "197373"
        ],
        "to": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "value": "0"
      }
    ],
    "type": "evm"
  })
});
const execution = await response.json();
Request data explanation

  • dry is false, unless we want to get just the estimates

  • metadata contains information displayed in the UI - it's optional

  • outOperation means that it's outbound operations and does not require a deposit

  • quote

    • amount contains the input amount used for the action

    • destinationAsset assetId used for the action on the destination chain

    • originChain assetId deposited into the deposit account

    • slippageTolerance value is basis points, so 100 is 1%

  • steps is used to define an operation on the destination chain

    • functionSignature function signature to be called on the EVM chain

    • parameters arguments to be passed to the function

      • Notice {DEPOSIT_ADDRESS}, which is a placeholder for the deposit account generated during quoting

    • to contact to interact with

    • value native value - in case a native token needs to be used

  • type type of the action

Example response
Field
Description

details.payload.payload_json

Message to be signed by the wallet

id

Identifier of the execution, needed for tracking

status

Status of the transaction, used for understanding the lifecycle of the execution

steps

Updated steps were built based on the user's signed input steps. The additional transfer added to the array is used to reimburse the gas fee

3

Submit the digest

Use Submit digest to submit the signed message. This will allow executing batched transactions on the destination chain.

const response = await fetch(`https://intents-connect-alpha-api.aurora.dev/api/v1/executions/${solanaWalletAccount}/submit`, {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    "executionId": "74e0cbfe-def3-47fb-8f1c-469778c6acbc",
    "publicKey": "ed25519:BTKcXNp1wSzs9Mp2ejsPrHLr59z5UkEDJgqcWyXGhGc4",
    "signature": "ed25519:466cjq2diW62zHhHik8hQQGLjLTg2drnZCEjBxDnUDZCoN4HmcXv4F4WTe2LqDgJk8Ccaq1rjusA47DeUWKegNy1"
  })
});
const execution = await response.json();
Request data explanation

  • executionId ID of the execution

  • publicKey public key of the wallet

  • signature signed message signature

Example response
{
  "result": {
    "status": "SIGNING"
  }
}
4

Monitor the status of the execution

Use Fetch executions using id of the execution

const response = await fetch(`https://intents-connect-alpha-api.aurora.dev/api/v1/executions/BTKcXNp1wSzs9Mp2ejsPrHLr59z5UkEDJgqcWyXGhGc4?id=74e0cbfe-def3-47fb-8f1c-469778c6acbc`);
const execution = await response.json();
Response explanation

The response will contain the entire execution object, but look out for status the field that indicates the lifecycle of the execution. SUCCESS means the execution is fully processed.

PreviousDeposit into Aave from Solana
NextDeveloper Guides

Last updated