-
Notifications
You must be signed in to change notification settings - Fork 0
Endpoints
Igor Sazonov edited this page Jul 15, 2026
·
1 revision
The Nansen PHP client groups endpoints into categories, mirroring the structure of the Nansen API documentation.
Here is a comprehensive list of the supported endpoints:
| Category | Endpoint Method | Description |
|---|---|---|
| Smart Money | smartMoney()->netflows() |
Returns netflow data for smart money addresses. |
smartMoney()->holdings() |
Returns token holdings for smart money addresses. | |
smartMoney()->dexTrades() |
Returns decentralized exchange trades executed by smart money. | |
| Token God Mode | tokenGodMode()->tokenScreener() |
Allows screening tokens based on various metrics and signals. |
tokenGodMode()->flowIntelligence() |
Provides insights into token flows. | |
tokenGodMode()->whoBoughtSold() |
Identifies top buyers and sellers for a specific token. | |
| Profiler | profiler()->addressBalance($address) |
Retrieves the current token balances for a specific address. |
profiler()->addressDexTrades($address) |
Retrieves DEX trades for a specific address. | |
profiler()->addressLabels($address) |
Retrieves Nansen's proprietary labels for a specific address. | |
| Portfolio | portfolio()->defiHoldings($address) |
Retrieves DeFi holdings (e.g., LP positions, staking) for an address. |
| Search | search()->general($query) |
Performs a general search across the Nansen database. |
search()->entity($entityId) |
Searches for a specific entity by its ID. | |
| Historical Data | historicalData()->query($path) |
Accesses v1beta1 backtesting endpoints dynamically. |
historicalData()->netflows() |
Shortcut for historical smart money netflows. | |
historicalData()->holdings() |
Shortcut for historical smart money holdings. | |
historicalData()->dexTrades() |
Shortcut for historical smart money DEX trades. |
If Nansen releases a new endpoint or adds new fields to an existing response, you do not have to wait for the library to be updated.
Because every response DTO preserves the untouched API response in the ->raw property, you can always access the underlying data directly. For more details, see Working with Responses.