API Send Transactions — Broadcast Signed Tron Payloads

Tronfuel offers an endpoint to send signed Tron transactions while automatically managing energy and bandwidth allocation. This allows your transactions to execute reliably — even if your wallet has insufficient resources.

---

#✅ What You Need

Before calling this endpoint, ensure you have:

• A valid signed transaction object (see How to Sign Transactions)
• An active Tronfuel account with sufficient balance
• API key and authorization headers configured
• X-Network header set to either mainnet or nile

---

#⚙️ How It Works

When you send a signed transaction to our API:

1. Tronfuel receives your signed transaction.
2. The platform analyzes the transaction to determine energy and bandwidth requirements.
3. If needed, it delegates resources to the sender address.
4. The transaction is broadcasted to the Tron blockchain.
5. Confirmation and error status are monitored.
6. Webhooks are triggered based on success, failure, or timeout.
7. Associated resource fees are deducted from your internal Tronfuel wallet.

---

#📡 Example Request

Endpoint:

 1POST /transactions/build
 2Host: tronfuel.dev
 3Authorization: Bearer YOUR_API_KEY
 4Content-Type: application/json
 5{
 6  "visible": false,
 7  "txID": "b6ed04b2fa51668922bc4152190b26e95e8174d86eef7801d63be3da1a7a729c",
 8  "raw_data": {
 9    "contract": [
10      {
11        "parameter": {
12          "value": {
13            "data": "a9059cbb000000000000000000000000aef434d3b649333ede3f64456d0ca67d83f871a700000000000000000000000000000000000000000000000000000000000f4240",
14            "owner_address": "4177bafb1379d3b8f85404c8bfa243c4416dcf2092",
15            "contract_address": "41eca9bc828a3005b9a3b909f2cc5c2a54794de05f"
16          },
17          "type_url": "type.googleapis.com/protocol.TriggerSmartContract"
18        },
19        "type": "TriggerSmartContract"
20      }
21    ],
22    "ref_block_bytes": "7f32",
23    "ref_block_hash": "bd5f66a94fdb1076",
24    "expiration": 1751275206000,
25    "fee_limit": 15000000000,
26    "timestamp": 1751275148383
27  },
28  "raw_data_hex": "0a027f322208bd5f66a94fdb107640f0ea8b81fc325aae01081f12a9010a31747970652e676f6f676c65617069732e636f6d2f70726f746f636f6c2e54726967676572536d617274436f6e747261637412740a154177bafb1379d3b8f85404c8bfa243c4416dcf2092121541eca9bc828a3005b9a3b909f2cc5c2a54794de05f2244a9059cbb000000000000000000000000aef434d3b649333ede3f64456d0ca67d83f871a700000000000000000000000000000000000000000000000000000000000f424070dfa88881fc32900180acc7f037",
29  "signature": [
30    "6e9de05c130f5fcca290fe07e00218a23359faae5255228a86e48e72afa6a7e1f7305bda9b16ba3fbd95811abeff89f627875380ec8c4f026d932852a3529a3400"
31  ]
32}

#⚠️ Important

⏱ Make sure your transaction expiration field is at least 60 seconds in the future when you submit it. Transactions with an already-expired deadline will be rejected immediately.

#🔁 Response

The response contains either:

• The internal transaction ID and tron txid with a queued status
• Or an immediate error with details

 1{
 2  "status": 201,
 3  "ok": true,
 4  "message": "Transaction created successfully",
 5  "data": {
 6    "id": "0198421c-9110-7301-bdcf-b81bcf9b98f1",
 7    "txid": "b6ed04b2fa51668922bc4152190b26e95e8174d86eef7801d63be3da1a7a729c",
 8    "network": "testnet",
 9    "type": "TRC20",
10    "status": "pending",
11    "estimated_energy": 32000,
12    "estimated_bandwidth": 345,
13    "price": 4.464,
14    "created_at": "2025-07-25T15:03:45.000000Z",
15    "updated_at": "2025-07-25T15:03:45.000000Z"
16  }
17}

Need help signing transactions? Check out How to Sign Transactions.