POST
/
95e61622bf6a8af293978377718e3b77
/
wallet
/
delegateresource
wallet/delegateresource
curl --request POST \
  --url https://tron-mainnet.core.chainstack.com/95e61622bf6a8af293978377718e3b77/wallet/delegateresource \
  --header 'Content-Type: application/json' \
  --data '{
  "owner_address": "41608f8da72479edc7dd921e4c30bb7e7cddbe722e",
  "receiver_address": "41e9d79cc47518930bc322d9bf7cddd260a0260a8d",
  "balance": 1000000,
  "resource": "BANDWIDTH",
  "lock": false,
  "lock_period": 0,
  "visible": false
}'
{
  "visible": true,
  "txID": "<string>",
  "raw_data": {
    "contract": [
      "<any>"
    ],
    "ref_block_bytes": "<string>",
    "ref_block_hash": "<string>",
    "expiration": 123,
    "timestamp": 123
  },
  "raw_data_hex": "<string>"
}
TRON API method that delegates resources to another account. This method allows you to delegate bandwidth or energy resources obtained from staking TRX to another address, enabling that address to use your resources for transactions.
Get you own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

  • owner_address — the address that owns the resources to delegate (hex format)
  • receiver_address — the address that will receive the delegated resources (hex format)
  • balance — the amount of TRX equivalent resources to delegate (in sun)
  • resource — the resource type to delegate (“BANDWIDTH” or “ENERGY”)
  • lock — optional boolean to lock the delegation (default: false)
  • lock_period — optional lock period in seconds (if lock is true)
  • visible — optional boolean to specify address format (default: false for hex format)

​
Response

  • visible — boolean indicating address format used
  • txID — transaction ID hash
  • raw_data — raw transaction data object containing delegation contract details
  • raw_data_hex — hexadecimal representation of raw transaction data

​
Use case

The wallet/delegateresource method is used for:
  • Sharing bandwidth or energy resources with other accounts that need them.
  • Implementing resource rental or delegation services in DApps.
  • Allowing users to sponsor transaction costs for other accounts.
  • Building resource management systems that optimize usage across multiple addresses.

Body

application/json

Response

200 - application/json

Resource delegation transaction

The response is of type object.