Pb with Tick History Response
I have been struggling recently with some strange behaviour I didn't have 2 months ago.
Each time I ask a specific epoch in the request, it return as if it was "latest".
For example:
{"count": 5, "ticks_history": "frxEURUSD", "end": "1568114399"}
should return something from last week but I got:
{
"echo_req": {
"count": 5,
"end": "1567865632",
"ticks_history": "frxEURUSD"
},
"history": {
"prices": [
1.10126,
1.10128,
1.10128,
1.10128,
1.10128
],
"times": [
1568715535,
1568715537,
1568715539,
1568715540,
1568715541
]
},
"msg_type": "history",
"pip_size": 5
}
Which is today, current time as if I asked "latest".
Can you help me ?
Comments
It occurs on API playground as well
:
Support told me it would be fixed, but I don't know when
Still not fixed, it's very long... I need this to work with Binary
Support gave me a work around that works, but is kind of weird:
{
"count": 5,
"ticks_history": "frxEURUSD",
"end": "1568114399",
"start": "1568104399"
}
{
"echo_req": {
"count": 5,
"end": "1568114399",
"start": "1568104399",
"ticks_history": "frxEURUSD"
},
"history": {
"prices": [
1.10376,
1.10377,
1.10376,
1.10376,
1.10376
],
"times": [
1568114395,
1568114396,
1568114397,
1568114398,
1568114399
]
},
"msg_type": "history",
"pip_size": 5
}