# History API response with Time in different format

**URL:** <https://community.delta.exchange/t/history-api-response-with-time-in-different-format/2448>\
**Category:** APIs & Algo Trading\
**Created:** [September 13, 2026, 8:19pm UTC](https://community.delta.exchange/t/history-api-response-with-time-in-different-format/2448 "2026-09-13T20:19:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dharmender](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@Dharmender](https://community.delta.exchange/u/Dharmender)\
**Post date:** [September 13, 2026, 8:19pm UTC](https://community.delta.exchange/t/history-api-response-with-time-in-different-format/2448/1 "2026-09-13T20:19:56Z")

</div>

Hi Delta,

First thing, I just observed minor thing in History API response. Just want to cross check if this is intentional or something.

When we fetch “1h” candles then API response’s candles have “Time” in Unix Second e.g. 1789312500 whereas for “1w” it is Unix Microseconds e.g. 1788739200000000.

Though it can be handled but want to cross check once. Also want to understand rationale behind it.

Secondly, I have observed that when I subscribed to

wss://public-socket.india.delta.exchange

{  
“type”: “subscribe”,  
“payload”: {  
“channels”: [  
{  
“name”: “candlestick\_1w”,  
“symbols”: [“PAXGUSD”]  
}  
]  
}  
}

WSS Response:

{

```auto
"c": 4343.9,

"cst": 1788998400000000,

"h": 4432.73,

"l": 4300.8,

"o": 4393.4,

"res": "1w",

"sy": "PAXGUSD",

"ts": 1789332399052134,

"type": "candlestick_1w",

"v": 96438093.0

```

}

Above response received at: Sept 14, 2026 at 02:16:38.391 AM IST

Logically, CST is **1788998400000000** which is 2026-09-10 00:00:00 UTC or 2026-09-10 05:30:00 IST. 2026-09-10 is wrong for current week timestamp which should be 2026-09-07. Similarly TS is also in future. In fact this tick response is incorrect and OHLC doesn’t match with chart candle.

Thanks!

---

<div class="post-metadata">

**Author:** ![manku.pathak](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@manku.pathak](https://community.delta.exchange/u/manku.pathak)\
**Post date:** [October 5, 2026, 7:36am UTC](https://community.delta.exchange/t/history-api-response-with-time-in-different-format/2448/2 "2026-10-05T07:36:50Z")

</div>

The timestamp format returned in both cases — 1h and 1w resolution — is the same: Unix epoch timestamp in seconds. Please refer to the attached files for reference.

Yes, there is a difference in timestamp format between the API and WebSocket, and this is intentional:

- **API:** Unix timestamp in seconds
- **WebSocket:** Unix timestamp in microseconds

I don’t see a future timestamp in the response. The timestamp shown is the current timestamp: **Monday, September 14, 2026 at 02:16:39.052**.

There is, however, an issue with the **1w timestamp**. As you pointed out, the CST should have been **07/09/2026**. We will fix this shortly.

 ![Screenshot 2026-10-05 at 12.36.04](https://canada1.discourse-cdn.com/flex004/uploads/deltaexchange/original/1X/9fa0bb5bd3db7ac8f503e8079f4c545daceb7d77.png)  
 ![Screenshot 2026-10-05 at 12.35.44](https://canada1.discourse-cdn.com/flex004/uploads/deltaexchange/original/1X/4d51167d397498a954c84b853070b95be4bd7663.png)

---

<div class="post-metadata">

**Author:** ![Dharmender](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@Dharmender](https://community.delta.exchange/u/Dharmender)\
**Post date:** [October 6, 2026, 8:13am UTC](https://community.delta.exchange/t/history-api-response-with-time-in-different-format/2448/3 "2026-10-06T08:13:53Z")

</div>

Thanks! Please let me know when fix get deployed. I will try to test again.

Secondly, I also mentioned that OHLC (may be some part of it) of wss isn’t matching with chart 1w OHLC. Can you please cross check that also?