API

Automation

Pricing

About us

API

Blog

Start now

REST · JSON · API v1

TRON Energy rental API

Tron energy
rental API

Delegate Energy and Bandwidth to any number of TRON wallets from your backend. One API key, a simple REST interface, and no TRX locked in staking — so USDT withdrawals, sweeps, and payouts stop burning your balance.

Get API key

API documentation

65,000 – 2,000,000 Energy per order

1h · 1d · 3d · 7d

OpenAPI 3.0.3

curl https://api.tronex.energy/api/v1/buyenergy \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'X-API-KEY: YOUR_API_KEY' \
  --data '{
    "days": "1h",
    "volume": 65000,
    "target": "TVVX6svz6vXGVACeH9jNMk5M3dH5SvcT71"
  }'

POST /api/v1/buyenergy · rents 65,000 Energy for 1 hour to one address

curl https://api.tronex.energy/api/v1/buyenergy \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'X-API-KEY: YOUR_API_KEY' \
  --data '{
    "days": "1h",
    "volume": 65000,
    "target": "TVVX6svz6vXGVACeH9jNMk5M3dH5SvcT71"
  }'

POST /api/v1/buyenergy · rents 65,000 Energy for 1 hour to one address

What the TRON Energy API does

Everything you need to supply TRON resources to your own addresses, without running a staking operation.

Rent Energy on demand

Order from 65,000 to 2,000,000 Energy per request for 1 hour, 1 day, 3 days, or 7 days. Enough to turn USDT transfers from a burn into a fixed, known cost.

Rent Bandwidth

Cover Bandwidth separately when a wallet sends more transfers than its free daily allowance can handle.

Activate new addresses

Resources can’t be delegated to an inactive wallet. Activate fresh deposit addresses on TRON mainnet with one call.

Know what each address needs

Send up to 10 addresses and get back the Energy each one needs for a USDT transfer: about 65,000 if it already holds USDT, about 131,000 if it doesn’t.

Quote before you buy

Get the price of any volume and term before committing funds, so your system can decide per order whether renting beats burning.

Track every order on-chain

Each order returns an ID and a transaction hash, so you can confirm the delegation on Tronscan or against your own node.

How it works

A typical exchange or payment setup: customers pay into deposit addresses, and funds are swept to a main wallet. Every sweep is a USDT transfer that needs Energy.

Deposit wallet

receives delegated Energy in seconds

Tronex API

buyenergy for the deposit address

Your system

detects a deposit to sweep

Main wallet

receives USDT with no TRX burned

Deposit wallet

receives delegated Energy in seconds

Tronex API

buyenergy for the deposit address

Your system

detects a deposit to sweep

Main wallet

receives USDT with no TRX burned

Deposit wallet

receives delegated Energy in seconds

Tronex API

buyenergy for the deposit address

Your system

detects a deposit to sweep

Main wallet

receives USDT with no TRX burned

Works the same for payout wallets, merchant settlements, and any address that sends TRC-20 transfers. No limit on the number of addresses.

API endpoints

Nine endpoints cover the full cycle: fund the account, estimate, buy, and confirm. All requests go to https://api.tronex.energy.

Method

Endpoint

What it does

Get balance

GET /api/v1/balance

Current balance of your account

Get refill address

GET /api/v1/refill

Address for topping up your balance

Get energy price

POST /api/v1/precountOrder

Price for a given Energy volume and term

Buy energy

POST /api/v1/buyenergy

Creates an Energy order for a target address

Get energy needed

POST /api/v1/cost

Energy required for up to 10 addresses

Get bandwidth price

POST /api/v1/precountBandwidth

Price for a given Bandwidth volume and term

Buy bandwidth

POST /api/v1/buybandwidth

Creates a Bandwidth order for a target address

Activate address

POST /api/v1/activate

Activates an address on TRON mainnet

Get order status

GET /api/v1/status/{id}

Status and transaction hash of an order

Check what an address needs, then buy

Tron energy
rental API

The Energy a USDT transfer needs depends on the recipient. If it already holds USDT, about 65,000 is enough. If it has never held USDT, the contract creates a new balance record and the transfer needs about twice as much.

Instead of guessing, send the addresses to /api/v1/cost and order exactly what each one needs. For every order, /api/v1/buyenergy returns the order ID, status, and the transaction hash of the delegation.

The API doesn’t send webhook callbacks, so integrations poll /api/v1/status/{id} until the order is filled. Delegation normally lands within seconds, so a short polling interval is enough.

