{"@context":"https://schema.org","@type":"Article","headline":"Trade ticks not matching Aggregates","image":"https://massive.com/blog/content/images/2023/08/Trade-ticks-not-matching-Aggregates.png","description":"Aggregates ( OHLCV ) are a little more complex to calculate than just min,max,sum. There are condition matrix tables you must adhere to in the CTA and UTP specifications. ","publisher":{"@type":"Organization","name":"Massive","url":"https://massive.com/blog","logo":{"@type":"ImageObject","url":"https://massive.com$/brands/logo-massive.png"}},"url":"https://massive.com/blog/trade-ticks-not-matching-aggregates/","keywords":["api","equities","stocks","trades","faq"],"datePublished":"2019-09-06T12:20:00.000-04:00","dateCreated":"2019-09-30T12:20:33.000-04:00","dateModified":"2023-08-10T11:38:03.000-04:00","articleBody":"

Quite often we get support emails where a user is trying to calculate aggregates from the raw trade data. When doing so, the data does not seem to match up.

This is because aggregates ( OHLCV ) are a little more complex to calculate than just min,max,etc. There are condition matrix tables you must adhere to in the CTA and UTP specifications.

You can find our API aggregate condition mappings here.

For more information, the CTA and UTP documentation is below:

For CTA, See page 62:
https://www.ctaplan.com/publicdocs/ctaplan/notifications/trader-update/CTS_BINARY_OUTPUT_SPECIFICATION.pdf

For UTP, See page 43:
http://utpplan.com/DOC/UtpBinaryOutputSpec.pdf

","author":{"@type":"Person","name":"Quinton Pike","image":{"@type":"ImageObject","url":"https://massive.com/blog/content/images/2018/01/datacenter-1.jpg"},"url":"https://massive.com/blog/author/quintonpike/"},"mainEntityOfPage":"https://massive.com/blog/trade-ticks-not-matching-aggregates/"}