--- title: "Get specified events" method: GET path: "/v4/data/defi/events" tags: ["DeFi API"] --- # Get specified events `GET /v4/data/defi/events` /v4/data/defi/events **50 credits per API call** Get all events on given addresses and / or in the requested block range on the following blockchains: * Ethereum - ethereum-mainnet / ethereum-sepolia * Base - base-mainnet / base-sepolia * Arbitrum - arb-one-mainnet / arb-testnet * BNB (Binance) Smart Chain - bsc-mainnet / bsc-testnet * Polygon - polygon-mainnet * Optimism - optimism-mainnet / optimism-testnet * Berachain - berachain-mainnet * Unichain - unichain-mainnet / unichain-sepolia * Monad - monad-mainnet / monad-testnet * Celo - celo-mainnet / celo-testnet * Chiliz - chiliz-mainnet * Avalanche - avax-mainnet / avax-testnet * Gnosis - gno-mainnet / gno-testnet * zkSync - zksync-mainnet / zksync-testnet * Rootstock - rsk-mainnet / rsk-testnet * Ethereum Classic - ethereum-classic-mainnet / ethereum-classic-testnet * Lisk - lisk-mainnet / lisk-testnet * XDC - xdc-mainnet / xdc-testnet * Sonic - sonic-mainnet / sonic-blaze To get started: * To improve response times and obtain specific data, it is recommended to use proper filtering techniques. Please provide a chain name and a combination of filters that will accomplish this (at least block range or contract addresses must be specified). * It is possible to specify multiple contract addresses at once by passing them as a comma separated string. * If block range is not specified, the API attempts to go through all available blocks, which may result in a timeout error. * When you are filtering data using blockFrom and not using blockTo, blockTo is automatically added as blockFrom + 500. The same applies when blockTo is present and blockFrom is not. In that case blockFrom is automatically added as blockTo - 500. * Block range filter is limited to maximum 500 * It is recommended to filter only one specific type of events, which comes with built-in decoding for all the supported types. * It is, however, also possible to filter by signature hashes, which can be passed together as a comma separated string. * For Chiliz, only the first signature will be considered; additional signatures in the array will be ignored. As noted above, aside from general info and hashed event data, the API also decodes them for you in case you filter by one of the following supported event types: * `tokenTransfer`: All transfers of fungible tokens (including stablecoins) and NFTs as per ERC-20 and ERC-721 standard. * `multitokenTransfer`: All transfers of multitokens (both single transfers and batch transfers) as per ERC-1155 standard. * `stablecoinTransfer`: Refers to the transfer of specific stablecoins on the mainnet. Typically, the top 10 to 16 stablecoins on each chain according to CoinMarketCap are included. If the `contractAddresses` parameter is also used in the filter combination, any tokens specified in it will also be included in the list. * `uniswapTrade`: Provides all swap events that occur on both Uniswap V2 and V3. In some cases, it may not be possible to map the swapped amounts to specific tokens. As a result, certain decoded data such as token amounts might be missing or in the original big number format. This will be indicated by the response parameter `partiallyRaw: true`. ## Query parameters - `chain` 'ethereum-mainnet' | 'ethereum-sepolia' | 'base-mainnet' | 'base-sepolia' | 'arb-one-mainnet' | 'arb-testnet' | 'bsc-mainnet' | 'bsc-testnet' | 'polygon-mainnet' | 'optimism-mainnet' | 'optimism-testnet' | 'berachain-mainnet' | 'unichain-mainnet' | 'unichain-sepolia' | 'monad-mainnet' | 'monad-testnet' | 'celo-mainnet' | 'celo-testnet' | 'chiliz-mainnet' | 'avax-mainnet' | 'avax-testnet' | 'gno-mainnet' | 'gno-testnet' | 'zksync-mainnet' | 'zksync-testnet' | 'rsk-mainnet' | 'rsk-testnet' | 'ethereum-classic-mainnet' | 'ethereum-classic-testnet' | 'lisk-mainnet' | 'lisk-testnet' | 'xdc-mainnet' | 'xdc-testnet' | 'sonic-mainnet' | 'sonic-blaze', required - `contractAddresses` string, required - `blockFrom` number, required - `blockTo` number, required - `eventType` 'tokenTransfer' | 'multitokenTransfer' | 'stablecoinTransfer' | 'uniswapTrade', required - `signatures` string - `pageSize` number - `offset` number ## Response `200` OK - Event[] — List of all event data. - `chain` string — Name of the chain. - `address` string — The address associated with the event. - `blockNumber` integer — The block number where the event was recorded. - `timestamp` integer — The timestamp of the event in UNIX format. - `decoded` union — The decoded event data based on the given models. - FungibleTransfer — Common properties for decoded data events. - `label` string — The label of the event. - `type` string — The type of the event. - `subtype` string — The subtype of the event. - `from` string — The sender address of the event. - `to` string — The receiver address of the event. - `decimals` integer — The number of decimal places for the transferred token. - `value` string — The value of the transferred token. - StablecoinTransfer — Common properties for decoded data events. - `label` string — The label of the event. - `type` string — The type of the event. - `subtype` string — The subtype of the event. - `from` string — The sender address of the event. - `to` string — The receiver address of the event. - `decimals` integer — The number of decimal places for the transferred token. - `value` string — The value of the transferred token. - `stablecoin` string — The address of the stablecoin being transferred. - NftTransfer — Common properties for decoded data events. - `label` string — The label of the event. - `type` string — The type of the event. - `subtype` string — The subtype of the event. - `from` string — The sender address of the event. - `to` string — The receiver address of the event. - `tokenId` string — The unique identifier of the NFT being transferred. - MultitokenTransferSingle — Common properties for decoded data events. - `label` string — The label of the event. - `type` string — The type of the event. - `subtype` string — The subtype of the event. - `from` string — The sender address of the event. - `to` string — The receiver address of the event. - `operator` string — The address of the operator initiating the transfer. - `multitokenId` string — The unique identifier of the single multitoken being transferred. - `multitokenValue` string — The value of the single multitoken being transferred. - MultitokenTransferBatch — Common properties for decoded data events. - `label` string — The label of the event. - `type` string — The type of the event. - `subtype` string — The subtype of the event. - `from` string — The sender address of the event. - `to` string — The receiver address of the event. - `operator` string — The address of the operator initiating the transfer. - `multitokenIds` string[] — The unique identifiers of the multitokens being transferred. - `multitokenValues` string[] — The values of the multitokens being transferred. - UniswapTradeV2 — Common properties for decoded data events. - `label` string — The label of the event. - `type` string — The type of the event. - `subtype` string — The subtype of the event. - `from` string — The sender address of the event. - `to` string — The receiver address of the event. - `token0` string — The address of the first token involved in the trade. - `token1` string — The address of the second token involved in the trade. - `partiallyRaw` boolean — Indicates whether the trade data is partially raw or not. - `amount0In` string — The input amount of the first token in the trade. - `amount1In` string — The input amount of the second token in the trade. - `amount0Out` string — The output amount of the first token in the trade. - `amount1Out` string — The output amount of the second token in the trade. - UniswapTradeV3 — Common properties for decoded data events. - `label` string — The label of the event. - `type` string — The type of the event. - `subtype` string — The subtype of the event. - `from` string — The sender address of the event. - `to` string — The receiver address of the event. - `token0` string — The address of the first token involved in the trade. - `token1` string — The address of the second token involved in the trade. - `partiallyRaw` boolean — Indicates whether the trade data is partially raw or not. - `amount0` string — The net amount of the first token involved in the trade. - `amount1` string — The net amount of the second token involved in the trade. - `sqrtPriceX96` string — The square root price of the trading pair scaled by 2^96. - `liquidity` string — The liquidity of the trading pair at the time of the trade. - `tick` integer — The tick index of the Uniswap V3 pool at the time of the trade. - `raw` RawData — Raw data associated with the event, including topics and data. - `topic_0` string, required — The first topic of the event, if present. - `topic_1` string — The second topic of the event, if present. - `topic_2` string — The third topic of the event, if present. - `topic_3` string — The fourth topic of the event, if present. - `data` string — The data associated with the event, if present. - `txHash` string — The transaction hash related to the event. - `txIndex` integer — The transaction index within the block. - `logIndex` integer — The log index within the transaction. ## Other responses - `400` — Bad Request - `401` — Unauthorized. Not valid or inactive subscription key present in the HTTP Header. - `403` — Forbidden. The request is authenticated, but it is not possible to perform the operation due to logical error or invalid permissions. - `500` — Internal server error. There was an error on the server during the processing of the request. --- [API](https://skmtc.net/tatum/apis/blockchain-data.md) · [All operations](https://skmtc.net/tatum/apis/blockchain-data/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tatum/blockchain-data/revisions/8622ee4b8fae/schema)