|
3 | 3 | This section explains how the dexpool data is built and shared via APIs and [Kafka streams](https://docs.bitquery.io/docs/streams/kafka-streaming-concepts/). It also explains how to understand each entry of the response. |
4 | 4 |
|
5 | 5 | > **Note:** In GraphQL, DEXPools data is accessed through two schema cubes: |
| 6 | +> |
6 | 7 | > - **`DEXPoolEvents`**: Provides pool event data (swaps, mints, burns, etc.) |
7 | 8 | > - **`DEXPoolSlippages`**: Provides slippage and price impact data for different trade sizes |
8 | | -> |
9 | | -> For blockchain-specific slippage API documentation, see: |
10 | | -> - [Arbitrum Slippage API](https://docs.bitquery.io/docs/blockchain/Arbitrum/arbitrum-slippage-api/) |
11 | | -> - [Base Slippage API](https://docs.bitquery.io/docs/blockchain/Base/base-slippage-api/) |
12 | | -> - [BSC Slippage API](https://docs.bitquery.io/docs/blockchain/BSC/bsc-slippage-api/) |
13 | | -> - [Matic Slippage API](https://docs.bitquery.io/docs/blockchain/Matic/matic-slippage-api/) |
| 9 | +
|
14 | 10 |
|
15 | 11 | import VideoPlayer from "../../src/components/videoplayer.js"; |
16 | 12 |
|
@@ -110,12 +106,30 @@ The following events trigger a new DEXPool entry: |
110 | 106 | - `ModifyLiquidity(bytes32,address,int24,int24,int256,bytes32)` - Emitted when liquidity is modified in the pool |
111 | 107 | - `Swap(bytes32,address,int128,int128,uint160,uint128,int24,uint24)` - Emitted when tokens are swapped in the pool |
112 | 108 |
|
| 109 | +> Note: Forks of Uniswap can also be tracked with these APIs if the signature is exactly the same. |
| 110 | +
|
113 | 111 | ## Filtering in DEXPools Cube |
114 | 112 |
|
115 | 113 | Filtering helps to fetch the exact pool data you are looking for. DEXPools Cube can filter based on pool address, token addresses, DEX protocol, liquidity amounts, and more. |
116 | 114 |
|
117 | 115 | Everything inside the "where" clause filters; it follows the `AND` condition by default. |
118 | 116 |
|
| 117 | +## API Examples |
| 118 | +For blockchain-specific slippage API documentation, see: |
| 119 | + |
| 120 | +- [Arbitrum Slippage API](https://docs.bitquery.io/docs/blockchain/Arbitrum/arbitrum-slippage-api/) |
| 121 | +- [Base Slippage API](https://docs.bitquery.io/docs/blockchain/Base/base-slippage-api/) |
| 122 | +- [BSC Slippage API](https://docs.bitquery.io/docs/blockchain/BSC/bsc-slippage-api/) |
| 123 | +- [Matic Slippage API](https://docs.bitquery.io/docs/blockchain/Matic/matic-slippage-api/) |
| 124 | + |
| 125 | +For blockchain-specific liquidity API documentation, see: |
| 126 | + |
| 127 | +- [Arbitrum Liquidity API](https://docs.bitquery.io/docs/blockchain/Arbitrum/arbitrum-liquidity-api/) |
| 128 | +- [Base Liquidity API](https://docs.bitquery.io/docs/blockchain/Base/base-liquidity-api/) |
| 129 | +- [BSC Liquidity API](https://docs.bitquery.io/docs/blockchain/BSC/bsc-liquidity-api/) |
| 130 | +- [Ethereum Liquidity API](https://docs.bitquery.io/docs/blockchain/Ethereum/dextrades/ethereum-liquidity-api/) |
| 131 | +- [Matic Liquidity API](https://docs.bitquery.io/docs/blockchain/Matic/matic-liquidity-api/) |
| 132 | + |
119 | 133 | ## Advanced Use Cases and Processing Patterns |
120 | 134 |
|
121 | 135 | ### Liquidity Depth Analysis |
|
0 commit comments