Skip to content
TRXUp
English
Telegram bot API docs
TRXUp
English
Telegram Energy Bot Buy Energy now

For business

An Energy API for teams that build on TRON

Each USDT payout your platform makes runs on TRON Energy. Wire our API into the code that sends it, and the resource gets bought per address by your backend, unattended.

API documentation Discuss an integration

Where the order fits in your code

  • Sending from an address with no TRX

    An address holds USDT and zero TRX, and it has to send. Your backend buys the resource for it a moment before broadcasting, and the transfer still goes through.

  • Sweeping many addresses into one

    Moving collected deposits into one hot wallet is a USDT transfer per deposit address. Let the collection job order Energy for each of them first.

  • Queues of outgoing transfers

    A queue of outgoing USDT transfers burns TRX on every transfer unless the address has Energy and Bandwidth. Have the payout job order the resource before each transfer, instead of someone topping the addresses up by hand.

What the API does

One POST per call, a JSON body and your signature in a header. It pays from the balance you top up in the cabinet.

  • Get Energy, Bandwidth or the two together delegated to an address of your choosing, with one call.
  • Activate an empty TRON address alone, or in the same call as the resources.
  • Ask what a transfer will need and what it will cost, then decide whether to order.
  • Read an order's state by our ID or by the external_id you sent with it: new, pending, success or failed, with the transaction hash once it succeeds.
  • Keep one address supplied with Energy for a set number of days or transfers, and stop the subscription with one call.
  • Get a risk score for a sender before your system credits the money.

How to start

  1. Open an account

    Sign up in the cabinet and fund its balance with TRX: the cost of each order is charged against it.

  2. Create API credentials

    In the API section, issue a token with its secret. Allow only your servers' IPs if you like.

  3. Send the first request

    Start from the docs: each endpoint has its parameters, a sample response and code to copy.

Big volume, custom setup?

Sketch your flow and the payouts it sends per day; a person from our team writes back.

Discuss an integration API documentation