As part of our continuous improvements to the BitMEX platform, we will be updating the rejection message in the response body when an order amendment request is rejected by the BitMEX platform on 21 December 2021.
When BitMEX receives an order amendment request through the PUT `/order` endpoint, in which the order has been filled, cancelled, or rejected, BitMEX sends a 400 response with `“message”: “Invalid ordStatus”` in the response body.
Going forward, BitMEX will provide more details when the platform rejects the order amendment request.
- When a user amends an order that has been fully filled, and BitMEX rejects further amendments, the `message` field in the response body will become `Invalid ordStatus: Filled`
- When a user amends an order that has been canceled, the `message` field in the response body will become `Invalid ordStatus: Canceled`
- When a user amends an order that has been rejected, such as failing to pass risk checks, the `message` field in the response body will become `Invalid ordStatus: Rejected`
This change has been applied in Testnet.