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:
{
"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!