thirdwebDocs

Insight API Fields Deprecation

Toomas Oosalu

Insight API will deprecate all camelCase fields from responses and remove them by 30th of March 2025. Every field that was previously in camelCase has a duplicate field in snake_case for the time being, allowing users to migrate their response handling.

List of affected fields:

  • decodedData
    • New name: decoded
    • Affected endpoints
      • v1/transactions (in case of decode=true query param)
      • v1/transactions/:contractAddress (in case of decode=true query param)
      • v1/transactions/:contractAddress/:signature
      • v1/events (in case of decode=true query param)
      • v1/events/:contractAddress (in case of decode=true query param)
      • v1/events/:contractAddress/:signature
  • decodedData.indexedParams and decoded.indexedParams
    • New name: indexed_params
    • Affected endpoints
      • v1/events (in case of decode=true query param)
      • v1/events/:contractAddress (in case of decode=true query param)
      • v1/events/:contractAddress/:signature
  • decodedData.nonIndexedParams and decoded.nonIndexedParams
    • New name: non_indexed_params
    • Affected endpoints
      • v1/events (in case of decode=true query param)
      • v1/events/:contractAddress (in case of decode=true query param)
      • v1/events/:contractAddress/:signature
  • chainId
    • New name: chain_id
    • Affected endpoints
      • v1/tokens/erc20/:ownerAddress
      • v1/tokens/erc721/:ownerAddress
      • v1/tokens/erc1155/:ownerAddress
  • tokenAddress
    • New name: token_address
    • Affected endpoints
      • v1/tokens/erc20/:ownerAddress
      • v1/tokens/erc721/:ownerAddress
      • v1/tokens/erc1155/:ownerAddress
  • tokenId
    • New name: token_id
    • Affected endpoints
      • v1/tokens/erc721/:ownerAddress
      • v1/tokens/erc1155/:ownerAddress

Example of a decoded data response 

// rest of response...
"decoded": {
    "name": "Transfer",
    "signature": "Transfer(address,address,uint256)",
    // will be deprecated
    "indexedParams": {
        "from": "0x0000000000000000000000000000000000000000",
        "to": "0x321b7ff75154472b18edb199033ff4d116f340ff"
    },
    "indexed_params": {
        "from": "0x0000000000000000000000000000000000000000",
        "to": "0x321b7ff75154472b18edb199033ff4d116f340ff"
    },
    // will be deprecated
    "nonIndexedParams": {
        "amount": 4843303142399797056
    },
    "non_indexed_params": {
        "amount": 4843303142399797056
    }
},
// rest of response...

It should be noted that the properties in indexed_params and non_indexed_params could be any format, because they are based on how the smart contract was programmed.

Example of a token response

// rest of response...
{
  // will be deprecated
  "chainId": 1,
  "chain_id": 1,
  // will be deprecated
  "tokenAddress": "0xca8098ab4503aee15b3291d22c0852518d04da63",
  "token_address": "0xca8098ab4503aee15b3291d22c0852518d04da63",
  // will be deprecated
  "tokenId": "78",
  "token_id": "78",
  "balance": "1"
},
// rest of response...

📖 Learn more about Insight - it’s open source and ready to power your applications!