Insight API Fields Deprecation

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 ofdecode=true
query param)v1/transactions/:contractAddress
(in case ofdecode=true
query param)v1/transactions/:contractAddress/:signature
v1/events
(in case ofdecode=true
query param)v1/events/:contractAddress
(in case ofdecode=true
query param)v1/events/:contractAddress/:signature
- New name:
decodedData.indexedParams
anddecoded.indexedParams
- New name:
indexed_params
- Affected endpoints
v1/events
(in case ofdecode=true
query param)v1/events/:contractAddress
(in case ofdecode=true
query param)v1/events/:contractAddress/:signature
- New name:
decodedData.nonIndexedParams
anddecoded.nonIndexedParams
- New name:
non_indexed_params
- Affected endpoints
v1/events
(in case ofdecode=true
query param)v1/events/:contractAddress
(in case ofdecode=true
query param)v1/events/:contractAddress/:signature
- New name:
chainId
- New name:
chain_id
- Affected endpoints
v1/tokens/erc20/:ownerAddress
v1/tokens/erc721/:ownerAddress
v1/tokens/erc1155/:ownerAddress
- New name:
tokenAddress
- New name:
token_address
- Affected endpoints
v1/tokens/erc20/:ownerAddress
v1/tokens/erc721/:ownerAddress
v1/tokens/erc1155/:ownerAddress
- New name:
tokenId
- New name:
token_id
- Affected endpoints
v1/tokens/erc721/:ownerAddress
v1/tokens/erc1155/:ownerAddress
- New name:
Example of a decoded data 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
📖 Learn more about Insight - it’s open source and ready to power your applications!