In/out volume of an address
Check the *_complete flags before trusting a total or a 0 — a hub-sized address can run out of budget. On Solana (chain -1) the answer also carries coverage_status — pending (the address's history is still being filled, or no fill was asked for yet, since this read never starts one) or partial (filled to a documented bound). The *_complete flags describe the request budget only and never cover the Solana fill state. A Solana answer without coverage_status could not read it in time — treat it as pending.
Request
- Base URL: https://stablescan.achivx.com
- URL: https://stablescan.achivx.com/v1/addresses/{address}/volume
- Auth: none required
Path parameters
Address in the network's native spelling (0x… EVM, T… Tron, base58 Solana). The answer writes it in the spelling of chain_id (address; /balances alone echoes the path there) and echoes the path in requested_address; address_respelled: true means the spelling belongs to another kind of chain than chain_id (a T… address asked about an EVM chain, a 0x… address asked about Tron) — answered about the same bytes there, not refused, and the same owner only for a plain key account.
Query parameters
Pass it explicitly — silent default is Base (8453); an answer about the wrong network looks exactly like an answer. Accepted as the number, the number in a string, the network slug (ethereum, bnb-chain, … from /v1/networks) or the CAIP-2 id. Surrounding whitespace, a leading + and leading zeros are ignored, slugs and CAIP-2 ids match in any letter case, and an empty or blank value is the parameter left off (/v1/freezes/acts alone refuses it).
Response
In/out volume of an address.
Changes
No recorded changes to this operation across all 1 revision of this API.