Hmm, I'll investigate - canPlaceOrder should be true if both active is true and you haven't placed the maximum # of allowed orders for Arms day yet.
Изменено (VThornheart): 2/20/2016 12:19:02 AMOh, that's right - you're hitting the public Advisor endpoint! Aha! So canPlaceOrder isn't really relevant in the public advisor - the reason why it's returned is a little embarassing. So on the server side, we reuse our contracts whenever we can, and we reused the private contract for the public one: but the canPlaceOrder field is non-nullable, and rather than break the contract or change its meaning (which was intended to check whether you specifically have the ability to place orders at this time) we simply have it return a default value of False. Let me give this some thought, it might be worthwhile to change its meaning for the public-facing API and make it a bit more useful as a result. Note that, if I were to make that change, all it really means is that canPlaceOrder would always be true if active is true, so I don't know if it's particularly useful.