Operating Principles
General info about Crypto Data Service:
Our platform collects cryptocurrency price data with 1-minute precision—allowing you to track every market movement with maximum granularity.
All prices are pegged to USDT (Tether USD), ensuring comparability with the US dollar.
The project launch is scheduled for January 1, 2026, but for key assets (Bitcoin and Ethereum), we're ready to provide historical data dating back to 2020. Five years of market history at your fingertips.
Data collection runs continuously: each day is automatically closed in complete 24-hour blocks that can be divided into portions.
You receive fresh information without gaps or delays.
All prices are pegged to USDT (Tether USD), ensuring comparability with the US dollar.
The project launch is scheduled for January 1, 2026, but for key assets (Bitcoin and Ethereum), we're ready to provide historical data dating back to 2020. Five years of market history at your fingertips.
Data collection runs continuously: each day is automatically closed in complete 24-hour blocks that can be divided into portions.
You receive fresh information without gaps or delays.
Query Parameters
Data export from Crypto Data Service:
-
Export PeriodTime period (date and time) for data export. -
Data Aggregation StepAggregation step specification for the export period. -
CryptocurrencyAsset code selection for data export. -
Data Export FormatExport file generation in user-specified format.
Data Structure
Set of data fields in Crypto Data Service:
Pair
Cryptocurrency identifier consisting of base and quote assets supported by the service.
Timestamp
Timestamp corresponding to the start of the trading period (candle open), represented in Unix Time format.
Open
Price of the first trade executed at the beginning of the given trading period.
The value is denominated in USDT.
The value is denominated in USDT.
High
Highest price reached by the asset during this trading period.
The value is denominated in USDT.
The value is denominated in USDT.
Low
Lowest price reached by the asset during this trading period.
The value is denominated in USDT.
The value is denominated in USDT.
Close
Price of the last trade recorded at the very end of the given trading period.
The value is denominated in USDT.
The value is denominated in USDT.
Volume
Total amount of the base asset that was bought or sold during this period.
The value is expressed in units.
The value is expressed in units.
Primary Key
Unique record identifier in the database, consisting of the cryptocurrency ID and corresponding timestamps.
Storage Format
Data organization in Crypto Data Service:
Data Export Format
XLSX – modern open-standard format for spreadsheets developed by Microsoft.
CSV – simple text format for storing tabular data, where each line in the file represents a table row, and fields (columns) are separated by a delimiter.
XML – universal text format for structured storage, transmission, and description of data using self-defining tags.
JSON – lightweight text format for data storage and exchange, based on key-value pairs and lists (arrays).
.
CSV – simple text format for storing tabular data, where each line in the file represents a table row, and fields (columns) are separated by a delimiter.
XML – universal text format for structured storage, transmission, and description of data using self-defining tags.
JSON – lightweight text format for data storage and exchange, based on key-value pairs and lists (arrays).
.
- XLSX
- CSV
- XML
- JSON
Visual Preview
Processing result of Crypto Data Service:
The representation of export results depends on the export file format specified by the user.
In general, the retrieved data can be represented as a table that fully corresponds to the service-side data storage format, with the exception of the "pair" and "timestamp" fields.
On the service side, a " / " delimiter is added to the "pair" field value, and the "timestamp" field value is converted to a human-readable format depending on the user's locale. This is done for your convenience.
On the service side, a " / " delimiter is added to the "pair" field value, and the "timestamp" field value is converted to a human-readable format depending on the user's locale. This is done for your convenience.