Skip to main content
POST
Synchronous endpoint Forward an unsigned TronWeb transaction without converting it to the flattened transaction format.
Use EVM / TRON Flattened when your wallet already has the common chain_id, from, to, value, and data shape.

Quick Start

Request Examples

Request Fields

string
required
Your HashDit API key. Missing or invalid keys return HTTP 401. Keep the key on a trusted server.
string
Full URL of the dApp that initiated the transaction. Alias: dappUrl.
object[]
required
Exactly one unsigned transaction returned by tronWeb.transactionBuilder.*. Send it unchanged. Alias: tronTransactions.
boolean
default:"true"
Keep true for the fullest assessment. Set to false only for a verdict without execution-dependent signals.

Response Fields

string
required
API result code. "0" indicates success; non-zero values indicate an error.
string
required
Request status. A successful completed response returns "ok".
integer
required
Risk score from 0 to 5; higher values indicate greater risk.
string
required
Human-readable risk level corresponding to overall_score.
Signing-flow decision: ALLOW, WARN, or BLOCK.
object[]
Triggered findings.

How to Use the Response

Use recommended_action as the signing decision. Show every risk_details[].description for WARN and BLOCK, and use each finding’s name for application logic.

Risk Level Reference

TRON payload rules

  • Send the unsigned object returned by tronWeb.transactionBuilder.*; do not rebuild protocol payloads.
  • Addresses may use the 21-byte hex or Base58 representation emitted by TronWeb.
  • Numeric values inside tron_transactions are decimal only. A 0x-prefixed amount is rejected.
  • txID, visible, and raw_data_hex may be forwarded unchanged.

Errors and Retry Guidance