Send a Mass Payout
Paying many recipients one transaction at a time is slow and error-prone. This guide sends a single batched payout that fans out to a list of recipients. Simulate the batch first so a fee or energy shortfall does not strand part of the run.
- A funded source with enough balance plus fees for the batch.
- An API key with C2 access for the payouts endpoint.
1Assemble the recipient list
Build an items array of destination addresses and amounts. Amounts are in the chain's smallest unit.
curl -X POST https://api.1st-node.com/v1/payouts \
-H "Authorization: Bearer sk_live_..." \
-d '{"chain":"tron","items":[
{"to":"TR8h2...","amount":"1000000"},
{"to":"TQ9k4...","amount":"2500000"}]}'
> {"payout_id":"po_4a1c","count":2,"status":"pending"}2Confirm the fee and energy budget
On TRON each TRC-20 leg needs energy. Rent or delegate energy to the sender so the whole batch clears, then let the payout proceed.
curl -X POST https://api.1st-node.com/v1/tron/energy/rent \
-H "Authorization: Bearer sk_live_..." \
-d '{"receiver":"TTreas...","amount":64000}'
> {"status":"active","energy":64000}3Track the batch to completion
Poll the payout_id or subscribe to your webhook. Each item reports its own hash and status so you can retry only the failed legs.
常见问题
What happens if one recipient fails?
Each item settles independently and reports its own status and hash. Retry only the failed legs rather than resending the whole batch.
Why do TRON payouts need energy?
TRC-20 (USDT) transfers consume energy. Staking, delegating or renting energy to the sender cuts the per-transfer cost across the batch.
继续阅读
充值、拿密钥、上线。
自助开通。支持加密货币或银行卡。按额度计费——重型原语更贵，简单调用很便宜。
获取 API 密钥