Known Issues And Challenges With Exchanges API
The driving force for Path.‘s API platform is to ‘Make Crypto Easy’ for everyone. We do the hard work behind the scene so a developer can focus on building amazing products.
However, there are some fundamental issues with the core data sources that are beyond our control. We code around these challenges where possible, but the following are known issues that affect our platform.
Issue: Transaction history does not include any assets or activities in the lending account.
What does this mean for Path API?: The data returned will not reflect any movement of assets between the lending account and the main trading account.
Issue: The Bitstamp API will only return history from the last 30 days.
What does this mean for Path API?: As our API can store previously fetched data, the initial request will have a history of 30 days. But subsequent requests will contain persisted data from prior requests. Bitstamp does offer the complete transaction history via a CSV download. We plan to offer this support soon.
Issue: The Bittrex API will only return recent trade history.
What does this mean for Path API?: As our API can store previously fetched data, the initial request will have the most recent data. But subsequent requests will contain persisted data from prior requests. Bittrex does offer the transaction history via a CSV download which our API support.
Issue: Binance does not expose all deposits/forks/airdrops via their API.
What does this mean for Path API?: Since this information is missing, we try to infer as much as possible. Like many financial systems, we use a pseudo double-entry system to audit data. With the missing distribution entries, applications that depend on a similar audit system will fail. We are working on a solution to help resolve this.