Hi All,

I have been struggling to understand the different sale conditions for US stocks. I have been looking for this answer for quite a while, but wasn't able to find anything useful.
I am referring to sale conditions such as:

* Acquisition ({"UTP": "A"})

* Average Price Trade ({"CTA": "B", "UTP": "W", "FINRA_TDDS": "W"})

* Automatic Execution ({"CTA": "E"})

* Bunched Trade ({"UTP": "B"})

* Bunched Sold Trade ({"UTP": "G"})

* CAP Election ({"CTA": "I"})

* Cash Sale ({"CTA": "C", "UTP": "C", "FINRA_TDDS": "C"})

...

I can see that TradingView or Interactive Brokers have different highs and lows than what I have in my PolygonIO data. I am guessing that they exclude some of these order types.

Question 1: If I want to recreate the same charting UI, which sale conditions should I also exclude?

Question 2: Which of these types would not affect my stop or limit orders? For example, if the condition is Acquisition, would that trigger my stop or fill my limit order?

Question 3:Is there any free or paid tutorial regarding these types?

If someone could help me out with this, I would really appreciate it.

Szervusz,

as far as I remember, the trade conditions in Polygon can be queried separately using their API, and the response will have fields such as 'updates high/low' and 'updates close'.

So some trades do not update any of the high/low/close (e.g. Average Price trades, these are just invisible for a chart) and some trades don't update just the high/low but do update close. One of their blogposts contains the rules for whether you use AND or OR logic for trades that have multiple trade conditions with conflicting 'updates XYZ' status.

Question 1 will be answered in the mentioned blogpost on polygon site.

Question 2 I would ask Polygon support about this, making sure some of the old time guys answers, the cute lady seemed to be a bit lost when I talked to her (about a year ago).

Question 3 - I wondered this myself so many times. If you find some material about this, we can split the cost if its paid. I have wondered a lot what is the significance (or maybe insignificance) of FORM-T and STOCK_OPTION_TRADE conditions. On databento support channel, a guy from some volatility trading hedge fund said that seeing trade conditions in option trades is absolutely necessary (for them to be profitable), so if we knew the details of what trade conditions imply in options trading, it would be even better.

Cheers,
Daniel

Eubie 

Szervusz, as far as I remember, the trade conditions in Polygon can be queried separately using their API, and the response will have fields such as 'updates high/low' and 'updates close'. So some trades do not update any of the high/low/close (e.g. Average Price trades, these are just invisible for a chart) and some trades don't update just the high/low but do update close. One of their blogposts contains the rules for whether you use AND or OR logic for trades that have multiple trade conditions with conflicting 'updates XYZ' status. Question 1 will be answered in the mentioned blogpost on polygon site. Question 2 I would ask Polygon support about this, making sure some of the old time guys answers, the cute lady seemed to be a bit lost when I talked to her (about a year ago). Question 3 - I wondered this myself so many times. If you find some material about this, we can split the cost if its paid. I have wondered a lot what is the significance (or maybe insignificance) of FORM-T and STOCK_OPTION_TRADE conditions. On databento support channel, a guy from some volatility trading hedge fund said that seeing trade conditions in option trades is absolutely necessary (for them to be profitable), so if we knew the details of what trade conditions imply in options trading, it would be even better. Cheers, Daniel

Hi Daniel,
Thanks. I don't know how come that I didn't find this blogpost from Polygon. I am very new to stock trading, and it is clearly much more complex than I thought.
If I find any useful tutorial, I will let you know.