FIX›Orders FIX

FIXMsgType 35=F

Order Cancel Request (35=F)

FIX 4.4 Gateway TLS/TCP

The client sends OrderCancelRequest (35=F) to the server over TLS/TCP. This is not an HTTP request.

Cancel an open order on the order-entry session.

Provide OrderID (37) and/or OrigClOrdID (41); at least one is required. Tag 37 takes precedence when both are supplied.

On success: server sends PendingCancel ExecutionReport (150=6, 39=6) then Canceled ExecutionReport (150=4, 39=4). LeavesQty (151) on the Canceled report is the open quantity at cancel time, not 0. Detect completion via OrdStatus (39) or ExecType (150), not 151=0.

On failure: server sends OrderCancelReject (35=9). Check CxlRejReason (102) and Text (58).

Message fields

TagFieldRequiredDescription
11 ClOrdID Optional

Optional. Unique ID for this cancel request. This ID is not echoed back in the cancel ExecutionReports.
41 OrigClOrdID Optional

Conditional. ClOrdID of the order to cancel; must match the ClOrdID sent in the NewOrderSingle. Required if OrderID (37) is absent.
37 OrderID Optional

Conditional. BitGo order UUID from ExecutionReport. When present, takes precedence over OrigClOrdID (41) for order resolution.
60 TransactTime Required

Required. UTC timestamp. Format YYYYMMDD-HH:MM:SS[.sss].
1 Account Optional

Optional. Must match the session account. Rejected if present and mismatched.

Response messages

  • On success
    Cancel accepted. PendingCancel then Canceled ExecutionReports follow.
  • On reject
    Cancel refused. The server responds with OrderCancelReject (35=9).

Examples

Examples (pipe-delimited FIX):

Cancel by OrigClOrdID:

8=FIX.4.4|9=132|35=F|49=0123456789abcdef0123456789abcdef|56=BITGO|34=91|52=20260618-12:46:28.424|11=cxl-ord-006|41=ord-006|60=20260618-12:46:28.424|10=XXX

Cancel by OrderID:

8=FIX.4.4|9=161|35=F|49=0123456789abcdef0123456789abcdef|56=BITGO|34=92|52=20260618-12:46:29.000|11=cxl-ord-007|37=80115a50-1542-48b7-92f9-03d99194ade3|60=20260618-12:46:29.000|10=XXX