Transfer Packages
Move Packages
Move your transfer packages to a new TRON address
POST
Move Packages
Move Packages
Moves every active and paused package of your account on the address to a new address, with all their remaining transfers. A single package cannot be moved separately. Use it when the wallet that sends the transfers changes.- Packages that were working keep working on the new address. Paused packages stay paused there — resume them with the new address when you need them.
- The paid 24 hours keep running across the move, as across a pause. If they ran out by the time the packages start on the new address, one transfer is charged at once; otherwise nothing is.
- The move itself is free, and there is no limit on how often you move.
- If the new address is not activated on the TRON network yet, it is activated at your account’s cost, as on a purchase.
- Transfers from the old address are no longer served or counted after the response.
Request body
TRON address to move the packages to. Must differ from
address and must not be a smart contractResponse
The moved packages — the same objects as in List Packages, with
address set to the new address. status is active for packages that were working (paused_at is null) and paused for packages that were paused.Example
subscription_used and remaining are the same as before the move.
Response
Webhooks
A move of working packages pauses them on the old address, moves them, and resumes them on the new one, so each package sends three events in this order:package.pausedwith the oldaddress;package.movedwith the newaddressand the old one inprevious_address;package.resumedwith the newaddress.
package.moved. The events are sent in this order but delivered independently, so they can arrive in a different one — compare the envelope timestamp, or read the current state from List Packages.
Errors
Returned in the standard shape, underdetail.error.code.
These come before anything is changed or charged — the packages keep working on the old address:
These come from stopping delivery on the old address. Nothing was moved, and the packages keep working on the old address. If the new address was activated before the error, that activation stays charged — the address remains activated for a later move:
These come after delivery to the old address was stopped. The message says where the packages are now:
ADDRESS_BUSY and MOVE_AFTER_PAUSE can also come at this step, when another operation on the address got in between. The packages are then paused on the old address; repeat the move to carry them over — they arrive paused.