POST /api/solscan/accounts/analytics
Price: 1 credit
Get the activity analytics of a Solana account: lifetime totals, daily balance and transfer history
Get the activity analytics of a Solana wallet by its address: lifetime transfer count, active days, longest activity streak, first activity time and account age in days, the daily USD balance history, daily inbound and outbound transfer counts, and the top counterparties of the last 7 days with their labels.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)address string required — Solana account or token mint address (base58) (examples: "5tzFkiKscXHK5ZXCGbXZxdw7gTjjD1mBwuoFbhUvuAi9")@type string (default: "SolscanAccountAnalytics")address string requiredtransfer_count integer nullableactive_day_count integer nullablelongest_streak_days integer nullablefirst_active_at integer nullableage_days integer nullablebalance_history array (default: [])@type string (default: "SolscanBalancePoint")date integer requiredvalue number nullabledaily_transfers array (default: [])@type string (default: "SolscanDailyTransfers")date integer requiredsender_count integer nullablereceiver_count integer nullabletransfer_in_count integer nullabletransfer_out_count integer nullablevalue_in number nullablevalue_out number nullabletop_counterparties_7d array (default: [])@type string (default: "SolscanCounterparty")address string requiredlabel string nullabledirection string nullabletotal_value number nullabletransfer_count integer nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — Account not found Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.