POST Register
/api/v1/register
This endpoint registers a new Transfer Edge account by accepting a signed (but not yet broadcasted) deposit transaction in TRX or USDT. Upon successful processing, the system creates a new account with the provided email, credits the deposited balance, and returns API keys along with account details.
The transaction must not be broadcasted on-chain before calling this endpoint. If the transaction is already on-chain, the request will be rejected.
Parameters/Body
{
"transaction": "<signed transaction object>",
"email": "user@example.com"
}
transaction: a signed TRX or USDT transaction object (not yet broadcasted).- The
toaddress must match the Transfer Edge payment address (TFPzL92nmSxLVVNHoL5cbZ6tjSxfuKUBeD). - The transaction amount must meet the minimum deposit threshold for the respective token (TRX or USDT).
- TRX transactions are sent on-chain instantly via TronNode. USDT transactions are processed via Transatron using a system API key.
- The
email: email address for the new account. A verification email is sent, but the account is activated immediately and fully operational before email verification. Email can be verified later via the link in the verification email.
An unverified email does not prevent the account from operating. All API keys and transaction processing work normally. However, the /api/v1/config endpoint will include a notice array with a reminder to verify the email.
Minimum deposit amounts follow the same thresholds as standard TRX/USDT deposits.
Validation Rules
The endpoint performs the following checks before processing:
- Not on-chain — the transaction hash is checked via
getTransactionInfo. If the transaction already exists on TRON, an error is returned. - Correct recipient — the
toaddress must equal the configured Transfer Edge payment address. If not, an error is returned. - Minimum amount — the deposit amount must meet or exceed the minimum for TRX or USDT deposits. If below the minimum, an error is returned.
Flow
- The signed deposit transaction is validated and broadcasted on-chain.
- The deposited amount is initially credited to the sender address of the transaction.
- If the transaction fails (e.g. invalid signature), an error is returned.
- On successful processing:
- A new account is created for the provided email address, with an assigned internal deposit address.
- A random temporary password is generated.
- The deposited balance is credited to the new account:
- A balance entry is created with type
DEPOSITand statusCOMPLETED. - The TFN (former RTRX) or TFU (former RUSDT) balance is credited to the account's internal deposit address.
- The sender address balance is set to zero.
- A balance entry is created with type
Response contains the following data:
deposit_address: the TRON deposit address for future top-ups.activation_price: account activation fee.energy_price_per_unit: energy resource price.bandwidth_price_per_unit: bandwidth resource price.balance_rtrx: current TFN (former RTRX) balance.balance_usdt: current TFU (former RUSDT) balance.spender_api_key: auto-generated Spender API key (allows spending operations).non_spender_api_key: auto-generated Non-Spender API key (read-only operations).password: the generated account password.
Store the API keys and password securely — they are only returned once during registration.
Example of response:
{
"activation_price": 1230000,
"balance_rtrx": 5000000,
"balance_usdt": 0,
"bandwidth_price_per_unit": 1000,
"deposit_address": "TXr4B8dNfEn7K2pGLkvsq9WBcKR1F8mHa6",
"energy_price_per_unit": 35,
"non_spender_api_key": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"password": "tmp_Xk9mP2vL",
"spender_api_key": "12345678-abcd-ef01-2345-6789abcdef01"
}