<p>I have noticed the same. I am afraid that we have to live with it since even on bittrex website charts are delayed by 3 minutes approximately. You can see that if you get the 1-minute chart plotted. Market history is on time though. If you need this sort of speed, you could build a script to catch ticks from market history list. </p>

CC BY-SA 3.0
2018-02-19T21:32:17.160Z
2018-02-19T21:32:17.160Z
Ben2209
<p>I have noticed this delay as well. There can be up to four-minutes of delay on the Bittrex API. When looking at the parabolic SAR, I have found that this data can be behind by up to three ticks of the SAR. To solve the problem, I used <a href="https://www.cluedex.com/product/api/ohlcv-candle-api" rel="nofollow noreferrer">cluedex.com</a> which provides a premium API for this data. There is no delay and I have found that the SAR metric that I calculate is much faster with this data, which means I can place trades ahead of the trend. </p>

CC BY-SA 3.0
2018-03-18T21:50:24.200Z
2018-03-18T21:50:24.200Z
Laser-Lance
<p>I'm noticing that the Bittrex API (both v1.1 and v2.0) have a 3 to 4 minute delay when getting data, i.e. GetLatestTick:
<a href="https://bittrex.com/api/v2.0/pub/market/GetLatestTick?marketName=BTC-NEO&amp;tickInterval=hour" rel="nofollow noreferrer">https://bittrex.com/api/v2.0/pub/market/GetLatestTick?marketName=BTC-NEO&amp;tickInterval=hour</a></p>

<p>So if you make a request say at 8:00PM, it will not bring the 7:00 to 8:00PM candle data until 8:03PM, some times 8:04PM ...</p>

<p>I thought about constructing my own candles querying the API every few seconds with /getticker - but for a few cryptos it will get lengthy and might get banned for the amount of requests per second ...</p>

<p>Anyone knows any other method to get candle data sooner?</p>

<p>Thanks!</p>

CC BY-SA 3.0
2018-02-05T18:32:48.110Z
what are you trying to get?
Tailer
CC BY-SA 3.0
2018-02-05T20:57:02.350Z
Candles for the last hour for a number of currencies (/GetLatestTick)
Neurus
<api><bittrex>
Bittrex API 3 minute delay
Neurus
# Bittrex API 3 minute delay

(Asked by: username_0 on 2018-02-05)

I'm noticing that the Bittrex API (both v1.1 and v2.0) have a 3 to 4 minute delay when getting data, i.e. GetLatestTick:
<https://bittrex.com/api/v2.0/pub/market/GetLatestTick?marketName=BTC-NEO&tickInterval=hour>

So if you make a request say at 8:00PM, it will not bring the 7:00 to 8:00PM candle data until 8:03PM, some times 8:04PM ...

I thought about constructing my own candles querying the API every few seconds with /getticker - but for a few cryptos it will get lengthy and might get banned for the amount of requests per second ...

Anyone knows any other method to get candle data sooner?

Thanks!

**Tags:** api, bittrex

> **Comments:**
> **username_1**: what are you trying to get?  
> **username_0**: Candles for the last hour for a number of currencies (/GetLatestTick)  

---

## 2 answers

### Answer by username_2 on 2018-02-19. Score: 0 | Accepted answer

I have noticed the same. I am afraid that we have to live with it since even on bittrex website charts are delayed by 3 minutes approximately. You can see that if you get the 1-minute chart plotted. Market history is on time though. If you need this sort of speed, you could build a script to catch ticks from market history list.


---

### Answer by username_3 on 2018-03-18. Score: 0

I have noticed this delay as well. There can be up to four-minutes of delay on the Bittrex API. When looking at the parabolic SAR, I have found that this data can be behind by up to three ticks of the SAR. To solve the problem, I used [cluedex.com](https://www.cluedex.com/product/api/ohlcv-candle-api) which provides a premium API for this data. There is no delay and I have found that the SAR metric that I calculate is much faster with this data, which means I can place trades ahead of the trend.


---

