Skip to Content
APIDeep AnalysisGet Large Transactions

Get Large Transactions

1. Overview & Typical Use

Returns large transactions for a specified account filtered by token, type, and amount, supporting filtering by transfer type (incoming, outgoing, swap, liquidity operations, etc.).

  • Typical use: large transaction monitoring, DeFi operation tracking, fund movement alerts.
  • When not to use: to query fund flow distribution, use “Get Account Transfer Amount Distribution”; to query chain-wide stablecoin large transactions, use “Get Stablecoin Large Transactions”.

2. Endpoint & Authentication

GET /api/deep/account/token/bigAmount

For Base URL and authentication, see Common Network & Authentication.

This endpoint requires an API Key; calls without a Key return 401.

3. Request

ParameterTypeRequiredDefaultDescription
addressstringYes—Account address to query
relatedTokenstringYes—Related token address (Base58)
typesstringYes—Transfer types (comma-separated): 0 all, 1 incoming, 2 outgoing, 3 swap, 4 add liquidity, 5 remove liquidity, 6 deposit, 7 borrow, 8 repay, 9 withdraw
txUsdstringNo—USD amount range, comma-separated, e.g. 1,10
txAmountstringNo—Token quantity range, comma-separated, e.g. 100,10000
relatedAddressstringNo—Filter by related address
startTimeintegerNo—Start time (Unix timestamp in seconds), maximum interval: 6 months
endTimeintegerNo—End time (Unix timestamp in seconds), maximum interval: 6 months
limitintegerNo100Number of results, maximum 100
sortBystringNotimeSort field: time, amount, usd
ascbooleanNofalseWhether to sort ascending

4. Response

Top-level

FieldTypeRequiredDescriptionUnit/Precision
totalintegerRequiredTotal number of matches—
codeintegerRequiredStatus code; 0 means success—
dataarrayRequiredTransaction list—
contractMapobjectOptionalAddress → whether the address is a contract (boolean)—
contractInfoobjectOptionalInvolved contract address → label info (value schema below)—
chartRefreshTimeintegerOptionalChart data refresh timestamp; code-derived from Greason v5 scan (reproducing sample pending)Unix seconds

contractInfo[<addr>] object schema (8 fields):

FieldTypeRequiredDescription
tag1stringRequiredPrimary label (project name / contract name / exchange name)
tag1UrlstringRequiredURL of the primary label (may be an empty string)
namestringRequiredFormal contract / project name
isTokenbooleanRequiredWhether it is a token contract (true / false)
vipbooleanRequiredWhether it is a VIP entity (true / false)
riskboolean | stringRequiredRisk label; most endpoints return boolean, some return a string risk type (blacklist / fraud, etc.)
publicTagDescstringRequiredPublic label description; empty string for most accounts
publicTagstringOptionalPublic label (e.g. "USDT Token" / "Binance"); returned only for well-known entities or certain endpoints

data[] element

FieldTypeRequiredDescriptionUnit/Precision
amountnumberRequiredTransaction quantityToken units
amountUsdnumberRequiredTransaction amountUSD
contractAddressstringRequiredToken contract address—
dateTimeintegerRequiredTransaction timeMillisecond timestamp
fromAddressstringRequiredSender address—
fromAddressTagstringOptionalSender label—
toAddressstringRequiredRecipient address—
toAddressTagstringOptionalRecipient label—
hashstringRequiredTransaction hash—
transferTypestringRequiredTransfer type code—
externalContractAddressstringOptionalExternal contract address (for DeFi operations)—

5. Errors

For HTTP status codes, see Common Errors. Key points for this endpoint:

  • API Key Required: returns 401 if not provided.
  • Missing required parameters: when address, relatedToken, or types is absent, empty data is returned without an error.
  • Time range exceeds 6 months: silently truncated.
  • Empty result is not an error: no matches returns 200 + data: [] as a normal response.
Last updated on: