Changelog

API Changelog

2025-08-29 - Major API Restructuring: Beta β†’ v1 Migration

This changelog highlights the key architectural and structural differences between the beta endpoints and v1 endpoints, focusing on breaking changes that developers need to be aware of when migrating.

πŸ”„ Version Update

  • From: Beta endpoints (/api/beta/*)

  • To: v1 endpoints (/api/v1/*)

πŸ—οΈ Major Structural Changes

1. Parameter Structure Overhaul

Before (Beta): Nested Parameters Object

{
  "parameters": {
    "tokenAddress": "2zMMhcVQEXDtdE6vsFS7S7D5oUodfJHE8vd1gnBouauv",
    "smFilter": ["180D Smart Trader"],
    "chain": "solana"
  },
  "pagination": {
    "page": 1,
    "recordsPerPage": 100
  }
}

After (v1): Structured Request with Nested Filters

{
  "chain": "solana",
  "token_address": "2zMMhcVQEXDtdE6vsFS7S7D5oUodfJHE8vd1gnBouauv",
  "filters": {
    "smart_money": {
      "include": ["180D Smart Trader"]
    },
    "include_stablecoins": true,
    "include_native_tokens": true
  },
  "pagination": {
    "page": 1,
    "per_page": 100
  }
}

Impact: All existing client code must be restructured to remove the nested parameters wrapper.

2. Naming Convention Changes

Before (Beta): camelCase

  • tokenAddress

  • includeStablecoin

After (v1): snake_case

  • tokenAddress β†’ token_address`

  • smFilter β†’ filters.smart_money.include (nested structure)

  • includeStablecoin β†’ filters.include_stablecoins

Impact: Significant impact - all fields are changed to snake_case

3. Response Structure Standardization

Before (Beta): camelCase Response Fields

{
  "tokenAddress": "...",
  "symbol": "...",
  "marketCap": 1000000
}

After (v1): snake_case Response Fields

{
  "token_address": "...",
  "symbol": "...",
  "market_cap": 1000000
}

Note: Not all v1 endpoints return pagination fields - some return data only while others include pagination metadata. When pagination is present, it now includes an is_last_page boolean for easier pagination handling.

Impact: All client code must be updated to handle snake_case field names in responses.

πŸ“‹ Renamed Endpoint

Smart Money Endpoints

/beta/smart-money/inflows β†’ /api/v1/smart-money/netflow

Profiler Endpoints

/beta/profiler/address/balances β†’ /api/v1/profiler/address/current-balance

🚨 Breaking Changes Summary

Must Update:

  1. Remove nested parameters wrapper from all requests

  2. Handle new response structure with data and pagination fields

  3. Check parameter naming for snake_case vs camelCase changes

Last updated

Was this helpful?