Build, sign and broadcast a transaction
Sending value reliably means more than one call: build the transaction, preview the outcome, then sign and broadcast. Each step is its own primitive so you keep full control over keys and timing.
- A live API key
- A funded source address and a destination
1Build the transaction
Ask the build endpoint for a ready-to-sign payload given source, destination and amount. On TRON you can attach an energy estimate so fees are predictable.
curl https://api.1st-node.com/v1/tx/tron/build \
-H "Authorization: Bearer sk_live_..." \
-d '{"from":"T...","to":"T...","amount":"1000000"}'2Simulate before sending
Run the built transaction through simulate to preview balance changes and catch reverts or insufficient-fee errors before anything is broadcast.
curl https://api.1st-node.com/v1/tx/tron/simulate \
-H "Authorization: Bearer sk_live_..." -d '{ "raw": "0a..." }'3Sign and broadcast
Sign locally or via the signing primitive, then broadcast. The response returns the transaction hash you track to confirmation.
Частые вопросы
Do you hold my keys?
Build, simulate and broadcast are non-custodial primitives — you decide where signing happens. Custodial signing is a separate primitive you opt into.
Why simulate first?
Simulation surfaces reverts, slippage and fee shortfalls before you spend a real transaction, which is cheaper than a failed broadcast.
Читать дальше
Пополнили, получили ключ, запустили.
Полное самообслуживание. Оплата криптой или картой. Тарификация в кредитах — тяжёлые примитивы дороже, простые дёшевы.
Получить API-ключ