A deprecated SQL database and REST API providing historical XRP Ledger transaction data and analytics.
Ripple Data API v2 is a deprecated SQL database and REST API that serves as a canonical source for historical data from the XRP Ledger. It provides transaction history, analytical data, and network metrics, offloading historical storage from `rippled` servers. The project was used to power applications like XRP Charts and ripple.com.
Developers and analysts building applications that require historical XRP Ledger data, such as blockchain explorers, financial dashboards, or auditing tools. It is also relevant for those needing to self-host historical data for compliance or specific use cases.
It offers a dedicated, processed dataset with a rich REST API for querying historical ledger data, which simplifies building analytical applications compared to querying `rippled` directly. However, it is deprecated, and users are advised to migrate to the `rippled` API for ongoing support.
SQL database as a canonical source of historical data
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides processed analytical data and full transaction history from the XRP Ledger, enabling deep historical analysis beyond what `rippled` servers store.
Includes specific methods for exchange rates, payment volumes, active accounts, and daily reports, simplifying data aggregation for dashboards and tools.
Offloads historical storage from `rippled` servers, allowing them to maintain fewer ledger versions and improve performance for real-time operations.
Offers a wide range of REST methods for querying ledgers, transactions, payments, and network metrics, as detailed in the extensive API reference.
The project is explicitly deprecated with no ongoing support, updates, or security patches, making it a risky choice for production environments.
The README warns against self-hosting due to complexity and recommends contacting Ripple Technical Services, indicating significant setup and maintenance challenges.
Focuses solely on historical data, so it cannot provide real-time ledger state or instant transaction queries, limiting its use for live applications.