Skip to main content
When you no longer need the ENERGY or BANDWIDTH resources provided by staked TRX — or when you want to reallocate your TRX — use this endpoint to initiate the unstaking process. After submitting an unstake request, the TRX enters a cooldown period defined by the Tron protocol. During this time the resources are released but the TRX is not yet available for transfers. Once the cooldown completes, use the Release Unstaked TRX endpoint to return the funds to your available balance.

​
Request

Method: POST
URL: https://api.finrock.io/dav/v1/unstake

​
Body Parameters

​
string
default:"TRX"
required
The blockchain ticker. Must be TRX.
​
string
required
The Tron address from which you want to unstake TRX. This must be the address where you previously staked via the Stake TRX endpoint.
​
string
default:"ENERGY"
required
The resource type associated with the TRX you want to unstake. Must match what was staked:
  • ENERGY — unstake TRX that was staked for ENERGY
  • BANDWIDTH — unstake TRX that was staked for BANDWIDTH
​
number
default:"100"
required
The amount of TRX to unstake, expressed as a decimal number. Must not exceed the amount currently staked for the specified resource on this address.

​
Headers

​
string
required
Your Finrock API key.
​
string
required
Your JWT bearer token. Format: Token {JWT}

​
Example Request

​
Response

A 200 response confirms the unstaking has been initiated and the TRX is now in the cooldown period. A 400 response indicates that the unstaking cannot proceed, typically because the amount exceeds what is staked or the address is invalid.
​
object
Confirms the unstaking request has been submitted. Includes details of the cooldown period after which the TRX can be released.
​
object
Returned when the address is invalid, the resource type does not match what is staked, or the unstake amount exceeds the staked balance.
During the Tron cooldown period, the unstaked TRX is neither available for transfer nor earning resources. Plan your unstaking operations in advance to avoid gaps in resource coverage for high-volume addresses.