# Timestamp value is in future or sometimes null

**URL:** <https://community.hubspot.com/t/timestamp-value-is-in-future-or-sometimes-null/11245>\
**Category:** APIs & Integrations\
**Tags:** contacts\
**Created:** [September 7, 2018, 7:41am UTC](https://community.hubspot.com/t/timestamp-value-is-in-future-or-sometimes-null/11245 "2018-09-07T07:41:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fivetran](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/fivetran/32/33328_2.png) [@Fivetran](https://community.hubspot.com/u/Fivetran)\
**Post date:** [September 7, 2018, 7:41am UTC](https://community.hubspot.com/t/timestamp-value-is-in-future-or-sometimes-null/11245/1 "2018-09-07T07:41:15Z")

</div>

Hi,  
We are using Hubspot API And we found that timestamp value is sometimes null or sometimes it has a huge value, check the below example -  
“hs\_email\_delivered” : {  
“versions” : [  
{  
“timestamp” : 1449077401367000002,  
“selected” : false,  
“source-type” : “EMAIL”,  
“source-vids” : [  
19713  
],  
“source-id” : null,  
“source-label” : null,  
“value” : “2”  
},  
Could you please confirm if the timestamp value is always in milis or it can be micro secs as well.If you convert the above value in milis, it becomes a future value (more than 10000 years ahead).

---

<div class="post-metadata">

**Author:** ![IsaacTakushi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isaactakushi/32/70387_2.png) [@IsaacTakushi](https://community.hubspot.com/u/IsaacTakushi)\
**Post date:** [September 17, 2018, 3:53pm UTC](https://community.hubspot.com/t/timestamp-value-is-in-future-or-sometimes-null/11245/2 "2018-09-17T15:53:44Z")

</div>

Hi [@FivetranDevelopers](https://community.hubspot.com/u/fivetrandevelopers),

To my knowledge, HubSpot’s APIs only use [millisecond timestamps](https://developers.hubspot.com/docs/faq/how-should-timestamps-be-formatted-for-hubspots-apis). Curiously, when the [Epoch Converter](https://www.epochconverter.com/) interprets the timestamp **1449077401367000002** in microseconds, the resulting year is **47889**.

Would you confirm your Hub ID as well as the endpoint you used?