Endpoints Reference

This page provides a quick reference of all Nansen API endpoints covered by nansen-go, mapped to their corresponding service methods.

Stable API (v1)

HTTP Method	Path	Service	Method
POST	/api/v1/smart-money/netflow	client.SmartMoney	Netflow
POST	/api/v1/smart-money/holdings	client.SmartMoney	Holdings
POST	/api/v1/smart-money/dex-trades	client.SmartMoney	DEXTrades
POST	/api/v1/token-screener	client.TokenGodMode	TokenScreener
POST	/api/v1/tgm/flow-intelligence	client.TokenGodMode	FlowIntelligence
POST	/api/v1/tgm/who-bought-sold	client.TokenGodMode	WhoBoughtSold
POST	/api/v1/profiler/address/current-balance	client.Profiler	AddressCurrentBalance
POST	/api/v1/profiler/dex-trades	client.Profiler	AddressDEXTrades
POST	/api/v1/portfolio/defi-holdings	client.Portfolio	DeFiHoldings

Beta API (v1beta1)

These endpoints are under the Historical service and are intended for backtesting and historical analysis. The v1beta1 prefix indicates that the API contract may change.

HTTP Method	Path	Service	Method
POST	/api/v1beta1/tgm/historical-token-flow-summary	client.Historical	HistoricalTokenFlowSummary
POST	/api/v1beta1/smart-money/historical-token-balances	client.Historical	HistoricalSmartMoneyTokenBalances

Authentication

All endpoints require an API key, which is sent as the apiKey request header. The key is set once when constructing the client and is applied automatically to every request.

client, err := nansen.New(os.Getenv("NANSEN_API_KEY"))