Solana Token Security - HashDit API Documentation

Asynchronous endpoint Get a Solana token mint’s overall security score and risk level.

This endpoint is dedicated to Solana. Send the token mint in address; do not send chain_id.

The completed payload can contain additional Solana analysis. For a durable integration, rely on the decision fields documented below; auxiliary analysis objects may change as coverage evolves.

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/solana-token-security \
  --header 'Content-Type: application/json' \
  --header 'X-API-KEY: YOUR_API_KEY' \
  --data '{
    "address": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
    "sync": false
  }'

{
  "code": "0",
  "status": "ok",
  "data": {
    "status": 200,
    "address": "sol:EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
    "address_type": "Solana",
    "overall_score": "80",
    "overall_risk_level": "Low Risk",
    "scanned_time": 1790617277,
    "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

Solana token mint address.

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 token 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 Solana token-security result.
`data.status`	integer	Yes	Analysis status. `200` means the result was produced successfully.
`data.address`	string	Yes	Chain-qualified token mint address.
`data.address_type`	string	Yes	Detected blockchain type.
`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_level for the user-facing verdict and overall_score for ranking or policy thresholds.
Read result_stage before using any auxiliary fields. A fallback result can be less detailed than complete analysis.
Treat any additional Solana-specific objects as optional context, not as the stable decision contract.
No Obvious Risk is a point-in-time assessment, not a safety guarantee.

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`	Invalid or unsupported mint 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.

For polling, respect pollAfter; aggressive polling may trigger rate limits without completing analysis sooner.

​Quick Start

​Request Fields

​Response Fields

​How to Use the Response

​Risk Level Reference

​Errors and Retry Guidance

Quick Start

Request Fields

Response Fields

How to Use the Response

Risk Level Reference

Errors and Retry Guidance