Planned October 2022 - BREAKING
Removal of a number of fields in the trade/v1/allocationkeys resource:
The following fields are planned for removal (On or after October 2022)
|PredefinedQuantity||Please use TotalUnitValues instead.|
Planned November 2022 - BREAKING
Removal of a number of fields in the trade/v2/orders, trade/v2/orders/multileg , trade/v2/orders/precheck and trade/v2/orders/multileg/precheck resources:
The following fields are planned for removal (On or after November 2022)
|OrderDuration.ExpirationDate||Please use ExpirationDateTime instead.|
|OrderDuration.ExpiryTimeOnExchange||Please use ExpirationDateTime instead.|
Change to functionality in PUT ca/v2/elections (On or after November 2022)
While changing and withdrawing previous elections are allowed for most of the voluntary events, some events have special terms that once submitting the elections, investors are not be allowed to change or withdraw these elections. Today it is possible to submit changes or withdrawal via OpenAPI and such elections are handled in later stages.
After this change,
- the PUT ca/v2/elections endpoint will reject an election base on the AllowedAction settings of the options. Error codes ChangeInElectionNotAllowed and WithdrawalOfElectionNotAllowed will be responded together with their messages respectively;
- the GET /ca/v2/events will respond the additional AllowedAction in each options to indicate which actions are allowed on this option. For most of the voluntary events, the AllowedActions will be ["Change", "Withdrawal"];
- these election rules will also take place in the PUT ca/v2/elections/bulk endpoint.
As an example, assume that an event has 2 options, option 1 allows change and withdrawal while option 2 disallows change and withdrawal, it's response of GET /ca/v2/events will be:
After making the initial election, further changes on Option 1 will still be available. But changes or withdrawals on Option 2 will be rejected.