When you make many API order requests it can be confusing keeping an accurate history of which requests have been successful, failed, or returned with an error status.

Adding idempotency to your API requests via the client_order_id field is a great way to always be able to locate a unique API request and determine its status accurately.

For instance, if a user has 5 orders and wants to cancel all of them - once the user submits all 5 cancellation requests, the user will also receive 5 unique responses. This informs the user that all orders have been canceled.

Without idempotency, users might not be able to monitor if all 5 orders were canceled, as the user might have sent the cancel request for 1 order 5 times - leaving the other 4 orders still active.