Skip to main content
POST
Synchronous endpoint Analyze multiple transaction-history targets and token contracts in one request. Every input item carries its own chain_id, so one batch may cover more than one network.
All verdict flags are the strings "0" and "1", not booleans. Compare a flag with "1"; the string "0" is truthy in JavaScript.

Quick Start

Provide at least one user_addresses item and at least one item across target_addresses and token_addresses. The three arrays may contain at most 1000 items in total.

Request Fields

string
required
Your HashDit API key. Missing or invalid keys return HTTP 401. Keep the key on a trusted server.
object[]
required
One or more connected wallet addresses used for lookalike comparisons.
string
required
Network identifier for this user address, sent as a string in Try It. JSON clients may also send a numeric chain ID.
string
required
User address on the specified chain.
object[]
default:"[]"
Transaction-history addresses to analyze. At least one target or token item is required.
object[]
default:"[]"
Token contracts to analyze. At least one target or token item is required.
string
required
Network identifier for this target item, sent as a string in Try It. JSON clients may also send a numeric chain ID.
string
required
Target address on the specified chain.
string
required
Network identifier for this token item, sent as a string in Try It. JSON clients may also send a numeric chain ID.
string
required
Token contract on the specified chain.

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".
object[]
Target results in input order.
string
Aggregate target verdict: "1" when a signal was detected, otherwise "0".
string
"1" when the target resembles a user address in the same address family.
string
"1" when the target resembles a known exchange or bridge address.
object[]
Token results in input order.
string
"1" when the token resembles a well-known token on its chain.
object
Per-item validation error. Its presence does not invalidate successful siblings.

How to Use the Response

  • Results preserve the separate target and token groups and their input order.
  • An item with error failed validation; successful sibling items remain usable.
  • Branch on each successful item’s is_poisoning value and compare it with the string "1".
  • mimics_user, mimics_exchange, and mimics_top_token explain the detected signal.
  • "0" means no configured signal was detected. It is not a guarantee of safety.

Errors and Retry Guidance