/solscan/tokens/transfers

POST /api/solscan/tokens/transfers

Price: 1 credit

List the transfer history of a Solana token by its mint address

How to use it

List the transfers of a specific Solana SPL token by its mint address, newest first. Returns each transfer's transaction signature, slot, block time, activity type, sender and recipient addresses, token mint, amount, and USD value. Filter by a Unix time range, and optionally exclude spam and zero-amount transfers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• address string required — Token mint address (base58) (examples: "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v")
• count integer required — Max number of transfers to return (min: 1)
• from_time integer nullable — Only transfers at or after this Unix time (seconds) (min: 0)
• to_time integer nullable — Only transfers at or before this Unix time (seconds) (min: 0)
• remove_spam boolean — Exclude transfers flagged as spam (default: true)
• exclude_amount_zero boolean — Exclude zero-amount transfers (default: true)

Response

• @type string (default: "SolscanTransfer")
• signature string nullable
• slot integer nullable
• block_time integer nullable
• activity_type string nullable
• from_address string nullable
• to_address string nullable
• token_address string nullable
• decimals integer nullable
• amount number nullable
• flow string nullable
• value number nullable

Errors

• 422 — 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 — Token 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.