New entry order with stop/limit results in "Trigger level calculation type does not exist" in General Questions and Discussion Posted July 25, 2013 · Report reply Ok, I’ve found the problem. Let me give you some context first: I’m using the CIAPI.CS, and more specifically, the WP7 branch. The problem is that the ApiStopLimitOrderDTO inherits from ApiOrderDTO, which has a Price property. Then I found an important difference when I compared my JSON message with the one sent by FlexITP: the API expects stop/limits with a property calledTriggerPrice, so the mapping is not correct. I tested the same JSON message with the corrected property name and it worked fine. Could you please give it a look?