Orchimate / Community /

FINRA CAT4.0.0-r18

A timestamp represents a moment in time. Two timestamp formats are supported including STRING and NUMBER. <br> <br> Timestamps formatted as a STRING have a maximum length of 25 and are formatted as ‘YYYYMMDD HHMMSS.CCCNNNNNN’ with the Date and Time portions, separated by a space (ASCII decimal 32, hex 20) or the letter T (ASCII decimal 84, hex 54). All timestamps submitted in STRING format must be in Eastern Time (ET). <br> • The Date portion must include four digit year, two digit month, and two digit day. Valid values: YYYY = 0000 - 9999, MM = 00 - 12, DD = 00 – 31. <br> • The Time portion must include a two digit hour, two digit minute, two digit seconds. Valid values: HH = 00 - 23, MM = 01 - 59, SS = 01 - 59, CCC = 000 – 999, NNNNNN = 000000 - 999999. <br> <br> Examples which comply with Timestamp in STRING format: <br>• 20190617T000120.000000000<br>• 20190617T000120<br>• 20190617T000120.000<br>• 20170107T213000.123456789<br>• 20170107 213000.123456789<br>• 20190617 000120.123000000<br><br>Examples which do not comply with Timestamp in STRING format:<br>• 20190617T0120<br>• 20190617T000120.<br><br>As an alternative format, timestamp can be submitted as a value of type Unsigned, representing the number of nanoseconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970, not counting leap seconds. This is also commonly known as POSIX time or UNIX time. The same point in time from the above example would be represented as the number 1483842600123456789. Timestamps submitted in UTC must not be adjusted for Eastern Time.<br><br>Note that the data type is different between the two formats. In JSON, the first representation requires it to be surrounded by double quotes, while the second does not.<br><br>Examples which comply with Timestamp in NUMBER format:<br>• 1483842600123456789<br><br>Examples which do not comply with Timestamp in NUMBER format:<br>• 20190617T000120<br>• 20190617 000120