TRON Energy Smart Leasing

OnlinePublic Project

Provide TRON Energy Smart Leasing API, which automatically calculates the energy that needs to be purchased according to the status of the transaction wallet.

Contact Service Provider

Email [email protected]

Telegram idatariver

This project is provided by the platform. If you have any questions about this project, please contact us.

API Calls

Basic usage

  • All API need to pass apikey in the query string parameter for authentication. [apikey]
  • All API return json format. Regardless of whether the request is successful or not, the response status is 200.
  • Please judge whether it is successful based on the code field. For details, please refer to the explanation below.
  • It is recommended to determine whether retry is needed based on the code and cost fields. When cost=true, please do not repeat the request.
  • The timeout should be greater than 60 seconds to avoid deductions caused by early termination of the request.

Top-level field explanation

NameDescription
code(Required) Return code. The return result is determined based on this field. See the table below for detailed meaning.
credits(Required) Consumed credits in this call.
result(Optional) The complete original return result, field structure and explanation should be provided by the supplier.
msg(Optional) Reason for request failure.
tip(Optional) Other prompt information.

Return code explanation (Integer)

codeDescriptionRemark
0The request is correct without any errors
1000Internal errorNormally you can just retry
1001Parameter errorPlease modify the parameters and retry
1002The requested resource does not exist and may be deleted.In this case, please do not retry
1003Internal processing is busy, please retry laterGenerally, the internal request resources are temporarily insufficient or the API is temporarily unavailable. Take a rest and try again.
1004Insufficient permissionsPlease contact the administrator to activate permissions
1005Insufficient balancePlease recharge

APIsOnly display online Endpoints

Intelligently buy TRON energy Pay as you go
GEThttps://apiok.us/api/e971/energy/new/v1

2024-07-12 03:00 ~ 04:00

Insufficient data for statistics

2024-07-12 04:00 ~ 05:00

Insufficient data for statistics

2024-07-12 05:00 ~ 06:00

Success Rate: 100.00%

Avg response time: 1519ms

2024-07-12 06:00 ~ 07:00

Insufficient data for statistics

2024-07-12 07:00 ~ 08:00

Insufficient data for statistics

2024-07-12 08:00 ~ 09:00

Insufficient data for statistics

2024-07-12 09:00 ~ 10:00

Insufficient data for statistics

2024-07-12 10:00 ~ 11:00

Insufficient data for statistics

2024-07-12 11:00 ~ 12:00

Insufficient data for statistics

2024-07-12 12:00 ~ 13:00

Insufficient data for statistics

2024-07-12 13:00 ~ 14:00

Insufficient data for statistics

2024-07-12 14:00 ~ 15:00

Insufficient data for statistics

2024-07-12 15:00 ~ 16:00

Insufficient data for statistics

2024-07-12 16:00 ~ 17:00

Insufficient data for statistics

2024-07-12 17:00 ~ 18:00

Insufficient data for statistics

2024-07-12 18:00 ~ 19:00

Insufficient data for statistics

2024-07-12 19:00 ~ 20:00

Insufficient data for statistics

2024-07-12 20:00 ~ 21:00

Insufficient data for statistics

2024-07-12 21:00 ~ 22:00

Insufficient data for statistics

2024-07-12 22:00 ~ 23:00

Insufficient data for statistics

2024-07-12 23:00 ~ 00:00

Insufficient data for statistics

2024-07-13 00:00 ~ 01:00

Insufficient data for statistics

2024-07-13 01:00 ~ 02:00

Insufficient data for statistics

2024-07-13 02:00 ~ 03:00

Insufficient data for statistics

2024-07-13 03:00 ~ 04:00

Insufficient data for statistics

2024-07-13 04:00 ~ 05:00

Insufficient data for statistics

2024-07-13 05:00 ~ 06:00

Insufficient data for statistics

2024-07-13 06:00 ~ 07:00

Insufficient data for statistics

2024-07-13 07:00 ~ 08:00

Insufficient data for statistics

2024-07-13 08:00 ~ 09:00

Insufficient data for statistics

2024-07-13 09:00 ~ 10:00

Insufficient data for statistics

2024-07-13 10:00 ~ 11:00

Insufficient data for statistics

2024-07-13 11:00 ~ 12:00

Insufficient data for statistics

2024-07-13 12:00 ~ 13:00

Insufficient data for statistics

2024-07-13 13:00 ~ 14:00

Insufficient data for statistics

2024-07-13 14:00 ~ 15:00

Insufficient data for statistics

2024-07-13 15:00 ~ 16:00

Insufficient data for statistics

2024-07-13 16:00 ~ 17:00

Insufficient data for statistics

