Execute an action
Build the unsigned transactions for a Borrow action such as supply or borrow, and return them for the wallet to sign.
201 with an action whose transactions[] you sign and submit in the order returned, using Submit a transaction, then poll Get an action. Nothing executes until a signed transaction is submitted. metadata previews the health factor and LTV after the action.
args is one flat object shared by every action. Required arguments per action and integration, the amount and amountRaw rules, repayAll, and the validation errors are in Action arguments. Which integration supports which action is in Availability by integration. The Borrow API applies no geolocation block on this route.
Only borrow and repay accept a collateral amount, which adds a collateral leg to the same action; see Collateral bundling. On pool markets it also needs collateralTokenAddress:
statusCode, timestamp, path and message. Common causes of 400: an unknown or unsupported integrationId, an action the integration does not support, an argument that fails the rules above, and Lista minLoan violations. An unknown marketId returns 404. See Errors and retries.Authorizations
Body
Integration identifier
"aave-borrow"
Action to execute
supply, borrow, repay, withdraw, enableCollateral, disableCollateral, supplyAndBorrow "supply"
User wallet address
"0x742d35Cc6634C0532925a3b844Bc9e7595f8fB28"
Action arguments
Response
Action created with unsigned transactions ready for signing
Unique action identifier (UUID)
"550e8400-e29b-41d4-a716-446655440000"
Integration identifier
"aave-borrow"
Action type executed
supply, borrow, repay, withdraw, enableCollateral, disableCollateral, supplyAndBorrow "supply"
User wallet address
"0x742d35Cc6634C0532925a3b844Bc9e7595f8fB28"
Current action status
CANCELED, CREATED, WAITING_FOR_NEXT, PROCESSING, FAILED, SUCCESS, STALE "CREATED"
Transactions to sign (current step only)
Whether there are more transactions to sign after the current step completes. When true, call POST /actions/:id/step after confirming to get the next transaction(s). Used for async multi-step flows such as cross-chain bridges or delayed withdrawals.
false
Current step number (1-indexed)
1
Total number of steps in this action. Most actions are single-step. Multi-step actions occur when an async operation (e.g., bridge confirmation) must complete before the next transaction can be constructed.
1
When the action was created
Raw arguments as submitted
Action metadata with predicted position impact (health factor, LTV, USD totals)

