The ttmonitor service of the TT REST API is used for requests pertaining to viewing positions and SOD records for a given account.<\/p>\n\n\n\n
Note: <\/strong>ttmonitor is not intended to be used as a real-time feed since there may be delays between the time at which order and fill events occur and the time when they are available via TT REST API. Applications requiring a real-time feed should use TT .NET SDK<\/a> or TT FIX<\/a> .<\/p>\n\n\n\n Requests to the ttmonitor service of the TT REST API use the following base URL: ttrestapi.trade.tt\/ttmonitor\/<environment><\/strong>:<\/p>\n\n\n\n Note<\/strong>: When submitting requests, all API urls are case sensitive and should include the endpoint name in lowercase. For example, using https:\/\/ttrestapi.trade.tt\/TTMONITOR<\/strong>\/ext_uat_cert\/<\/em> results in a 403 server error.<\/p>\n\n\n\n You must use https:\/\/ttrestapi.trade.tt\/ttmonitor<\/strong>\/ext_uat_cert\/<\/em> in order to properly reach the API.<\/p>\n\n\n\n For POST endpoints which allow for the submission of a list of items, the number of list items must not exceed twenty. Furthermore, a one-second pause must be initiated after the acknowledgement from a prior POST submission has been received. Most daily maintenance and activity will not be affected by these limits and can be accomplished normally on weekdays.<\/p>\n\n\n\n Activities that involve uploading significant amounts of data, such adding large numbers of users or starting a migration, will require special scheduling. In such circumstances, please contact TT Onboarding with scheduling assistance.<\/p>\n\n\n\n Calls to the ttmonitor services listed below require both of the following in your header:<\/p>\n\n\n\n For instructions on obtaining your\u00a0application key<\/a>\u00a0and\u00a0token<\/a>, refer to the related sections in the TT REST Web Services documentation.<\/p>\n\n\n To test the calls below, click the\u00a0Authorize<\/strong>\u00a0button and enter values for both access parameters into the “Available authorizations” dialog.<\/p>\n\n\n\n Note:<\/strong>\u00a0When entering your\u00a0token<\/strong>,\u00a0you will need to manually concatenate “Bearer” and a single space in front of the token value sent by ttid.<\/p>\n\n\n\n All test calls sent through this help site use the following base URL:<\/p>\n\n\n\n <\/p>\n<\/div>\n\n The ttmonitor service of the TT REST API is used for requests pertaining to viewing positions and SOD records for a given account.<\/p>\n Note: <\/strong>ttmonitor is not intended to be used as a real-time feed since there may be delays between the time at which order and fill events occur and the time when they are available via TT REST API. Applications requiring a real-time feed should use TT .NET SDK<\/a> or TT FIX<\/a> .<\/p>\n Requests to the ttmonitor service of the TT REST API use the following base URL: ttrestapi.trade.tt\/ttmonitor\/<environment><\/strong>:<\/p>\n Note<\/strong>: When submitting requests, all API urls are case sensitive and should include the endpoint name in lowercase. For example, using https:\/\/ttrestapi.trade.tt\/TTMONITOR<\/strong>\/ext_uat_cert\/<\/em> results in a 403 server error.<\/p>\n You must use https:\/\/ttrestapi.trade.tt\/ttmonitor<\/strong>\/ext_uat_cert\/<\/em> in order to properly reach the API.<\/p>\n For POST endpoints which allow for the submission of a list of items, the number of list items must not exceed twenty. Furthermore, a one-second pause must be initiated after the acknowledgement from a prior POST submission has been received. Most daily maintenance and activity will not be affected by these limits and can be accomplished normally on weekdays.<\/p>\n Activities that involve uploading significant amounts of data, such adding large numbers of users or starting a migration, will require special scheduling. In such circumstances, please contact TT Onboarding with scheduling assistance.<\/p>\n Calls to the ttmonitor services listed below require both of the following in your header:<\/p>\n For instructions on obtaining your\u00a0application key<\/a>\u00a0and\u00a0token<\/a>, refer to the related sections in the TT REST Web Services documentation.<\/p>\n","protected":false},"author":2,"template":"single-item-doc-uat","meta":{"_acf_changed":false,"footnotes":""},"docs-category":[1600],"class_list":["post-7958","doc","type-doc","status-publish","hentry","docs-category-api-reference-tt-rest-api-2-0-uat"],"acf":[],"_links":{"self":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7958","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc"}],"about":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/types\/doc"}],"author":[{"embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/users\/2"}],"version-history":[{"count":0,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7958\/revisions"}],"wp:attachment":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/media?parent=7958"}],"wp:term":[{"taxonomy":"docs-category","embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/docs-category?post=7958"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
Limitations for POST requests<\/a><\/h2>\n\n\n\n
Access Parameters<\/a><\/h2>\n\n\n\n
\n
\n
x-api-key=<application key><\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n\n
Authorization=Bearer <token><\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\nTest calls<\/a><\/h2>\n\n\n\n
https:\/\/ttrestapi.trade.tt\/ttmonitor\/ext_uat_cert<\/code><\/p>\n\n\n\nLimitations for POST requests<\/a><\/h2>\n
Access Parameters<\/a><\/h2>\n