--- title: "Get Smart Money Netflow Data" method: POST path: "/api/v1/smart-money/netflow" tags: ["Smart Money"] --- # Get Smart Money Netflow Data `POST /api/v1/smart-money/netflow` Analyze net capital flows (inflows vs outflows) from smart traders and funds across different time periods. This endpoint helps identify which tokens are experiencing net accumulation or distribution by smart money. What are Net Flows? Net flows represent the difference between smart money inflows and outflows for a token. This includes: - DEX Trading Activity: Tokens bought vs sold on decentralized exchanges - CEX Transfers: Tokens sent to or received from centralized exchanges - Positive Net Flow: Smart money is accumulating (buying more than selling, or withdrawing from CEXs) - Negative Net Flow: Smart money is distributing (selling more than buying, or depositing to CEXs) Key Features: - Aggregated net flow calculations across all smart money activity - Multiple time period analysis (1h, 24h, 7d, 30d) - Sortable results by volume metrics - Includes both DEX trades and CEX transfers ## Request body - SmartMoneyNetflowRequest - `chains` SmartMoneyChain[], required — Chains to include in the analysis (only smart money supported chains). Use 'all' to include all available chains. - `filters` SmartMoneyNetflowFilters — Filters for smart money netflow endpoint. These filters control which smart money categories, tokens, and data are included in the netflow analysis. - `include_smart_money_labels` SmartMoneyFilterType[] — Smart money category filters - `exclude_smart_money_labels` SmartMoneyFilterType[] — Smart money category filters - `token_address` union — Token address or symbol filter - string - string[] - `include_stablecoins` boolean — Whether to include stablecoins in the results - `include_native_tokens` boolean — Whether to include native tokens (e.g., ETH, SOL) in the results - `token_sector` string[] — Token sector filter - `trader_count` NumericRangeFilter — Filter for numeric values (floats) with optional min/max bounds. Use for prices, volumes, ratios, and other decimal values. - Values between -10.5 and 100.75 - `min` number — Minimum value (inclusive) - `max` number — Maximum value (inclusive) - `token_age_days` NumericRangeFilter — Filter for numeric values (floats) with optional min/max bounds. Use for prices, volumes, ratios, and other decimal values. - Values between -10.5 and 100.75 - `min` number — Minimum value (inclusive) - `max` number — Maximum value (inclusive) - `market_cap_usd` NumericRangeFilter — Filter for numeric values (floats) with optional min/max bounds. Use for prices, volumes, ratios, and other decimal values. - Values between -10.5 and 100.75 - `min` number — Minimum value (inclusive) - `max` number — Maximum value (inclusive) - `pagination` PaginationRequest — Pagination parameters for API requests. - `page` integer — Page number (1-based) - `per_page` integer — Number of records per page (max 1000) - `order_by` SortOrderSmartMoneyNetflowSortField[] — Custom sort order to override the endpoint's default ordering. Examples: - [{"field": "market_cap_usd", "direction": "DESC"}] - Sort by market cap descending - [{"field": "net_flow_24h_usd", "direction": "ASC"}] - Sort by 24h flow ascending - [{"field": "market_cap_usd", "direction": "DESC"}, {"field": "net_flow_24h_usd", "direction": "ASC"}] - Sort by market cap descending, then 24h flow ascending - `field` 'chain' | 'token_address' | 'token_symbol' | 'net_flow_1h_usd' | 'net_flow_24h_usd' | 'net_flow_7d_usd' | 'net_flow_30d_usd' | 'token_sectors' | 'trader_count' | 'token_age_days' | 'market_cap_usd', required — Enum for sortable fields in smart money netflow. - `direction` 'ASC' | 'DESC', required — Enum for sort directions. ## Response `200` Smart money netflow data - SmartMoneyNetflowResponse — Response model for smart money netflow endpoint. Contains the filtered smart money netflow data with metadata. - `data` SmartMoneyNetflow[], required — List of smart money netflow records - `token_address` string, required — Token contract address - `token_symbol` string, required — Token symbol - `net_flow_1h_usd` number, required — Net flow bought/sold of token by Smart Money in the past 1 hour. - `net_flow_24h_usd` number, required — Net flow bought/sold of token by Smart Money in the past 24 hours. - `net_flow_7d_usd` number, required — Net flow bought/sold of token by Smart Money in the past 7 days. - `net_flow_30d_usd` number, required — Net flow bought/sold of token by Smart Money in the past 30 days. - `chain` string, required — Blockchain chain - `token_sectors` string[], required — Token sectors - `trader_count` integer, required — Number of Smart Money traders of token in the past 30 days. - `token_age_days` integer, required — Number of days since token was deployed. - `market_cap_usd` number — Market cap of token. - `pagination` PaginationInfo, required — Pagination information for API responses. - `page` integer — Current page number - `per_page` integer — Number of records per page - `is_last_page` boolean — Whether this is the last page ## Other responses - `400` — Bad Request - Invalid request parameters or malformed request - `401` — Authentication error - No API key found in request - `402` — Payment Required - This endpoint supports pay-per-request via x402 and MPP. x402 responses advertise payment options in `Payment-Required`; MPP responses advertise a fresh `WWW-Authenticate: Payment ...` challenge. Successful MPP responses may include `Payment-Receipt`. - `403` — Forbidden - User does not have required subscription tier or has exceeded credit limit - `404` — Not Found - The requested resource was not found - `422` — Validation error - Invalid request parameters - `429` — Too Many Requests - Rate limit exceeded - `500` — Internal Server Error - An unexpected error occurred --- [API](https://skmtc.net/nansen/apis/nansen-api.md) · [All operations](https://skmtc.net/nansen/apis/nansen-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/nansen/nansen-api/revisions/02a4d2e7d827/schema)