Conceptual Message Flows - Single Sided Submission - Trade Match

Use this search bar to search topics within the CME ClearPort API.

This page describes workflows associated with submission and successful matching (affirmation) of single sided trades submitted by participants. The variation in workflows based on the transport used for submitting these trades is also described here.

1 Trade Submitted Using MQ
2 Trade Submitted Using HTTP
3 Trade Submission for Match with Allocations

Trade Submitted Using MQ

In this scenario, two single-sided trades are submitted using MQ as a transport by two different submitters, and the trades are successfully matched by CME ClearPort. CME ClearPort will do a credit check if the matched trade does not require explicit claim by the clearing firms.

Trade Submitted Using HTTP

In this scenario, two single-sided trades are submitted using HTTP as a transport by two different submitters, and the trades are successfully matched by CME ClearPort. The difference here is that when a trade is matched, the submitters are not automatically notified of the match. The submitter will have to request for a trade status.

Trade Submission for Match with Allocations

This scenario is similar to the above scenarios where single sided trades are submitted for match into CME ClearPort. The variation here is allocations can be specified with the trade. Based on the asset class, allocations can be specified by one or both sides. If allocations are submitted allocation accounts will be validated. CME ClearPort may also check the risk limit for the allocation account if the allocations do not need to be claimed by the clearing firms.