Extend an existing TronSave order (v2) in two steps — fetch extendable delegates, then submit an extend request paid by API key or signed transaction.
The v2 extend endpoints let you prolong an order you already hold instead of placing a new one. Version 2 adds two improvements over earlier extend support:
Extension via signed transactions, not just an API key.
A new resource type: Bandwidth (in addition to Energy).
Extending is a two-step flow: first read which delegates on an order can be extended, then submit an extend request for the ones you want.
Query an order to find out which delegations can still be extended and for how long. Use the result to build the payload for step 2.
Send the extend request for the chosen delegates. Two payment methods are supported:
Option 1 — Extend using an API key: authorize the extension with a TronSave API key on a prefunded internal account; no per-order on-chain signing.
Option 2 — Extend using a signed transaction: sign the extension with your own private key and settle it on-chain.
The extend flow uses two POST endpoints:
Get extendable delegates
POST
/v2/get-extendable-delegates
Submit extend request
POST
/v2/extend-request
A Postman collection for the extend flow is available at postman.com/tronsave/tronsave.
Use the development host to test against the Nile Testnet:
Get extendable delegates: POST https://api-dev.tronsave.io/v2/get-extendable-delegates
Submit extend request: POST https://api-dev.tronsave.io/v2/extend-request
To integrate with the Nile Testnet from the website, replace the host with https://testnet.tronsave.io/ and follow the same steps as the Get API Key guide.
Get extendable delegates — start the flow.
Set up Authentication before calling the API.
Review Energy and Bandwidth and Order Types.
Last updated
