CFDs are complex instruments and come with a high risk of losing money rapidly due to leverage. 64 % of retail investor accounts lose money when trading CFDs with this provider. You should consider whether you understand how CFDs work and whether you can afford to take the high risk of losing your money.

Optional /history/badges

In the specification:

The response is a list of points (one point per day), oldest first.

__ item[0] -> (long) Millis at the end-of-day__
__ item[1] -> (double) D-Periods__
__ item[2][0] -> (double) Ex score__
__ item[2][1] -> (double) Mc score__
__ item[2][2] -> (double) Rs score__
__ item[2][3] -> (double) Ra score__
__ item[2][4] -> (double) Os score__
__ item[2][5] -> (double) Cs score__
__ item[2][6] -> (double) R+ score__
__ item[2][7] -> (double) R- score__
__ item[2][8] -> (double) Dc score__
__ item[2][9] -> (double) La score__
__ item[2][10] -> (double) Pf score__
__ item[2][11] -> (double) Cp score__
__ item[2][12] -> (double) D-Score__
**_ item[3] -> (long) Timestamp of the first calculation in millis (optional)_**
**_ item[4] -> (long) Timestamp of the last calculation in millis (optional)_**

What’s optional about? it is possible NOT to get those values? or it means that sometime you don’t get a value?

1 Like

To be honest, it should always have those values for every active darwin provided to the query.
And that’s really the key, the meaning of “active” darwin. Those optional parameters won’t exist for deleted darwins but, at the moment no query can be done over deleted products. Therefore, the specification is right even though in the practice these values should be received.

3 Likes