{
  "data": [
    { "address": "TVVX6svz6vXGVACeH9jNMk5M3dH5SvcT71", "need_energy": 65000 },
    { "address": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t", "need_energy": 130000 }
  ]
}

{
  "data": [
    { "address": "TVVX6svz6vXGVACeH9jNMk5M3dH5SvcT71", "need_energy": 65000 },
    { "address": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t", "need_energy": 130000 }
  ]
}

{
  "days": "1h",
  "volume": 65000,
  "price": …,
  "summa": …,
  "target": "TVVX6svz6vXGVACeH9jNMk5M3dH5SvcT71",
  "order_id": 123456,
  "status": "Pending",
  "txid": "8a2b3c4d5e6f…"
}

price and summa depend on the current rate — use precountOrder to get them before ordering

{
  "days": "1h",
  "volume": 65000,
  "price": …,
  "summa": …,
  "target": "TVVX6svz6vXGVACeH9jNMk5M3dH5SvcT71",
  "order_id": 123456,
  "status": "Pending",
  "txid": "8a2b3c4d5e6f…"
}

price and summa depend on the current rate — use precountOrder to get them before ordering

Resources, terms, and limits

Energy and Bandwidth are ordered through separate endpoints, each with its own volume range and terms. Knowing them upfront saves a round of 400 responses during integration.

Resource

Endpoints

Min per order

Max per order

Terms

Energy

buyenergy

65,000

2,000,000

1h · 1d · 3d · 7d

Bandwidth

buybandwidth

1,000

30,000

1h · 1d

65,000 Energy covers one USDT transfer to an address that already holds USDT; about 131,000 is needed for an address that doesn’t.
Resources can’t be delegated to an inactive wallet — call /api/v1/activate on new addresses before the first order.

Request rate limits

Request type

Limit per account

When exceeded

GET

100 requests / 20 seconds

HTTP 429 Too Many Requests

Address activation

40 requests / 20 seconds

HTTP 429 Too Many Requests

For high-volume flows, batch the /cost check (up to 10 addresses per call) and poll order status with a short backoff instead of a tight loop.

Authentication and security

Tron energy
rental API

Every request carries your key in the X-API-KEY header. There’s no OAuth handshake, no session, and no expiring token to refresh.

For an extra layer of protection, you can ask support to enable HMAC request signing on your account. Each request then also carries X-TIMESTAMP and an HMAC-SHA256 X-SIGNATURE of the method, path, timestamp, and body. Requests outside a ±30-second window are rejected, which limits the value of an intercepted request.

The key authorises spending from your balance, so treat it like production credentials.

Every request carries your key in the X-API-KEY header. There’s no OAuth handshake, no session, and no expiring token to refresh.

The key authorises spending from your balance, so treat it like production credentials.

The API doesn’t send webhook callbacks, so integrations poll /api/v1/status/{id} until the order is filled. Delegation normally lands within seconds, so a short polling interval is enough.

Keep the key server-side. Never in frontend code, public repositories, or shared logs.

Separate keys for staging and production, so a test script can’t spend your live balance.

Rotate credentials on a schedule and immediately after any staff or vendor change.

Enable HMAC signing if your key passes through infrastructure you don’t fully control.

Watch for a rise in 401 responses — it often signals a leaked or stale key.

Response codes

Standard HTTP status codes, each with a clear meaning for your error handling.

200

Success

The request was processed.

400

Bad request

Malformed body, or a volume or term outside the allowed range.

Seamless API integration for user transit wallet management

401

Unauthorized

Missing or invalid API key, or an invalid HMAC signature.

402

Insufficient balance

Top up your account using the refill address.

404

Not found

Unknown order ID in a status request.

429

Too many requests

Rate limit reached. Wait and retry with backoff.

Who uses the Energy API

Any system that sends USDT TRC-20 from many addresses, or many times a day.

Exchanges

Energy for deposit sweeps and customer withdrawals, ordered per address as funds arrive.

Payment gateways

A fixed cost per merchant settlement instead of a TRX burn that moves with the token price.

Payout systems

Resources for mass payouts from hot wallets, sized to each day’s volume.

Wallets and apps

Cover transfer costs for users so they don’t need to hold TRX to send USDT.

OTC and treasury desks

Predictable transfer costs for large, irregular movements between wallets.

dApps and bots

Energy for contract calls from service wallets that run around the clock.

Need Energy kept topped up without writing the ordering logic yourself? See automation modes.

Quickstart: first order in four steps

No SDK needed — any HTTP client that can set a header and send JSON is enough.

Get an API key

Request it in the Telegram bot or from the team. It’s linked to your account balance.

Get an API key

Request it in the Telegram bot or from the team. It’s linked to your account balance.

Top up

Call GET /api/v1/refill and send funds to the address it returns.

Top up

Call GET /api/v1/refill and send funds to the address it returns.

Estimate

Call POST /api/v1/precountOrder with the volume and term to see the price.

Estimate

Call POST /api/v1/precountOrder with the volume and term to see the price.

Buy and track

Place the order with POST /api/v1/buyenergy and poll the status until delegation is confirmed.

Buy and track

Place the order with POST /api/v1/buyenergy and poll the status until delegation is confirmed.

The documentation is built on an OpenAPI 3.0.3 specification, downloadable as JSON or YAML, with request samples for cURL, Node.js, Python, PHP, and Ruby.

Reliability and support

Built for flows where a failed transfer costs more than the fee.

Live status

Service availability and incident history are public at status.tronxenergy.com.

Verifiable delivery

Every order returns a transaction hash, so delegation can be confirmed on-chain rather than taken on trust.

People, not just an endpoint

Our team helps with integration and stays reachable when something operational needs attention.

API pricing

You pay per order from your account balance — no subscription and no setup fee. Rates drop with volume, and you can always get the exact price of an order before placing it with precountOrder.

See rates and volume tiers

API pricing

You pay per order from your account balance — no subscription and no setup fee. Rates drop with volume, and you can always get the exact price of an order before placing it with precountOrder.

See rates and volume tiers