Passwords on MAPI are never expired, but Clients can request for password change to unlock an account or for any other reason.  If you wish to change the password, please contact MarketFactory Support.

• Client session is connected on receiving Trading session enabled notification from MAPI service.
• PrimeBroker Clients session is connected when PrimeBroker is logged in and Trading session is enabled by MAPI service.

CreditLow : UserNotification with this UserStatus is sent if remaining credit is below 25%.

CreditExhausted : UserNotification with this UserStatus is sent when credit is at 0%.

Global Throttle Rate Change : ErrorReport with Text message is sent when Global Throttle Rate Change override is received from MAPI. eg: "Global Throttle Rate Change override: New rate is 15 orders in 5 seconds."

Trade ExecutionReports are based on TradeCaptureReports received from the venue and thus the ordering of these are not reliable.

e.g: There can be Filled ExecutionReports received before PartiallyFilled ExecutionReports etc.

Clients should refer to PendingMatch ExecutionReports for the correct ordering.

• LegCurrency - Must be base currency of the instrument.
• LegPrice - Must be a multiple of the pip size and not exceed the left or right decimal place limits.
• 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. 

• 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.

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".

Clients will receive two ExecutionReports for each Fill/PartialFill as per below:

1. ExecType:PendingMatch, OrdStatus: PartiallyFilled/Filled.
2. 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.