Skip to main content
For an overview of order groups and how they work, see Order Groups.

Order Group Request (35=UOG)

Manage order groups with Create, Reset, Delete, Trigger, and Update operations.

Required Fields

Optional Fields

Order groups are scoped per subaccount. An OrderGroupID created under AllocAccount=2 cannot be reset, updated, deleted, or triggered without also passing AllocAccount=2 on the follow-up request. If the AllocAccount value does not match the group’s owning subaccount, the exchange returns an ORDER_GROUP_NOT_FOUND business reject.

Fields by Action

Create (Action=1)

The OrderGroupID is generated by the server and returned in the response. Do not include tag 20130 in Create requests.

Reset (Action=2)

Delete (Action=3)

Deleting an order group cancels all resting orders in that group.

Trigger (Action=4)

The Trigger action immediately cancels all orders in the specified order group, regardless of whether the contracts limit has been reached. This is useful for manual risk management or emergency order cancellation.

Update (Action=5)

If the updated limit would immediately trigger the group (based on the rolling 15-second window), the server cancels all orders in the group and marks it as triggered. No new orders can be placed until the group is reset.
Examples:
Create Order Group
Reset Order Group
Delete Order Group
Trigger Order Group
Update Order Group Limit
Create Order Group for subaccount 2

Order Group Response (35=UOH)

Response to order group management requests.

Response Fields

Business-logic errors (e.g. order group not found, exchange-returned errors) are returned as BusinessMessageReject (35=j) messages. Malformed fields (e.g. invalid UUID format for OrderGroupID) produce a session-level Reject (35=3).