The starting timestamp, representing the Unix timestamp in seconds.
end_time
The ending timestamp, representing the Unix timestamp in seconds. default: LatestBlock
limit
The max number of response records. A range of (0, 150] is supported. default: 100
Response (Arbitrage type)
Arbitrage is a trading strategy that allows traders to generate profit from price differences across different trading platforms.With our transaction data API, you can easily investigate the arbitrage transactions that occurred on both Ethereum and Binance Smart Chain.
We provide all the arbitrage transactions that have occurred from on-chain data based on the time range you select. The data we provide enables you to analyze the profits, costs and the specific protocols or pools utilized in each arbitrage transaction..
For example, the following response signifies an arbitrage transaction occurred between the liquidity pool of Uniswap V3:WETH/GETH and Uniswap V2:WETH/GETH.
A sandwich transaction group comprises of multiple transactions, with a typical group consisting of: the attacker's front-running transaction, the victim's transaction, and the attacker's back-running transaction.
In this API response, we provide a sandwichDetails field that represents the transactions that made up the sandwich transaction group.
The sandwichRole field indicates the role of each transaction. For example:FrontRun, Victim, BackRun
We provide liquidation data covering multiple protocols on the Ethereum chain. Currently, liquidation transactions happened in Aave V1, Aave V2, Compound, MakerDao, Liquity protocol are available in our responses. We will cover more lending platforms as necessary to provide more liquidation results.
In the response, we provide a liquidationDetails field that represents a specific liquidation data.
Please note that there may be multiple liquidations in a single transaction.
We provide lending data (with lending type of: Deposit, Withdrow, Borrow, Repay) for multiple protocols on the ethernet chain。Currently supported protocols: Aave V1,Aave V2,Compound
In the response, we provide a lendingDetails field
{
"data": [
{
.....
"lendingDetails": [
{
"address": "0x3c5fe9bad06ca2f64082295958a20da9c7260ad7", //Address where the operation was initiated
"lendingType": "Withdraw", //Deposit,Withdraw,Borrow,Repay
"protocol": "Aave V2", //protocol:AAVE V2,Compound,AAVE V1
"token": {
"address": "0x514910771af9ca656af840dff83e8264ecf986ca",
"symbol": "LINK"
},
"tokenAmount": 2600.53316334657, //Number of Token
"tokenVolume": 20262.310644652 // The value of Token (usd)
}
],
........
"type": "Lending"
}
]
}
Error Codes
Errors consist of two parts: an error code and a message. Codes are universal, but messages can vary.
401 UNAUTHORIZED
Please provide valid API key in the apikey query parameter.
{"errcode": 401, "err":"Please provide valid API key in the apikey query parameter."}
429 Quota limit exceeded
{"errcode": 429, "err":"Quota limit exceeded"}
10000 not_support_chain
Query parameter chain only supports [ethereum,bsc]
{"errcode": 10000, "err":"not_support_chain"}
10001 not_support_type
Query parameter type only supports [sandwich,liquidation,arbitrage,lending]