Address Classification - HashDit API Documentation

Synchronous endpoint Classify an address as an externally owned account (EOA), token, proxy, or another supported contract type. This endpoint describes what an address is; use a security endpoint when you need a risk verdict.

HashDit-owned request fields are documented in snake_case. Equivalent camelCase input remains accepted for compatibility.

Quick Start

curl --request POST \
  --url https://service.hashdit.io/v2/hashdit/address-classify \
  --header 'Content-Type: application/json' \
  --header 'X-API-KEY: YOUR_API_KEY' \
  --data '{
    "chain_id": "56",
    "address": "0x55d398326f99059ff775485246999027b3197955",
    "strict": false
  }'

{
  "code": "0",
  "status": "ok",
  "data": {
    "address": "bsc:0x55d398326f99059ff775485246999027b3197955",
    "address_type": "Contract",
    "classification": "ERC20",
    "classification_id": 101,
    "details": {
      "is_verified": true,
      "proxy_impl_address": "",
      "proxy_impl_type": ""
    },
    "is_erc20": "1",
    "scanned_time": 1766048799,
    "status": 200,
    "timestamp": "2025-12-18T09:06:43.166765",
    "verify_status": "verified"
  }
}

Request Fields

string

required

Your HashDit API key. Missing or invalid keys return HTTP 401. Keep the key on a trusted server.

string

required

Network identifier for the address, such as "56". JSON clients may also send a numeric chain ID. See Supported Chains.

string

required

Blockchain address to classify.

boolean

default:"false"

Apply the strict latency budget. When strict processing cannot finish within that budget, the API returns a service-level timeout result instead of continuing to wait.

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".

string

Fully qualified address including the normalized chain prefix.

string

Broad address family, commonly EOA or Contract.

string

Best available classification label.

integer

HashDit classification identifier. Prefer the string label unless your integration explicitly maps IDs.

object

Verification and proxy implementation metadata.

Show Classification detail fields

boolean

Whether verified source or equivalent verification metadata was found.

string

Proxy implementation address when detected, otherwise an empty string.

string

Token or contract standard detected for the proxy implementation, otherwise an empty string.

string

"1" when the contract follows ERC-20, otherwise "0".

integer

Unix timestamp of the latest classification scan.

integer

HTTP-style status code for the classification result.

string

ISO 8601 timestamp of the latest result update.

string

Contract verification status, commonly verified or unverified.

How to Use the Response

Use address_type for the broad distinction between an EOA and a contract.
Use classification for the more specific contract category, such as ERC20 or Proxy.
For proxies, read details.proxy_impl_address and details.proxy_impl_type only when populated.
A missing, empty, or Unverified classification means the service could not make a more specific classification. It is not a safe verdict.
Classification and verification metadata are descriptive signals. Do not convert them into a risk decision without a security analysis endpoint.

Errors and Retry Guidance

HTTP or status	Meaning	Client action
`400`	Unsupported chain or invalid address	Correct the request; do not retry unchanged.
`401`	Missing or invalid API key	Fix authentication; do not retry unchanged.
`422`	Request schema validation failed	Correct field names or values.
`429`	Rate limit exceeded	Retry with exponential backoff and jitter.
`500`	Transient service failure	Retry a bounded number of times with backoff.
`status: "notok"` with strict mode	Strict latency budget was exceeded	Retry without `strict`, or handle the timeout within your product’s latency policy.

​Quick Start

​Request Fields

​Response Fields

​How to Use the Response

​Errors and Retry Guidance

Quick Start

Request Fields

Response Fields

How to Use the Response

Errors and Retry Guidance