2024-07-13 17:00 ~ 18:00

Insufficient data for statistics

2024-07-13 18:00 ~ 19:00

Insufficient data for statistics

2024-07-13 19:00 ~ 20:00

Insufficient data for statistics

2024-07-13 20:00 ~ 21:00

Insufficient data for statistics

2024-07-13 21:00 ~ 22:00

Insufficient data for statistics

2024-07-13 22:00 ~ 23:00

Insufficient data for statistics

2024-07-13 23:00 ~ 00:00

Insufficient data for statistics

2024-07-14 00:00 ~ 01:00

Insufficient data for statistics

2024-07-14 01:00 ~ 02:00

Insufficient data for statistics

2024-07-14 02:00 ~ 03:00

Insufficient data for statistics

2024-07-14 03:00 ~ 04:00

Insufficient data for statistics

2024-07-14 04:00 ~ 05:00

Insufficient data for statistics

2024-07-14 05:00 ~ 06:00

Insufficient data for statistics

2024-07-14 06:00 ~ 07:00

Insufficient data for statistics

2024-07-14 07:00 ~ 08:00

Insufficient data for statistics

2024-07-14 08:00 ~ 09:00

Insufficient data for statistics

2024-07-14 09:00 ~ 10:00

Insufficient data for statistics

2024-07-14 10:00 ~ 11:00

Insufficient data for statistics

2024-07-14 11:00 ~ 12:00

Insufficient data for statistics

2024-07-14 12:00 ~ 13:00

Insufficient data for statistics

2024-07-14 13:00 ~ 14:00

Insufficient data for statistics

2024-07-14 14:00 ~ 15:00

Insufficient data for statistics

2024-07-14 15:00 ~ 16:00

Insufficient data for statistics

2024-07-14 16:00 ~ 17:00

Insufficient data for statistics

2024-07-14 17:00 ~ 18:00

Insufficient data for statistics

2024-07-14 18:00 ~ 19:00

Insufficient data for statistics

2024-07-14 19:00 ~ 20:00

Insufficient data for statistics

2024-07-14 20:00 ~ 21:00

Insufficient data for statistics

2024-07-14 21:00 ~ 22:00

Insufficient data for statistics

2024-07-14 22:00 ~ 23:00

Insufficient data for statistics

2024-07-14 23:00 ~ 00:00

Insufficient data for statistics

2024-07-15 00:00 ~ 01:00

Insufficient data for statistics

2024-07-15 01:00 ~ 02:00

Insufficient data for statistics

2024-07-15 02:00 ~ 03:00

Insufficient data for statistics

3 days ago100.00% uptime(avg 1519ms)now
Public APItimeout=60s qps/1 qpm/unlimit
The required energy is automatically calculated based on the wallet addresses of both parties to the transfer and sent to the 'from_addr' address. Since the transfer energy is dynamically calculated according to the actual situation, the amount of energy transferred has the following values: 👉0: When the mode is 1 and there is sufficient energy in the 'from_addr' wallet, the energy conversion operation will not be performed, and no fee will be deducted at this time. 👉32000: When 'to_addr' has USDT, this amount of energy will be transferred to 'from_addr', and the fee will be 3TRX, which is about 0.4 points on this platform. 👉65000: When 'to_addr' does not have USDT, this amount of energy will be transferred to 'from_addr', and the fee will be 6TRX, which is about 0.8 points on this platform. 🔔 Before calling this interface, please make sure that the 'from_addr' wallet is activated, otherwise it will not be able to send energy. 🔑 There are two types of values: 1 and 2. 👉 When passing 1, it means that the energy required for a transfer is calculated according to 'from_addr' and 'to_addr' at the same time, that is, the remaining energy of 'from_addr' will be calculated first, and if the energy is enough, the purchase will be canceled, and no fee will be deducted for this operation, which is suitable for using this mode in serial transfer. 👉 When passing 2, the energy required for one transfer is calculated only according to the 'to_addr', and does not care about the current energy of the 'from_addr', which is suitable for use in the scenario of 'from_addr' concurrent transfer.
Pricing Dynamic calculation
Query Params
NametypeRequiredDefault ValueExampleDescription
apikeystringtrueidr_***Copy apikey from Console
from_addrstringtrueTBWgTTf15qquuDVsaBkVn141wSN1hSAJhR转账钱包地址, 用户需要从此钱包转出USDT
to_addrstringtrueTMG5LWah8Ng1HmBEpzvkF2iRAL9Cuw3fui收款钱包地址, 用户需要将USDT转到此钱包
modenumbertrue1智能模式, 可传1或者2, 模式1会考虑当前已有的能量, 模式2不会考虑当前已有能量