Address Security v2
Address Security v2
POST
/
v2
/
hashdit
/
address-security-v2
curl --request POST \
--url https://service.hashdit.io/v2/hashdit/address-security-v2 \
--header 'Content-Type: application/json' \
--header 'X-API-KEY: YOUR_API_KEY' \
--data '{
"chain_id": "56",
"address": "0x73feaa1ee314f8c655e354234017be2193c9e24e"
}'
{
"code": "0",
"status": "ok",
"data": {
"status": 200,
"address": "bsc:0x73feaa1ee314f8c655e354234017be2193c9e24e",
"address_type": "MasterChef",
"overall_score": "90",
"overall_risk_level": "No Obvious Risk",
"scanned_time": 1764270688,
"result_stage": "complete"
}
}
Asynchronous endpoint
Get an address’s overall security score and risk level across supported EVM networks, TRON, and Solana.
For polling, respect
The completed payload can contain additional chain-specific analysis. For a durable integration, rely on the decision fields documented below; auxiliary analysis objects may differ by network and result stage.
HashDit-owned request fields are documented in
snake_case. Equivalent camelCase input remains accepted for compatibility. The legacy async field pollAfter is intentionally unchanged.Quick Start
curl --request POST \
--url https://service.hashdit.io/v2/hashdit/address-security-v2 \
--header 'Content-Type: application/json' \
--header 'X-API-KEY: YOUR_API_KEY' \
--data '{
"chain_id": "56",
"address": "0x73feaa1ee314f8c655e354234017be2193c9e24e"
}'
{
"code": "0",
"status": "ok",
"data": {
"status": 200,
"address": "bsc:0x73feaa1ee314f8c655e354234017be2193c9e24e",
"address_type": "MasterChef",
"overall_score": "90",
"overall_risk_level": "No Obvious Risk",
"scanned_time": 1764270688,
"result_stage": "complete"
}
}
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. Use a numeric string for EVM networks,
"tron" / "728126428" for TRON, or "sol" / "solana" for Solana. JSON clients may also send a numeric chain ID. See Supported Chains.string
required
Address to analyze.
boolean
default:"false"
Request synchronous processing when supported. Clients must still handle the documented in-progress response.
Response Fields
string
required
"0" means the request was accepted successfully, whether processing is still in progress or complete.string
required
"in progress" means poll again; "ok" means the completed data object is available.- In Progress
- Completed
Returned on a cache miss while the address is being analyzed:
{
"code": "0",
"status": "in progress",
"pollAfter": 10
}
| Field | Type | Required | Meaning |
|---|---|---|---|
pollAfter | number | Yes | Seconds to wait before repeating the identical request. This legacy response field intentionally remains camelCase. |
Branch on
status, not only on HTTP 200. Wait pollAfter seconds before retrying; this response does not include data.Returned when analysis is complete or a cached result is available:
| Field | Type | Required | Meaning |
|---|---|---|---|
data | object | Yes | Completed address-security result. |
data.status | integer | Yes | Analysis status. 200 means the result was produced successfully. |
data.address | string | Yes | Chain-qualified address. |
data.address_type | string | Yes | Best available address or contract classification. |
data.overall_score | string | Yes | Security score from "0" to "100"; lower is riskier. |
data.overall_risk_level | string | Yes | Human-readable risk summary derived from the score. |
data.scanned_time | integer | Yes | Unix timestamp for the analysis. |
data.result_stage | string | Yes | "complete", "fallback", or "degraded"; indicates how the result was produced. |
How to Use the Response
- Use
overall_risk_levelfor the user-facing verdict andoverall_scorefor ranking or policy thresholds. - Read
result_stagebefore using any auxiliary fields. Non-EVM requests can return afallbackresult based on available threat intelligence. - Treat any additional chain-specific objects as optional context, not as a stable cross-chain contract.
No Obvious Riskmeans no configured signal produced a stronger verdict at scan time. It is not a guarantee of safety.
Risk Level Reference
| Score | Value | Meaning |
|---|---|---|
86–100 | No Obvious Risk | No configured signal produced a stronger verdict at scan time. |
61–85 | Low Risk | Low-severity risk signals were detected. |
41–60 | Medium Risk | Material risk signals require user attention. |
16–40 | High Risk | Strong risk signals were detected. |
0–15 | Significant Risk | The highest-severity risk signals were detected. |
Errors and Retry Guidance
| HTTP | 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. |
pollAfter; aggressive polling may trigger rate limits without completing analysis sooner.Was this page helpful?