Check Transaction Security
1. Overview & Typical Use
Performs a per-transaction risk analysis on one or more transaction hashes, identifying zero-value transfers, risky tokens, risky addresses, and same-tail address impersonation attacks.
- Typical use: batch transaction risk check, zero-value attack detection, tail-number impersonation attack identification.
- When not to use: to check account security use “Check Account Security”; for transaction details use “Get Transaction Details by Hash”.
2. Endpoint & Authentication
GET /api/security/transaction/data
For Base URL and authentication, see Common Network & Authentication.
3. Request
Fields
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
hashes | string | Yes | — | One or more transaction hashes, comma-separated |
4. Response
Fields
The response is a map keyed by transaction hash; each record contains:
| Field | Type | Required | Description | Unit/Precision |
|---|---|---|---|---|
riskToken | boolean | Required | Whether a risky token is involved | — |
zeroTransfer | boolean | Required | Whether the transfer amount is zero | — |
riskAddress | boolean | Required | Whether a risky address is involved | — |
sameTailAttach | boolean | Required | Whether this is a same-tail impersonation attack | — |
riskTransaction | boolean | Required | Whether the transaction is flagged as risky overall | — |
5. Errors
For HTTP status codes, see Common Errors. Key points for this endpoint:
- When
hashescontains invalid hashes, invalid entries are silently ignored and only valid results are returned. - When no valid hashes are provided, the response is
200+{}— this is a normal response.
Last updated on: