Addresses and quick rent
Save the addresses you rent for, each with a rent size and a term, then rent for one with a single call. These are the same saved addresses as Account → My wallets on the website.
| Call | Perm |
|---|---|
GET /v1/addresses | Read |
POST /v1/addresses | Order |
PATCH /v1/addresses/{id} | Order |
DELETE /v1/addresses/{id} | Order |
POST /v1/addresses/{id}/quick-rent | Order |
Saved address
POST /v1/addresses
{"address": "TXYZ…", "label": "hot wallet", "is_default": false,
"preset": "Smart", "custom_energy": null, "term": "1h"}preset | Rents |
|---|---|
Smart | what one USDT transfer from this address needs, checked at rent time |
65k | 65,000 energy |
131k | 131,000 energy |
Custom | custom_energy |
PATCH takes any of label, is_default, preset, custom_energy, term. A missing address
⇒ 46008 (404).
Quick rent
POST /v1/addresses/{id}/quick-rent — header Idempotency-Key: <uuid> (required, 46010
without it), body {"charge_asset": "TRX", "confirm": false} (both optional).
It checks the address, sizes the rental from the saved preset and charges your balance:
{"result": "created", "order": {"…": "an Order"}, "confirm": null}When the address already has that much energy, nothing is charged and you are asked first:
{"result": "needs_confirm", "order": null,
"confirm": {"reason": "already_has_energy", "energy": 65000, "term": "1h",
"charge_asset": "TRX", "charge_amount": "2.08", "price_trx": "2.08",
"energy_available": 70000,
"already_has_energy": {"energy": 65000, "until": "…Z"}}}Resend with "confirm": true and a new Idempotency-Key. Re-sending the same key returns the
first answer; 46011 means the first request with that key is still being processed.
Quick rent does not support test mode (45216). Orders it creates are tagged with your key, so
their webhooks fire like any other API order.