Page History

...

Clients may reference or populate all other regulatory fields for appropriate messages via the use of dedicated repeating groups containing key/value pairs, at the appropriate level within the message structure:

RegulatoryBodies

...

This field in the main message body provides an explicit indication whether or not SEF, EMIR or MiFID fields are populated elsewhere in the message structure and provides the message reader - either Whisperer or the Client with an explicit means of deciding whether or not this request/trade requires further regulatory processing.

...

If the Client believes that they are submitting a trade on MTF (an NDF for example), then they should set the flag for MiFID.

Flags are ordered SEF EMIR MiFID SFTR. If connecting via FIX Protocol, this would be represented as : "N N Y N"

Regulatory Fields

NoBodyRegulatoryFields, NoLegRegulatoryFields and NoAllocRegulatoryFields groups contain sequences of key/value pairs, with keys of

...

type BodyRegulatoryKey,

...

 LegRegulatoryKey and AllocRegulatoryKey, respectively.

ISINs

For swaps, ISINs are maintained at the Leg level in the API.

...