Place a New Order Single request over FIX API.
The New Order Single message facilitates the submission of an order to the Central Limit Order Book (CLOB). Upon receiving this message, the FIX Gateway processes the request and provides a response in the form of an Execution Report or Business Message Reject, depending on the outcome of the order submission process.
This message serves as the primary method for initiating new trading orders within the system, enabling users to specify key order parameters such as instrument symbol, quantity, side (buy/sell), and price.
Message Fields
| Tag | Field Name | Required | Note |
|---|---|---|---|
| Standard Header | MsgType = D | ||
| 50 | SenderSubID | Yes | Participant ID created at Zero Hash with specific relationships on the CLOB |
| 1 | Account | Yes | Trading Account on the CLOB. This information will be shared during onboarding |
| 11 | ClOrdId | Yes | ClOrdID is a unique, platform generated identifier for an Order.
|
| 18 | ExecInst | - |
|
| 21 | HandlInst | Yes |
|
| 22 | SecurityIDSource | Yes |
|
| 38 | OrderQty | Yes | The amount of the base asset to be transacted.38 = 10.5146.Note - Not Required if field 152 used on Market with left over as Limit order instead |
| 40 | OrdType | Yes | The type of order for the request which can be:
|
| 44 | Price | - | The limit price for limit orders of the quote asset e.g. 19000.50 The decimal precision must fall within the requirements for each instrument |
| 48 | SecurityID | Yes | Symbol of the instrument being traded.
|
| 54 | Side | Yes | Side of the order.
|
| 55 | Symbol | - | Symbol of the instrument being traded e.g. BTC/USD, ETH/USD, etc |
| 59 | TimeInForce | - | Specifies how long the order remains in effect. The following values are supported:
|
| 60 | TransactTime | Yes | Time of execution/order creation. UTC time in datetime to millisecond or nanosecond format |
| 99 | StopPx | - | Specifies the quote price at which the order activates for Stop order types |
| 126 | ExpireTime | - | Required if TimeInForce = 6. UTC time in datetime to millisecond or nanosecond format |
| 152 | CashOrderQty | - | Can be used to specify dollar value to buy or sell on Market with left over as Limit orders instead of OrdQty(38) |
| 528 | OrderCapacity | Conditionally | OrderCapacity identifies the person submitting the trade. Values supported are :
|
| 582 | CustOrderCapacity | Conditionally | CustOrderCapacity identifies the customer/beneficiary of the trade.
|
| 1028 | ManualOrderIndicator | - | Indicates if the order was initially received manually (as opposed to electronically)
|
| 6127 | ConditionTriggerMethod | - | Specifies the trigger reference price for Stop Order.
|
| 8000 | SelfMatchPreventionInstruction | - | The following values specify what to do when two orders submitted by the same portfolio attempt to match.
|
| Standard Trailer | - | - | - |
Example Message
# Client - BTC/USD Buy Limit GTC Order for OrderQty 0.01 at Price of 19000.50
8 = FIXT.1.1
9 = 254
35 = D
34 = 426
49 = YOURSENDERCOMP
50 = [ParticipantId]
52 = 20230307-13:24:29.863406207
56 = ZERO
1 = [Account]
11 = 3637983906161824000
18 = R
21 = 1
22 = 8
38 = 0.01
40 = 2
44 = 19000.50
48 = BTC/USD
54 = 1
55 = BTC/USD
58 = ZH Testing Trades
59 = 1
60 = 20230307-13:24:29.863406207
167 = CS
10 = 007
8 = FIXT.1.1 | 9 = 254 | 35= D | 34= 426 | 49= YOURSENDERCOMP | 50= [ParticipantId] | 52= 20230307-13:24:29.863406207 | 56= ZERO | 1 = [Account] | 11= 3637983906161824000 | 18= R | 21= 1 | 22= 8 | 38= 0.01 | 40= 2 | 44= 19000.50 | 48= BTC/USD | 54= 1 | 55= BTC/USD | 58= ZH Testing Trades | 59= 1 | 60= 20230307-13:24:29.863406207 | 167 = CS | 10= 007