...
MAPI trading functions supported for all API users.
| Function | Interbank | Prime Broker Client (PBC) | Prime Brokerage (PB) |
|---|
| FX Spot | Supported | Supported | N/A |
| FX Swap | Not Supported | N/A | N/A |
| Drop Copy (STP) | Supported | Supported | Not Supported |
| STU Management | N/A | N/A | Not Supported |
| PBC Session Control | N/A | N/A | Not Supported |
| MOS & MOOPI | Supported | N/A | Not Supported |
| Info |
|---|
|
- Currency
LegCurrency - Must be base currency of the instrument. - Price
LegPrice - Must be a multiple of the pip size and not exceed the left or right decimal place limits. - OrderQty
LegOrderQty - Must be greater than the instruments minimum quantity , a multiple of the instruments lot size and less than the instruments maximum order size. LegAllocAccount - Not Mandatory but can be populated in NewOrderMultiLeg message and is echoed back in ExecutionReport but not validated by MAPI. LegGroup - Supported value is "Domestic" for "EUR/ISK" SPT only.
|
| Info |
|---|
|
ExecutionReport with OrdStatus calculated is received when MAPI service sends TradeCapture reports. - Clients can choose to receive these
ExecutionReports on Trading session or on DropCopy session. Please contact MarketFactory Support for a preferred setup. ExecutionReports on DropCopy session will not have all order attributes populated. e.g: LegCumQty, LegLeavesQty etc.
|
...
| Note |
|---|
| title | ExecutionReports: ExecID |
|---|
|
MAPI ExecID is not unique per ExecutionReport. Multiple ExecutionReports generated by the same event will have same ExecID. e.g Multiway matches, Unsolicited cancels due to logout etc. To maintain the uniqueness of ExecID in Clients ExecutionReport, it is constructed as below using venue's MatchID/ExecType/ClOrdID. - For
PartiallyFilled/Filled Execution Reports Venue TrdMatchID is the ExecID. - For
New/Canceled/PendingCancel/Rejected/Expired Execution Reports ExecID is "MF:ExecID:ExecType:ClOrdID". PendingNew Execution Reports ExecID is "MF:ClOrdID".
|
| Note |
|---|
| title | ExecutionReports: ExecType vs OrdStatus |
|---|
|
Clients will receive two ExecutionReports for each Fill/PartialFill as per below: ExecType:PendingMatch, OrdStatus: PartiallyFilled/Filled.ExecType:Trade, OrdStatus: PartiallyFilled/Filled.
There can be a delay between the PendingMatch and the Trade ExecutionReports received from MAPI. In such cases, it is possible for the client to receive ExecutionReport with OrdStatus Canceled followed by Trade/PartialFill. |
Algo Selection
MAPI supports MoreQty order in addition to native Iceberg Order, where order is cancelled automatically when MaxShow amt is filled.
Iceberg Order Variations |
Maxshow | TargetStategy |
|---|
| Iceberg | MoreQty |
|---|
MoreQty Order | ✓ |
| ✓ |
|---|
Native Iceberg Order | ✓ |
|
|
|---|
Iceberg Order with Strategy Parameters |
| ✓ |
|
|---|
The table below sets out the Iceberg order Strategy parameters and combinations currently supported.
| StrategyParameterName | StrategyParameterType | StrategyParameterValue | Conditions |
|---|
TargetStrategy | String | Iceberg | Maxshow not populated |
|---|
TipSpecificationType | String | D - Defined
R - Random | SPN1=TargetStrategy
SPV2=Iceberg
|
|---|
FirstTip | Qty | Primary First Tip Qty (eg:1000000) | SPN1=TipSpecificationType
SPV2=Defined
|
|---|
SecondTip | Qty | Primary Second Tip Qty (eg:2000000) | SPN1=TipSpecificationType
SPV2=Defined
|
|---|
ThirdTip | Qty | Primary Thrid Tip Qty (eg:3000000) | SPN1=TipSpecificationType
SPV2=Defined
|
|---|
MinimumRandomTip | Qty | The lower bound for the randomly chosen quantity | SPN1=TipSpecificationType
SPV2=Random
|
|---|
MaximumRandomTip | Qty | The upper bound for the randomly chosen quantity | SPN1=TipSpecificationType
SPV2=Random
|
|---|
Delay | Int | The delay used between refreshes | The ID number of the chosen delay range . |
|---|
- SPN : StrategyParameterName
- SPV : StrategyParameterNameStrategyParameterValue