> For the complete documentation index, see [llms.txt](https://docs.intents.aurora.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intents.aurora.dev/intents-connect/examples/deposit-into-aave-from-solana.md). # Deposit into Aave from Solana Below is an example flow depositing into Aave using a Solana wallet using the Intents Connect API. You'll need to reference supported assets by their IDs, then run a dry execution to get the estimated output amount, and estimate costs for the destination chain action, signing the intent (deposit to Aave), and the transfer transaction to move SOL from the Solana wallet. As a result, you'll have deposited Aave into an intermediary account associated with your Solana wallet. Make sure to understand [Execution Lifecycle](/intents-connect/deep-dive/execution-lifecycle.md) before you proceed with the implementation. {% stepper %} {% step %} ### List supported tokens Use [List supported tokens](/api-reference/intents-connect-api-reference/list-supported-tokens.md) to find the `assetId` values you will need. You'll need to use the Intents API for that. {% tabs %} {% tab title="JavaScript" %} ```javascript const response = await fetch(`https://intents-connect-api.aurora.dev/api/v1/supported_tokens`); const tokens = await response.json(); ``` {% endtab %} {% endtabs %}
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` ```json [ { "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" } ] ```
{% endstep %} {% step %} ### Request an execution Use [Request an execution](/api-reference/intents-connect-api-reference/request-an-execution.md) endpoint. {% tabs %} {% tab title="JavaScript" %} ```javascript const response = await fetch(`https://intents-connect-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_supply", "title": "Supply to Aave" }, "quote": { "amount": "1270000", "destinationAsset": "nep141:base-0x833589fcd6edb6e08f4c7c32d4f71b54bda02913.omft.near", "originAsset": "nep141:sol.omft.near", "slippageTolerance": 100 }, "steps": [ { "functionSignature": "approve(address,uint256)", "parameters": [ "0xA238Dd80C259a72e81d7e4664a9801593F98d1c5", "{MIN_AMOUNT_OUT}" ], "to": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913", "value": "0" }, { "functionSignature": "supply(address,uint256,address,uint16)", "parameters": [ "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913", "{MIN_AMOUNT_OUT}", "0xFe6EF968D2F7B2e9CCCF92150d96c930C3CC4a4E", "0" ], "to": "0xA238Dd80C259a72e81d7e4664a9801593F98d1c5", "value": "0" } ], "type": "evm" }) }); const execution = await response.json(); ``` {% endtab %} {% endtabs %}
Request data explanation * `dry` is false, unless we want to get just the estimates * `metadata` contains information displayed in the UI - it's optional * `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` not used in the initial dry run * `type` type of the action * `steps` are now used, and this is how we defined an action on the destination chain * `functionSignature` [function signature](https://docs.soliditylang.org/en/latest/contracts.html#function-signatures-and-selectors-in-libraries) to be called on the EVM chain * `parameters` arguments to be passed to the function * `to` contact to interact with * `value` native value - in case a native token needs to be used
Example response | Field | Description | | ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- | | `details.payload.payload_json` | Message to be signed by the wallet | | `id` | Identifier of the execution, needed for tracking | | `quote.depositAddress` | Deposit account to which the transfer needs to be done | | `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 | ```json { "result": { "createdAt": "2026-04-28T15:21:41Z", "details": { "estimatedTime": "22", "intermediaryAddress": "0xFe6EF968D2F7B2e9CCCF92150d96c930C3CC4a4E", "messageSigned": false, "messageToSign": "...", "networkFee": "7150", "payload": { "payload_bytes_base64": "..", "payload_json": "...", "standard": "raw_ed25519" }, "serviceFee": "0", "signingStandard": "raw_ed25519" }, "id": "33ca3807-0e1b-455f-a6dd-1a482ec9b385", "metadata": { "title": "Supply to Aave (single-round)", "url": "https://last-mile-fe-check.vercel.app/actions_min_amount", "intent": "aave_supply" }, "quote": { "amount": "1270000", "amountIn": "1270000", "amountInUsd": "0.1059", "amountOut": "95300", "amountOutUsd": "0.1024", "deadline": "2026-04-28T15:31:37Z", "depositAddress": "81VBKaGXxy6chA9KjsiuLiAqiaNnsTvjRLe2DX1jYq9M", "destinationAsset": "nep141:base-0x833589fcd6edb6e08f4c7c32d4f71b54bda02913.omft.near", "minAmountOut": "94275", "originAsset": "nep141:sol.omft.near", "recipient": "0xFe6EF968D2F7B2e9CCCF92150d96c930C3CC4a4E" }, "status": "CREATED", "steps": [ { "functionSignature": "approve(address,uint256)", "parameters": [ "0xA238Dd80C259a72e81d7e4664a9801593F98d1c5", "94275" ], "to": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913", "value": "0" }, { "functionSignature": "supply(address,uint256,address,uint16)", "parameters": [ "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913", "94275", "0xFe6EF968D2F7B2e9CCCF92150d96c930C3CC4a4E", "0" ], "to": "0xA238Dd80C259a72e81d7e4664a9801593F98d1c5", "value": "0" }, { "to": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913", "functionSignature": "transfer(address,uint256)", "parameters": [ "0x546252c9a0E974f75892b4c54b7a67B69a0aFf45", "7150" ], "value": "0", "metadata": { "name": "Fee Transfer", "description": "Gas fee reimbursement" } } ], "type": "evm", "version": "1.0" } } ```
{% endstep %} {% step %} ### Sign the message `details.payload.payload_json` needs to be signed by the Solana wallet so it can be submitted in the next step. {% endstep %} {% step %} ### Submit the digest Use [Submit digest](/api-reference/intents-connect-api-reference/submit-digest.md) to submit the signed message. This will allow executing batched transactions on the destination chain. {% tabs %} {% tab title="JavaScript" %} ```javascript const response = await fetch(`https://intents-connect-api.aurora.dev/api/v1/executions/${solanaWalletAccount}/submit`, { method: 'POST', headers: { 'Content-Type': 'application/json', }, body: JSON.stringify({ "executionId": "92a10832-d36b-46c6-807d-7f28469c2a94", "publicKey": "ed25519:BTKcXNp1wSzs9Mp2ejsPrHLr59z5UkEDJgqcWyXGhGc4", "signature": "ed25519:5VUXRtVgS6bq3Wn64YdCt5NSPfA1Ni5zqiLFsSScyq6Dj53pbNEcwKcp7t1aRqw8zWCoN7coMLBUmatmwLAEvndP" }) }); const execution = await response.json(); ``` {% endtab %} {% endtabs %}
Request data explanation * `executionId` ID of the execution * `publicKey` public key of the wallet * `signature` signed message signature
Example response ```json { "result": { "status": "SIGNED_PENDING_DEPOSIT" } } ```
{% endstep %} {% step %} ### Deposit into the deposit account Now, deposit exactly `quote.amount` into `quote.depositAddress` so the swap can execute. {% endstep %} {% step %} ### Monitor the status of the execution Use [Fetch executions](/api-reference/intents-connect-api-reference/fetch-executions.md) using `id` of the execution {% tabs %} {% tab title="JavaScript" %} ```javascript const response = await fetch(`https://intents-connect-api.aurora.dev/api/v1/executions/BTKcXNp1wSzs9Mp2ejsPrHLr59z5UkEDJgqcWyXGhGc4?id=92a10832-d36b-46c6-807d-7f28469c2a94`); const execution = await response.json(); ``` {% endtab %} {% endtabs %}
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.
{% endstep %} {% endstepper %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.intents.aurora.dev/intents-connect/examples/deposit-into-aave-from-solana.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.