Skip to main content
POST
/
yield
/
broadcast
curl --request POST \
  --url https://api.starkfi.io/yield/broadcast \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api_key>' \
  --data '{
    "chain_name": "solana",
    "op_signed": "AQAAAAA..."
  }'

{
  "statusCode": 200,
  "success": true,
  "status": "broadcast_operation_yield_strategy_ok",
  "message": "Yield operation broadcasted successfully",
  "data": {
    "status": 1,
    "transactionHash": "5VERv8NMvzbJME..."
  }
}
Optional for Yield Aggregator — you may broadcast signed transactions with your own RPC instead. StarkPay POST /payment/execute/on-chain remains required for payment flows.
​
x-api-key
string
required
Your StarkFi API key.
​
chain_name
string
required
Enabled chain where the operation was built, e.g. solana.
​
op_signed
string | string[]
required
Base64 signed Solana wire. One string for deposit, withdraw, or a merged rebalance. Up to two strings in an array for dual-transaction rebalance.
curl --request POST \
  --url https://api.starkfi.io/yield/broadcast \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api_key>' \
  --data '{
    "chain_name": "solana",
    "op_signed": "AQAAAAA..."
  }'

{
  "statusCode": 200,
  "success": true,
  "status": "broadcast_operation_yield_strategy_ok",
  "message": "Yield operation broadcasted successfully",
  "data": {
    "status": 1,
    "transactionHash": "5VERv8NMvzbJME..."
  }
}

​
Response

​
data.status
number
Confirmation status from the relay (1 when successful on Solana).
​
data.transactionHash
string
On-chain signature when available.