CME STP FIX - TradeCaptureReportRequest - EBS FX

CME STP FIX - TradeCaptureReportRequest - EBS FX

The Trade Capture Report Request (tag 35-MsgTyp=AD) message is used by FIX Client to: 

  • Subscribe (with or without filters) to trades on EBS Markets on CME Globex and EBS Direct

  • Request snapshot of trades on EBS Markets on CME Globex and EBS Direct

FIX Tag

Field Name

Req

Data Type

Description

Supported Values

Standard FIX Header

Y

 

tag 35-MsgTyp=AD

 

568

TradeRequestID

Y

String

TradeCaptureReportRequest ID.

 

1003

TradeID

N

String

The EBS Deal ID - Only trades of EBS on CME Globex are supported.
EBS Direct Deal ID support is under development.

 

569

TradeRequestType

Y

int

Type of Trade Capture Report.

1 - Matched trades matching criteria provided on request (Parties, ExecID, TradeID, OrderID, Instrument, InputSource, etc.)

263

SubscriptionRequestType

Y

char

Subscription Request Type. 

  • 0 - Snapshot

  • 1 - Snapshot + Updates (Subscribe)

11

SideClOrdID

N

String

Client Order ID, assigned by the API users.

For Globex , ClOrdId as stated in iLink or AI message. Not valid for workstation related trades. 

For EBS Direct, ClOrdID provided in API by Liquidity Consumers. Not relevant for tickets by Liquidity Providers.

 

 

 

 

 

442

MultiLegReportingType

N

int

Request multi-legged instrument trades either as Individual leg or Summary trades.

  • 2 - Request outright and individual legs of multi-leg deals
    (MLegRptTyp = '1' and '2')

  • 3 - Request outright and summaries of multi-leg deals
    (MLegRptTyp = '1' and '3')

Optional request parameter.

If not present in the subscription request, defaults to '2'. 

779

LastUpdateTime

C

UTCTimestamp

For a Snapshot + Update (263=1) subscription request, this tag specifies the date and time that the request should start to stream trade data from. If tag 779 is not present, the request will default to the current datetime of the subscription.

Tag 779 is not applicable to Snapshot-only (263=0). These requests will be rejected.

  • Format: Tag 779-LastUpdateTime must be formatted as YYYYMMDD-HH:MM:SS.ns
    All times must be in UTC. CME STP will not accept timezone offsets.

  • Example: 20200520-01:14:39.126000000

While client systems may submit the timestamp with up to nanosecond precision, CME STP will truncate the data to the second during request processing.

Back dated requests can be submitted for maximum period of 31 calendar days.

 

9593

StartTime

C

UTCTimestamp

For a Snapshot (263=0) request this required tag specifies the start date and time to pull data from.

Tag 9593 is not applicable to Snapshot + Update (263=1), requests including this tag will be rejected.

  • Format: Tag 9593-StartTime must be formatted as YYYYMMDD-HH:MM:SS.ns
    All times must be in UTC. CME STP will not accept timezone offsets.

  • Example: 20200520-01:14:39.126000000

While client systems may submit the timestamp with up to nanosecond precision, CME STP will truncate the data to the second during request processing.

Back dated requests can be submitted for maximum period of 31 calendar days.

 

9594

EndTime

N

UTCTimestamp

For a Snapshot (263=0) request this optional tag specifies the end date and time of the request. This value cannot be in the future. Client systems that submit requests without tag 9594, will default to the current date and time of the request.

Tag 9594 is not applicable to Snapshot + Update (263=1), requests including this tag will be rejected.

  • Format: Tag 9594-EndTime must be formatted as YYYYMMDD-HH:MM:SS.ns
    All times must be in UTC. CME STP will not accept timezone offsets.

  • Example: 20200520-01:14:39.126000000

While client systems may submit the timestamp with up to nanosecond precision, CME STP will truncate the data to the second during request processing.

Back dated requests can be submitted for maximum period of 31 calendar days.

 

99103

PostTradeType

N

int

Used to filter for / subscribe to tickets based on the ticket type. Typically only valid for use by Prime Brokers.

Prime Give Up tickets are also known as synthetic tickets representing the back to back deal with the prime Customer. 

  • 4 - Prime Give up (Synthetic tickets)

  • 5 - Interdealer

  • 6 - Prime of Prime Broker - Equivalent of Interdealer ticket (facing the Parent of the Prime of Prime Broker).

578

TradeInputSource

N

String

Type of input device or system from which the trade was entered.

  • GLBX (CME Globex)

  • EBSD (EBS Direct)

1028

ManualOrderIndicator

N

Boolean

Used to subscribe to tickets based on origination either from API or manually created trades.

  • Y - Manual Trades

  • N - API Trades 

20400

NonDisclosedIndicator

N

Boolean

Used to subscribe to tickets based on disclosed or non-disclosed status of the trade.

Only applies to EBS Direct trades, ignored for Globex trades.

  • N - Disclosed

  • Y - Non-Disclosed

1430

VenueType

N

char

Used to subscribe to trades based on the venue where the trade was executed.

  • For Globex Venue Type is set to 'E'.

  • For EBS Direct Venue Type is set to 'Q'.

  • E - Electronic

  • Q - Quote-driven Market

20401

TradePartyType

N

int

When used in conjunction with PartyRole (tag 452) R=7 (Trading Firm) provides further context of the role played by that trading firm.

  • 0 - All Trades

  • 1 - Executing Firm

  • 2 - Prime Broker

453

Parties

 

 

 

 

Instrument

 

 

 

 

580

TrdCapDtGrp

 

 

 

 

Standard Trailer




How was your Client Systems Wiki Experience? Submit Feedback

Copyright © 2024 CME Group Inc. All rights reserved.