This page describes the FX Integration API’s Block Trade trade model, as defined in the file
config/TradingAdapter/Blade/DataSource/etc/trademodels.xml in the FX Integration API Kit.
This documentation is for the FX Integration API 3.49.0.
Block trades use the RFS trade model, with the following modifications:
The RFS trade model is reproduced below. To simplify the diagram, the Rejected and Error states have been omitted.
Messages: client → server
Messages sent by StreamLink clients to the FX API DataSource.
A block trade uses the same trade model as an RFS trade, but the legs in
Execute messages play different roles when used in the context of a block trade:
In Submit messages,
Lnmessage parts refer to non-netted legs
In Execute messages,
Lnmessage parts refer to netted legs
Messages: server → client
Messages sent by the FX API DataSource to StreamLink clients.
A block trade uses the same trade model as an RFS trade, but with different specifications for
Price Update: Block Quote, Sales Block Quote
Trade Confirmation: Block Trade Confirmation, Block Sales Trade Confirmation
In Trade Confirmation messages, an
Ln message part represents an executed netted leg. Within an
Ln message part,
Ln_In message parts represent the original, pre-netted legs.