Consult Ethereum historical data with the final point of API paginado
I can see that you are experiencing problems to recover data from the Binance API, which is a popular platform for trade and data storage. Specifically, you are looking to consult the historical data of Ethereum using a paginated end point.
The problem that is found may be due to the way in which the Binance API manages the pagination or limitations of its API documentation. Here is an article that provides guidance on how to achieve this:
Introduction
Historical data are essential to analyze and make informed decisions about cryptocurrencies such as Ethereum. The Binance API offers an end point paginated to recover historical data, which allows you to obtain all the data available for each period.
Step 1: Identify the consultation pattern of the end element to first place (E2I)
To consult the E2I pattern, we need to understand how the Binance API handles the pagination. The general approach is to use the `to 'parameters to specify the starting and completion of the data.
For example, suppose you want to recover all the historical operations of Ethereum from January 1, 2020 to January 31, 2022. You can use a consultation like this:
JavaScript
{
"Method": "get",
"URL": "
"Parameters": {
"Ids": []
"Campos": [
"open",
"high",
"low",
"near",
"volume"
]
}
}
Step 2: Analyze and process the answer
Once you receive the answer, analyze it to extract the relevant data. The end pointKLINESReturns a matrix of objects with several fields for each operation.
For example:
JSON
[
{
"ID": 0,
"Time brand": 1643723400,
"Open": 10000000,
"High": 15000000,
"Bass": 9000000,
"Close": 10500000,
"Volume": 5000
},
{
"ID": 1,
"Time brand": 1643723405,
"Open": 10200000,
"High": 12000000,
"Bass": 9200000,
"Close": 10800000,
"Volume": 6000
},
...
]
Step 3: Implement the pagination
To implement the pagination, you must add the 'Limit parameter to your consultation. The value of the ‘limit’ depends on the number of elements returned per page.
For example:
`JavaScript
{
"Method": "get",
"URL": "
"Parameters": {
"Ids": []
"Campos": [
"open",
"high",
"low",
"near",
"volume"
]
}
}
`
Conclusion
The recovery of all the historical data of Ethereum available requires some work, but with the correct approach, you can achieve your goal. Following these steps and understanding how to implement the pagination using the Binance API, the E2I pattern should be able to consult successfully.
If you still find problems or need more help, do not hesitate to ask. I will do everything possible to provide more orientation or point it out in the right direction.