post
https://public-api.birdeye.so/token/v1/transfer
Retrieve the transfer history of a specified token
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Cursor-paginated transfer history for one Solana token.
- Solana transfer data is available from epoch
257(2021-11-12). - Supports four transfer actions:
mint,burn,transfer, andset_authority. - Pagination uses a cursor. On the first request, send normal filters without
cursor. Subsequent requests should send only the returnednext_cursor. - When
cursoris provided together with other filters, onlycursoris applied.
Reading the numbers. Use token transfer rows when you need the exact movement records behind supply changes, wallet flows, or mint/burn events.
- Standard
- Lite
- Starter
- Premium
- Business
- Enterprise
Solana
Compute Unit ⚙️
- This endpoint consumes
10 CUper request.
Use Cases 💡
- Inspect token transfer flow across all wallets for one mint.
- Review mint, burn, and standard transfer activity around launches or supply events.
- Support forensic timelines, treasury tracing, and token-flow monitoring.
How to Use 🛠️
- Set
x-chain=solana. - Send the token mint and any transfer filters in the POST body.
- On page 1, omit
cursor. - While
next_cursoris present, send only thatcursorvalue on the next request.
Best Practices ✅
- Use the total endpoint first when you only need counts before pulling the full list.
- Persist
next_cursorwhile paging; do not mix it with stale filters. - Use this token-level view when the token is the anchor, and wallet-transfer endpoints when one wallet is the anchor.
Limitations ⚠️
- Solana only.
- Historical coverage starts from epoch
257(2021-11-12). - Cursor pagination means page boundaries are driven by
next_cursor, not offset.